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.

List Webhooks

Webhook Fields
1
objectstring

Always `webhook`.

2
idstring (uuid)

Stable identifier for the webhook. Pass it to the get, update, delete, and rotate-secret endpoints, and as `webhook_id` on the Events endpoints.

3
urlstring (url)

HTTPS URL deliveries are POSTed to.

4
event_typestring

The event type (or types) this webhook is subscribed to.

5
statusstring

Lifecycle state: `active` (delivering) or `inactive` (soft-deleted).

6
signing_secret_last4string

Last 4 characters of the signing secret, for at-a-glance identification. The full secret is only returned on create and rotate.

7
created_atstring (date-time)

RFC 3339 timestamp of when the webhook was created.

8
updated_atstring (date-time)

RFC 3339 timestamp of the most recent update.

List Webhooks Response

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.

Create Webhook

Request Body
1
urlstring (url)Required

HTTPS URL deliveries will be POSTed to. Must answer `2xx` within the delivery timeout or the event is retried with backoff.

2
eventsstring[]

Event types this webhook should receive (e.g. `transaction.completed`, `wallet.created`). Omit to receive all event types.

Example Payload

Create Webhook Response
One-time secret

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.

Create Webhook Response

Get Webhook

Use Case

Returns a single webhook endpoint by ID.

Get Webhook

Path Parameters
1
idstring (uuid)Required

The webhook to retrieve.

Same shape as List Webhooks

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.

Get Webhook Response

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.

Update Webhook

Request Body
1
urlstring (url)

Replacement HTTPS delivery URL. Future events are POSTed here instead of the previous URL.

Same shape as Get Webhook

Returns the updated webhook object — same field shape as Get Webhook, with a fresh updated_at.

Example Payload

Delete Webhook

Use Case

Soft-deletes a webhook. Pending deliveries are cancelled and the webhook stops receiving events.

Delete Webhook

Path Parameters
1
idstring (uuid)Required

The webhook to delete.

Response

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.

Rotate Signing Secret

Path Parameters
1
idstring (uuid)Required

The webhook whose secret to rotate.

One-time secret

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.

Rotate Signing Secret Response
Did you find this page useful?