Skip to main content
Bridge now supports webhook events for the following categories:
  • customer
  • kyc_link
  • liquidation_address.drain
  • static_memo.activity
  • transfer
  • virtual_account.activity
  • bridge_wallet.activity
  • card_account
  • card_transaction
  • posted_card_account_transaction
  • card_withdrawal
  • external_acccount
Additional event categories will be added soon.

💬 Feedback welcome — Let us know which event types you’d like to see prioritized next.

Supported Event Types

Event Object Schema

Each webhook payload includes:

Event Object Schema Reference

The event_object field contains the full resource data, matching the structure returned by corresponding API endpoints. Webhooks and API responses use identical rendering logic, ensuring schema consistency.

Supported Mutation Types

Each event can have the following mutation types:
  • created
  • updated
  • updated.status_transitioned (for state transitions like KYC or Transfer status)
  • deleted (if applicable)

Examples

For cards-related webhook events, see the scenarios outlined in this cards-specific webhook scenarios page.

Transfers

Bridge Wallet Activity

To receive Bridge Wallet activity events, create or update a webhook endpoint subscribed to bridge_wallet.activity.
Bridge Wallet activity webhooks deliver the same object returned by the Bridge Wallet transaction history API.

Virtual Accounts

Below is a creation event for a Virtual Account Activity event object

Customers

Initial creation via a KYC link before the customer has taken any action.