Authentication
All webhook endpoints require a JWT bearer token. Managing webhooks is restricted to organization Owner and Admin roles (read access is also available to Issuer and Verifier roles).Base path
All webhook endpoints are rooted at/webhooks.
Register a webhook
POST /webhooks/orgs/:orgId/register
Register a webhook URL for an organization.
Required roles: owner, admin
Path parameters
string
required
UUID of the organization to register the webhook for.
Request body
string
required
A valid URL that CREDEBL will POST event payloads to.
string
Optional shared secret used for payload verification. Must be at least 16 characters long.
Example
Response
number
201 on success.string
Confirmation message.
object
The registered webhook record.
Get webhook URL
GET /webhooks/orgs/webhookurl
Retrieve the registered webhook URL for an organization or tenant.
Required roles: owner, admin, issuer, verifier
Query parameters
string
Organization ID to look up the webhook for.
string
UUID of a specific tenant to look up.
Example
Update a webhook
PATCH /webhooks/orgs/:orgId
Update the webhook URL or secret for an organization.
Required roles: owner, admin
Path parameters
string
required
UUID of the organization whose webhook to update.
Request body
string
New webhook endpoint URL.
string
New shared secret. Must be at least 16 characters long.
Example
Webhook payload structure
The platform POSTs event data to your registered URL using theWebhookResponseDto structure:
string
The URL the payload was delivered to.
object
The event-specific payload from the underlying Aries agent or platform service.
The exact shape of
data depends on the event type (connection, credential, or proof) and
the DIDComm protocol used. Inspect the payloads your endpoint receives to understand the
structure for your specific setup.