Update webhook secret
Updates the webhook secret used for signing webhook payloads.
Webhook Security: Each webhook request is signed using HMAC SHA256. The signature is computed from the exact JSON payload and included in the Signature HTTP header.
Verification: Compute the HMAC signature using your secret and the raw request body, then compare it to the Signature header before processing.
If no webhook secret is set, webhook requests will not include a Signature header.
Authorizations
HMAC signature authentication for backend integrators.
Required Headers:
- X-Integrator-Key: Integrator API key (format: int_...)
- X-Signature: HMAC signature (format: sha256={hex})
- X-Timestamp: Unix timestamp in milliseconds
- Authorization: Bearer {user-api-key}
Signature Algorithm: HMAC-SHA256
Signature Format: {timestamp}.{METHOD}.{path}.{bodyHash}
- timestamp: Unix timestamp in milliseconds
- METHOD: HTTP method in UPPERCASE (GET, POST, etc.)
- path: Request path (e.g., /v1/transactions)
- bodyHash: SHA256 hex digest of request body (empty string if no body)
Timestamp Tolerance: ±5 minutes (300 seconds)
Example: For POST /v1/transactions with body {"amount":100} and timestamp 1234567890000: Payload: 1234567890000.POST./v1/transactions.{sha256(body)} Signature: sha256=abc123...
Integrator API key (format: int_...) used with HMAC authentication
Unix timestamp in milliseconds for replay attack prevention. Must be within 5 minutes of server time.
Body
The secret key used to compute HMAC SHA256 signatures for webhook payloads. The signature is included in the Signature HTTP header of each webhook request.
1"whsec_abc123def456"
Response
Response for status 200
Always true after the webhook secret is configured
true