Create a sandbox webhook endpoint
Register a sandbox webhook endpoint and get its signing secret.
Path parameters
orgIdstringRequiredThe opaque organization id issued to you, normally CUID-shaped (for example
cmsx…). It is not anorg_-prefixed alias. Pass it unchanged in every organization-scoped path.
Body
This endpoint expects a JSON object.
urlstring<uri>RequiredPublicly reachable HTTPS URL. From your own machine, use a public HTTPS tunnel such as cloudflared or ngrok.
eventsarray of stringOptionalOmit to receive every event type.
Allowed values:payout.pendingpayout.processingpayout.completedpayout.failedShow 18 more values
payout.returnedpayout.canceledpayout_approval.pendingpayout_approval.approvedpayout_approval.rejectedpayout_approval.expiredpayout_approval.executedpayout_approval.execution_failedpayout_batch.awaiting_confirmationpayout_batch.completedpayout_batch.canceledpayout_batch.failedcheckout_payment.paidcheckout_payment.failedcheckout_payment.refundedcheckout_payment.reversedcheckout_payment.partially_refundeddeposit.completed
Behavior
Test keys only. Register a publicly reachable HTTPS receiver. Use a public HTTPS tunnel (for example cloudflared or ngrok) for webhooks from the sandbox.
Live endpoints are https and are created from the dashboard by a human: a credential able to repoint its own webhook URL could quietly redirect every payout notification, so that stays off the API.
The secret is returned once and is not retrievable afterwards.
The body is validated against the schema below: an unknown event
name, or an events that is not an array, answers
400 VALIDATION_ERROR.
Responses
201The endpoint, including its signing secret.
Body
idstringRequiredurlstringRequiredeventsarray of stringRequiredsecretstringRequiredShown once. Store it now.
warningstringRequiredcreatedAtstring<date-time>Required
Errors
400BAD_REQUEST: a live key (this is test-only), or nourl.UNSAFE_WEBHOOK_DESTINATION: the URL is malformed, carries credentials, or resolves to an address we will not deliver to.401The key was refused. Nothing ran.
UNAUTHORIZED: missing, invalid or revoked, or a key on a route that does not accept one.KEY_EXPIRED: the key passed the expiry it was issued with. Issue a new one; an expired key cannot be rotated.KEY_IP_NOT_ALLOWED: the key is pinned to source addresses and this request came from another.
403DEVELOPER_FEATURE_DISABLED: developer tools are off for your organization. Or the refusals every write can answer:FORBIDDEN,ACCOUNT_BLOCKED,INSUFFICIENT_SCOPE.429Too many requests. The default ceiling is 100 requests per minute per API credential on a 60-second window. High-volume payout and reconciliation routes declare a 600/minute override, and batch submission a 30/minute ceiling. A separate 2,000/minute per-source-IP abuse ceiling always applies.
Obey
Retry-After; it is in seconds and is authoritative. A 429 means the request was refused before the handler ran. Retry reads normally; retry an idempotent mutation with its sameIdempotency-Key.
Error body · Error
typestringRequiredStable machine-readable code.
detailstringRequiredWhat went wrong, in a sentence. Always a string, so
detail.toLowerCase()is safe.More
This is the field to read on
BAD_REQUESTandPROVIDER_REJECTED, where the type alone does not name the condition.messagestringRequiredThe same text as
detail, kept for integrations written beforedetailexisted. Readdetail.resolutionstringOptionalWhat to do about it, when there is a specific answer. It is not on every error (it is absent on
BAD_REQUEST,NOT_FOUND,PAYOUT_NOT_CANCELABLEandDESTINATION_ACCOUNT_NOT_FOUND), so treat it as optional and fall back todetail.statusintegerRequiredHTTP status, repeated in the body.
statusCodeintegerRequiredThe same value as
status, kept for integrations written beforestatusexisted. Readstatus.requestIdstringRequiredQuote this to support and we can find the exact request. Also sent as the
x-request-idresponse header, which is the only place it appears on a successful response. Success bodies do not carry it. Send your ownx-request-idon the request and we use it, so your trace and ours share one identifier; otherwise we mint one.errorsarray of stringOptionalPresent on VALIDATION_ERROR; names each field that failed.
originalIdempotencyKeystringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. Send the request again with this to receive the original payout instead of making a second one. Without it there is no way to recover except by risking a double payment.originalPayoutIdstringOptionalOn
DUPLICATE_REQUEST_DETECTEDonly. The payout the first request created.originalBatchIdstringOptionalOn a batch
DUPLICATE_REQUEST_DETECTED. The run the first request created.originalRequestIdstringOptionalOn a
409 PAYOUT_OUTCOME_UNKNOWNreplay. TherequestIdof the call whose outcome is unknown; quote it to support.existingRecipientIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The recipient in your organization that already holds this account.existingMethodIdstringOptionalOn
BANK_ACCOUNT_ALREADY_LINKED. The payment method on that recipient.
Branch on type, never on the status or the message. Every error type is listed with what to do about it.
Was this page helpful?