Easily Integrate Bridgeapi Webhooks with your application.

https://docs.bridgeapi.io/docs/webhooks-events

Steps to receive Bridgeapi Webhooks

  • Sign up for your free Hooky account.
  • Create a new Webhook Source, and select Bridgeapi. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
  • Step 1
  • Step 2
  • Once a webhook is received from Bridgeapi, you'll see it under the Live Logs section of your webhook source.
  • Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Save countless hours integrating Bridgeapi webhooks into your application.

Integrating Bridgeapi Webhooks Using Javascript

Integrating Bridgeapi webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.

Integrating Bridgeapi Webhooks Using Ruby

Integrating Bridgeapi webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.

Configuring Bridgeapi Webhook Authentication

Here's how it works

Supported Bridgeapi Webhook Events

item.created

This event is triggered at the very beginning of an item creation, when users enter their credentials in Bridge Connect and then click on "Add your account". You can use it, for example, to know if a user quitted the Bridge Connect before the end of the synchronization.

item.account.created

This event is triggered when we detect a new account on an item. It can be triggered at the same time as Item created but also later, for example if users opened a new account with their bank.

item.account.updated

This event is triggered each time we detect an update on an account

item.account.updated

Each time an item is refreshed, this event is triggered. You can use it to check if an item's status has changed, or to know right after a refresh that an item is now in error. The field full_refresh indicates you if we fetched the item's full history or not.

payment.transaction.created

This event is triggered when a payment transaction is created.

payment.transaction.updated

This event is triggered when a payment transaction is updated.

payment.link.updated

This event is triggered when a Payment Link is updated.

transfer.account.created

This event is triggered when a new sender account has been detected for an item.

transfer.account.updated

This event is triggered when a sender account has been updated (support has changed or account has been deleted).

transfer.created

This event is triggered when a transfer has been created (when a user confirm the first step of the Bridge Transfer journey).

transfer.updated

This event is triggered when a transfer has been updated.