Overview
Webhook endpoints are HTTPS URLs Bitnob Enterprise POSTs event payloads to. Register a webhook, choose which event types it receives, and verify each delivery with its signing secret. Individual delivery attempts are tracked as Events — use those to audit and retry failed deliveries.
List Webhooks
Use Case
Returns all webhook endpoints registered for the organization.
Webhook Fields
Always `webhook`.
Stable identifier for the webhook. Pass it to the get, update, delete, and rotate-secret endpoints, and as `webhook_id` on the Events endpoints.
HTTPS URL deliveries are POSTed to.
The event type (or types) this webhook is subscribed to.
Lifecycle state: `active` (delivering) or `inactive` (soft-deleted).
Last 4 characters of the signing secret, for at-a-glance identification. The full secret is only returned on create and rotate.
RFC 3339 timestamp of when the webhook was created.
RFC 3339 timestamp of the most recent update.
Create Webhook
Use Case
Registers a new webhook endpoint for event delivery. The response includes the signing secret once — store it before the response closes; it can be rotated but never retrieved again.
Request Body
HTTPS URL deliveries will be POSTed to. Must answer `2xx` within the delivery timeout or the event is retried with backoff.
Event types this webhook should receive (e.g. `transaction.completed`, `wallet.created`). Omit to receive all event types.
Create Webhook Response
The full signing_secret is returned only on this response. Store it immediately — subsequent reads only expose signing_secret_last4. Use it to verify the signature header on every delivery.
The response carries the same webhook fields as List Webhooks, plus the plaintext signing_secret.
Get Webhook
Use Case
Returns a single webhook endpoint by ID.
Path Parameters
The webhook to retrieve.
The response is a single webhook object — same field shape as each entry in List Webhooks. The full signing secret is never returned here, only signing_secret_last4.
Update Webhook
Use Case
Updates a webhook endpoint's URL. The signing secret is unchanged — use [Rotate Signing Secret](#Rotate Signing Secret) if you need a new one.
Request Body
Replacement HTTPS delivery URL. Future events are POSTed here instead of the previous URL.
Returns the updated webhook object — same field shape as Get Webhook, with a fresh updated_at.
Delete Webhook
Use Case
Soft-deletes a webhook. Pending deliveries are cancelled and the webhook stops receiving events.
Path Parameters
The webhook to delete.
Returns HTTP 200 on success. The webhook's status flips to inactive; historical events remain queryable for audit.
Rotate Signing Secret
Use Case
Generates a new signing secret for the webhook. The new secret is returned once; the previous secret stops verifying deliveries immediately.
Path Parameters
The webhook whose secret to rotate.
The new signing_secret is returned only on this response. Store it before the response closes — the old secret stops verifying signatures the instant the rotation completes.