Skip to main content

List event types

Requires webhooks:read. Example:
Response:

Create subscription

Requires webhooks:write. Use an Idempotency-Key header. Request:
The events array accepts concrete event types (e.g., transfer.completed) and namespace wildcards of the form <namespace>.* (e.g., transfer.*, payment.*, account.*). A wildcard subscribes to every event in that family, including any future events Brale adds. Wildcards are supported for all event families — not just transfer. Wildcard request example:
Response:

List subscriptions

Requires webhooks:read. Response:

Get subscription

Requires webhooks:read. The sharedSecret is not returned.

Update subscription

Requires webhooks:write. Use an Idempotency-Key header. Request:
Important: if events is included, it replaces the entire event set. It does not merge with existing events. Note: the subscription API has an intentional path-shape inconsistency:
  • GET /accounts/{account_id}/webhooks/{subscription_id} (get one)
  • PATCH /accounts/{account_id}/webhooks/subscriptions/{subscription_id} (update)
  • DELETE /accounts/{account_id}/webhooks/subscriptions/{subscription_id} (archive)

Subscribe to refund events

Brale reports refunds with transfer.refunding (the refund process has started) and transfer.refunded (the refund has completed). See Refund events. If your subscription already includes transfer.*, it receives both refund events. You do not need to change it. To subscribe by name on a new subscription, include both event types:
To add them to an existing subscription, first get the subscription and read its current events. Then send PATCH with the full list: every existing event type plus the two refund events. For example, if the subscription currently has ["transfer.completed", "transfer.failed"]:
events replaces the entire event set. If you send only ["transfer.refunding", "transfer.refunded"], the subscription stops receiving every other event it had.

Archive subscription

Requires webhooks:write. Archiving stops future deliveries. Delivery history is retained.

List delivery attempts

Requires webhooks:read. Optional pagination:
Do not send both page[after] and page[before]. Delivery logs are useful for debugging:
  • Whether Brale attempted delivery
  • What HTTP status your endpoint returned
  • Whether a delivery was retried
  • Failure messages
  • Attempt numbers