Register a Webhook Endpoint for Event Delivery
Register a new webhook endpoint to receive event deliveries for the specified subscribed events.
* for everything, or a resource wildcard such as customer.*. A new endpoint is enabled immediately and starts receiving matching events.
Each application may hold at most six active endpoints, counting the enabled, disabled, and errored states. Exceeding that returns 409. There is no update operation, so changing a URL or a subscription means creating a replacement and deleting the old endpoint — see managing endpoints for the zero-gap sequence.Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
API version date string provided by the client.
"2026-04-01"
List of event types this endpoint should receive.
1The HTTPS URL to deliver webhook events to.
2048"https://example.com/webhooks/sphere"
Human-readable description of this webhook endpoint.
500"Production payment events handler"
Arbitrary key-value metadata to attach to this endpoint.
Response
The created webhook endpoint, including the signing secret. The secret is returned only here and cannot be retrieved again.
Signing secret for this endpoint. Returned only on creation and never retrievable afterwards.
"whsec_a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6"
enabled, errored, disabled, deleted *, customer.*, transfer.*, document.*, service.*, customer.created, customer.pending, customer.approved, customer.rejected, transfer.created, transfer.pendingFunding, transfer.pendingReview, transfer.fundsReceived, transfer.processing, transfer.succeeded, transfer.returned, transfer.pendingRefundInformation, transfer.failed, transfer.canceled, transfer.refunded, transfer.unexpectedError, transfer.failedPrecondition, transfer.expired, transfer.unfunded, document.pending, document.processing, document.verified, document.rejected, service.pending, service.processing, service.succeeded, service.failed, service.cancelled