{ "event_types": [ { "event_type": "address.created", "summary": "Emitted when a wallet or bank account is added to an account." }, { "event_type": "address.ready", "summary": "Emitted when a wallet or bank account is ready to use." }, { "event_type": "transfer.created", "summary": "Emitted when a transfer (token order) is created." }, { "event_type": "transfer.completed", "summary": "Emitted when a transfer (token order) reaches complete status." }, { "event_type": "transfer.canceled", "summary": "Emitted when a transfer (token order) is canceled." }, { "event_type": "transfer.failed", "summary": "Emitted when a transfer (token order) reaches failed status." }, { "event_type": "payment.completed", "summary": "Emitted when a payment reaches complete status." }, { "event_type": "account.verification.documents_required", "summary": "Emitted when an account requires additional verification documents." }, { "event_type": "account.verification.completed", "summary": "Emitted when account verification reaches a completed state." } ]}
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:
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)
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.