Skip to main content
API v1 is deprecated and will be removed in the future. Please migrate to API v2 for new features and long-term support.

Overview

To protect your webhook endpoints from malicious requests, we’ve implemented RSA-SHA256 signature verification. Every webhook request from our system includes cryptographic signatures in the headers that you can verify using our public key to ensure the request genuinely came from us. Why This Matters: Without signature verification, anyone could send fake webhook requests to your endpoints. This system ensures only legitimate requests from our platform reach your application.

How It Works

We use RSA-SHA256 digital signatures with 2048-bit keys:
  1. We sign each webhook request with our private key
  2. You verify the signature using our public key
  3. If verification passes, you know the request is authentic

Request Headers

Every webhook request includes these security headers:

Signature Construction

We create the signature by concatenating three components:
Example:
Where:
  • timestamp: Request timestamp (matches X-Webhook-Timestamp)
  • url: Complete webhook URL (including query parameters)
  • body_sha256_hex: SHA256 hash of the request body in hex format

Get Our Public Key

API Endpoint

Response Format

Pro Tip: Cache this public key! Don’t fetch it on every webhook request.

Implementation Examples

Security Best Practices

πŸ”‘ Always Cache the Public Key

πŸ• Always Verify Timestamps

πŸ”’ Use HTTPS Only

🚫 Don’t Leak Error Details