Bridge API Documentation

Bridge Documentation

Welcome to our API documentation!

We're happy to share with you our new API 2021 version! Please check our Product Changelog to know the main changes.

You'll find comprehensive guides and documentation to help you start working with Bridge as quickly as possible, as well as support if you get stuck.

Let's jump right in!

Get Started

Webhooks events

📘

Please use real items to test the webhooks events

For now our bank test Simulator is not reliable to test the webhooks, please sync other bank accounts to test them.

There are four events available.

1. 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.

Example:

{
  "content": {
    "item_id": 4568477,
    "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672"
  },
  "timestamp": 1612782588323,
  "type": "ITEM_CREATED"
}

2. 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.

{
  "content": {
    "account_id": 22908770,
    "balance": 1678.12,
    "item_id": 4568477,
    "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672"
  },
  "timestamp": 1612782588323,
  "type": "ACCOUNT_CREATED"
}

3. Account updated

This event is triggered each time we detect an update on an account. An update can be:

  • transactions have been added
  • transactions have been deleted
  • transactions have been updated
  • balance has changed

Example:

{
  "content": {
    "account_id": 22908770,
    "balance": 1678.12,
    "item_id": 4568477,
    "nb_deleted_transactions": 0,
    "nb_new_transactions": 15,
    "nb_updated_transactions": 0,
    "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672"
  },
  "timestamp": 1612782588323,
  "type": "ACCOUNT_UPDATED"
}

4. Item refreshed

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.

Example:

{
  "content": {
    "full_refresh": false,
    "item_id": 4568565,
    "status_code": 1003,
    "status_code_info": "",
    "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672"
  },
  "timestamp": 1612783550980,
  "type": "ITEM_REFRESHED",
}

Updated 5 months ago

Webhooks events


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.