### Item Created Webhook Example Source: https://docs.bridgeapi.io/docs/webhooks-events Triggered at the start of item creation when users enter credentials. Useful for tracking if a user leaves before synchronization completes. ```json { "content": { "item_id": 4568477, "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672" }, "timestamp": 1612782588323, "type": "item.created" } ``` -------------------------------- ### Authenticated API Call Example Source: https://docs.bridgeapi.io/docs/user-creation-authentication Example of how to make an authenticated API call using the obtained access token. ```APIDOC ## Authenticated API Request Example ### Description To perform authenticated API calls, include the `access_token` in the `Authorization` request header using the bearer authentication scheme. ### Method GET ### Endpoint /v3/aggregation/items?limit=100 ### Headers - **Bridge-Version**: 2025-01-15 - **Client-Id**: MY_CLIENT_ID - **Client-Secret**: MY_CLIENT_SECRET - **Authorization**: Bearer TOP_SECRET_ACCESS_TOKEN ### Request Example ```curl curl "https://api.bridgeapi.io/v3/aggregation/items?limit=100" \ -X GET \ -H 'Bridge-Version: 2025-01-15' \ -H 'Client-Id: MY_CLIENT_ID' \ -H 'Client-Secret: MY_CLIENT_SECRET' \ -H 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' ``` ### Notes - The `access_token` is valid for two hours (UTC+0) after issuance. - If the token expires, subsequent calls will result in an HTTP 401 error. ``` -------------------------------- ### Callback URL Parameters Example Source: https://docs.bridgeapi.io/docs/end-of-the-connect-flow This example demonstrates how a redirect URL might be enriched with parameters after a user completes or exits a Connect session. The available parameters depend on the success and step of the funnel. ```text MY_REDIRECT_URL?item_id=ITEM_ID&user_uuid=USER_UUID&success=false&step=sync_pending ``` -------------------------------- ### Accounts Information Example Response Source: https://docs.bridgeapi.io/docs/your-first-account-check Example JSON response containing user account details, including item ID, names, and account information like IBAN. ```json { "resources": [ { "item_id": 5869768, "first_name": "JEAN", "last_name": "DUPONT", "accounts": [ { "id": 27341559, "name": "Compte Courant de MR DUPONT", "type": "checking", "currency_code": "EUR", "provider_id": 6, "iban": "FR3312739000309854725191G90" } ] } ] } ``` -------------------------------- ### Account Updated Webhook Example (Data Access Disabled) Source: https://docs.bridgeapi.io/docs/webhooks-events This example demonstrates an account update event where data access has been disabled. ```json { "content": { "account_id": 22908770, "data_access": "disabled", "item_id": 4568477, "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672" }, "timestamp": 1729694049981, "type": "item.account.updated" } ``` -------------------------------- ### Example Transaction Response Source: https://docs.bridgeapi.io/docs/data-fetching This is an example of the JSON response when fetching updated transactions. It includes details for each transaction and pagination information. ```json { "resources": [ { "id": 33000191035700, "clean_description": "CB Mad Cours Marjane M.m G", "provider_description": "PAIEMENT PAR CARTE 09/11/2024 73.6 MAD COURS 0.09402 MARJANE M.M G", "amount": -6.92, "date": "2024-11-09", "booking_date": "2024-11-09", "transaction_date": "2024-11-09", "value_date": "2024-11-09", "updated_at": "2024-11-09T18:10:10.143Z", "currency_code": "EUR", "deleted": false, "category_id": 249, "operation_type": "card", "account_id": 48178050, "future": false }, { "id": 33000191035701, "clean_description": "CB Idfs G", "provider_description": "PAIEMENT PAR CARTE 25/11/2024 IDFS T2 G", "amount": -194, "date": "2024-11-25", "booking_date": "2024-11-25", "transaction_date": "2024-11-25", "value_date": "2024-11-25", "updated_at": "2024-11-25T16:10:10.144Z", "currency_code": "EUR", "deleted": false, "category_id": 247, "operation_type": "card", "account_id": 48178050, "future": false } ], "generated_at": "2024-11-25T16:41:18.533Z", "pagination": { "next_uri": "/v3/aggregation/transactions?after=MTczMjExOTAxMDE0MjozMzAwMDE5MTAzNTY5OQ&limit=50" } } ``` -------------------------------- ### Account Resource Example Source: https://docs.bridgeapi.io/docs/migration-guide-from-2019-to-2025 Illustrates the structure of an account resource, highlighting new and renamed fields like `last_refresh_status`, `data_access`, and `pro`. ```json { "id": 48546984, "name": "Crédit Immo", "balance": 427928, "updated_at": "2024-12-06T08:45:38.643Z", "last_refresh_status": "successful", // new "type": "loan", "currency_code": "EUR", "item_id": 10224815, "provider_id": 574, // renaming "loan_details": { "next_payment_date": "2025-01-01", "next_payment_amount": 2772, "maturity_date": "2042-01-01", "opening_date": "2022-01-01", "interest_rate": 2.42, "borrowed_capital": 500000, "repaid_capital": 72072, "remaining_capital": 427928, "total_estimated_interests": 103939.7239008639 }, "data_access": "enabled", // new "pro": false, // renaming } ``` -------------------------------- ### Webhook Example (Item Refresh) Source: https://docs.bridgeapi.io/docs/manage-your-transactions This is an example of a webhook payload for an 'item.refreshed' event, indicating that transaction data may have been updated. ```json { "content": { "account_types": "payment", "full_refresh": true, "refresh_trigger":"scheduler", "item_id": 7984384, "status_code": 0, "status_code_info": "OK", "user_uuid": "806eda23-a648-426d-b4b1-615035fc60be" }, "timestamp": 1686230311473, "type": "item.refreshed" } ``` -------------------------------- ### Account Updated Webhook Example (Data Access Enabled) Source: https://docs.bridgeapi.io/docs/webhooks-events Triggered on account updates, such as new transactions or balance changes. This example shows an account with data access enabled. ```json { "content": { "account_id": 22908770, "balance": 1678.12, "data_access":"enabled", "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": "item.account.updated" } ``` -------------------------------- ### Account Created Webhook Example Source: https://docs.bridgeapi.io/docs/webhooks-events Fired when a new account is detected for an item. This can occur simultaneously with 'Item created' or later if a user opens additional accounts. ```json { "content": { "account_id": 22908770, "balance": 1678.12, "item_id": 4568477, "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672" }, "timestamp": 1612782588323, "type": "item.account.created" } ``` -------------------------------- ### List Transactions (Initial GET) Source: https://docs.bridgeapi.io/docs/manage-your-transactions Use this GET request to retrieve transactions without the 'since' parameter. Store the 'updated_at' field from the response for subsequent updates. ```curl curl --request GET \ --url https://api.bridgeapi.io/v3/aggregation/transactions \ --header 'accept: application/json' \ --header 'Bridge-Version: 2025-01-15' \ --header 'Client-Id: MY_CLIENT_ID' \ --header 'Client-Secret: MY_CLIENT_SECRET' \ --header 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' ``` -------------------------------- ### Create Connect Session - GET Request Source: https://docs.bridgeapi.io/docs/connect-user-journey Use this cURL command to initiate a Connect session. Ensure you replace placeholder values with your actual credentials and token. This request is used for provider selection. ```curl curl --request GET \ --url https://api.bridgeapi.io/v3/agreggation/connect-sessions/ \ --header 'accept: application/json' \ --header 'Bridge-Version: 2025-01-15' \ --header 'Client-Id: MY_CLIENT_ID' \ --header 'Client-Secret: MY_CLIENT_SECRET' \ --header 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' \ { "provider_id": 574 } ``` -------------------------------- ### Transaction Resource Example Source: https://docs.bridgeapi.io/docs/migration-guide-from-2019-to-2025 Shows the structure of a transaction resource, including renamed fields like `provider_description`, `deleted`, and `future`, and the new `operation_type` field. ```json { "id": 24000190448633, "clean_description": "Vir Sepa M John Doe Virement Vers Livret A", "provider_description": "VIR SEPA M JOHN DOE - VIREMENT VERS LIVRET A", // renaming "amount": -200, "date": "2024-09-30", "booking_date": "2024-09-30", "updated_at": "2024-12-06T08:46:10.065Z", "currency_code": "EUR", "deleted": false, // renaming "category_id": 326, "operation_type": "transfer", // new "account_id": 48546980, "future": false // renaming } ``` -------------------------------- ### Item Resource Example Source: https://docs.bridgeapi.io/docs/items-status This JSON object represents an item resource, illustrating the structure and fields returned by the API, including status codes and their descriptions. ```json { "id": 10173907, "status": 402, "status_code_info": "invalid_creds", "status_code_description": "The banks credentials you provided don't allow us to synchronize your accounts. Please edit them (check for any typo).", "provider_id": 14, "account_types": "all", "last_successful_refresh": "2024-11-25T10:42:06.387Z" } ``` -------------------------------- ### Provider Resource Example (JSON) Source: https://docs.bridgeapi.io/docs/migration-guide-from-2019-to-2025 This JSON structure represents a provider resource, showcasing new fields and renamed properties compared to the previous version. It details aggregation and payment metadata, health status, and tags. ```json { "id": 120, "name": "Crédit Agricole Val de France", "country_code": "FR", "images": { "logo": "https://web.bridgeapi.io/img/banks-logo/fr/creditagricole-dsp2.png" }, "group_name": "Crédit Agricole", "capabilities": [ "aggregation", "account_check", "single_payment", "single_payment_scheduled", "bulk_payment_scheduled", "bulk_payment", "instant_single_payment" ], "payment_metadata": { "release_status": "active", "nb_max_transactions": 80, "max_size_label": 140, "multiple_dates_payments": true, "sender_iban_available": true, "provider_environments": [ "prod" ], "execution_status_available": true }, "aggregation_metadata": { "release_status": "active" }, "health_status": { "single_payment": { "status": "healthy" }, "aggregation": { "status": "healthy" } }, "tags": { "keywords": [ "ca" ], "segment": [ "b2c", "b2b" ], "region": [ "Val de France" ] } } ``` -------------------------------- ### Payment Link Creation Response Source: https://docs.bridgeapi.io/docs/create-a-payment-link-dynamic-beneficiary This is an example of the response received after successfully creating a payment link. It includes the payment link URL and a unique ID. ```json { "url": "https://pay.bridgeapi.io/link/9dcf522ce3663efc598f573634531eb3fccbbcdde0bc5d674c95c0740feb0ec6", "id": "3ae3a3d6-f9d5-445e-b8fe-2db1ab8c39d8" } ``` -------------------------------- ### Create Payment Request with Execution Date Source: https://docs.bridgeapi.io/docs/initiate-your-first-payment-1 This cURL example shows how to schedule a payment for a future date by including the `execution_date` field. Note that certain banks have restrictions on how far in advance payments can be scheduled. ```curl curl 'https://api.bridgeapi.io/v3/payment/payment-requests' \ -X POST \ ``` -------------------------------- ### Item Refreshed Webhook Example Source: https://docs.bridgeapi.io/docs/webhooks-events Fired each time an item is refreshed. Use this to monitor status changes or errors post-refresh. Includes details on refresh type and status. ```json { "content": { "account_types":"payment", "full_refresh": false, "refresh_trigger":"scheduler", "item_id": 4568565, "status_code": 0, "status_code_info": "ok",, "authentication_expires_at": "2025-09-04T10:25:35Z", "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672" }, "timestamp": 1612783550980, "type": "item.refreshed" } ``` -------------------------------- ### Create Payment Request to Dynamic Beneficiary Source: https://docs.bridgeapi.io/docs/initiate-your-first-payment-1 This cURL example demonstrates how to create a payment request with a specified beneficiary, including their name and IBAN. This is useful when payments are not always to the same recipient. ```curl curl 'https://api.bridgeapi.io/v3/payment/payment-requests' \ -X POST \ -H 'Bridge-Version: 2025-01-15' \ -H 'Client-Id: MY_CLIENT_ID' \ -H 'Client-Secret: MY_CLIENT_SECRET' -H 'Content-Type: application/json' \ -d '{ "callback_url": "https://my-callback-url.com:8080/pay", "transactions": [ { "amount": 99.5, "currency": "EUR", "label": "Payment label", "beneficiary": { "first_name": "Test", "last_name": "Name", "iban": "FR2310096000301695931368H67" }, "client_reference": "12345678-AZERTY", "end_to_end_id": "12345678-AFERS" ], "user": { "first_name": "Firstname", "last_name": "Lastname", "external_reference": "AEF142536-890" }, "provider_id": 6 }' ``` -------------------------------- ### Example paginated API request Source: https://docs.bridgeapi.io/docs/basics Use this cURL command to fetch paginated transaction data. Ensure you include the correct Bridge-Version, Client-Id, Client-Secret, and Authorization header. ```curl curl "https://api.bridgeapi.io/v3/transactions?limit=2" \ -X GET \ -H 'Bridge-Version: 2025-01-15' \ -H 'Client-Id: MY_CLIENT_ID' \ -H 'Client-Secret: MY_CLIENT_SECRET' \ -H 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' ``` -------------------------------- ### Item Resource Example Source: https://docs.bridgeapi.io/docs/migration-guide-from-2019-to-2025 This JSON object represents an item resource, showcasing new fields like `account_types`, `last_successful_refresh`, and `created_at`. It also indicates renamed fields such as `provider_id`. ```json { "id": 10215554, "status": 1010, "status_code_info": "sca_required_webview", "status_code_description": "Your bank requires you to renew your account synchronization to confirm your identity.", "provider_id": 122, "account_types": "all", "last_successful_refresh": "2024-12-06T06:56:35.191Z", "last_try_refresh": "2024-12-06T06:56:14.000Z", "created_at": "2024-12-04T08:51:54.770Z" } ``` -------------------------------- ### `item.refreshed` Webhook Example Source: https://docs.bridgeapi.io/docs/migration-guide-from-2019-to-2025 This JSON payload demonstrates the `item.refreshed` webhook, including new fields such as `account_types` and `refresh_trigger`. It provides details about the refresh event, including its trigger and status. ```json { "content": { "account_types": "all", "full_refresh": true, "item_id": 10215554, "refresh_trigger": "connect", "status_code": 0, "status_code_info": "OK", "user_uuid": "24b0a87a-96ba-4d96-b39f-244fcb13969c" }, "timestamp": 1733302472225, "type": "item.refreshed" } ``` -------------------------------- ### Create Payment Link with Callback URL Source: https://docs.bridgeapi.io/docs/create-your-first-payment-api Use this example to create a payment link and redirect users to your specified callback URL upon payment completion. Ensure all required headers and the JSON body are correctly formatted. ```json curl 'https://api.bridgeapi.io/v3/payment/payment-links' \ -X POST \ -H 'Bridge-Version: 2025-01-15' \ -H 'Content-Type: application/json' \ -H 'Client-Id: MY_CLIENT_ID' \ -H 'Client-Secret: MY_CLIENT_SECRET' \ -d $'{ "user": { "first_name": "Thomas", "last_name": "Pichet", "external_reference": "REF-USER-1234_AZ" }, "callback_url": "https://myshop.com", "client_reference": "ABCDE_FG-HI_12345", "transactions": [ { "amount": 120.98, "currency": "EUR", "label": "Refund 123456", "end_to_end_id": "E2E_ID-1234" } ] }' ``` -------------------------------- ### Get Payer's IBAN from Payment Request Source: https://docs.bridgeapi.io/docs/create-a-refund-1 Retrieve the payer's IBAN by calling the Get a single payment request endpoint. This IBAN is crucial for initiating a refund. ```json { "id": "e959dccd632c49d7922a766e946ad9e9", "status": "ACSC", "user": { "name": "Firstname Lastname", "external_reference": "AEF142536-890", "ip_address": "0.0.0.0" }, "sender": { "name": "John doe", "iban": "FR183490204820028402" // <------ Get this value }, "transactions": [ { "amount": 99.5, "currency": "EUR", "label": "Payment label", "id": "79e61d0c29b1491196bc0c39f27b5bb8", "status": "ACSC", "beneficiary": { "first_name": "Test", "last_name": "Name", "iban": "FR2310096000301695931368H67" }, "client_reference": "12345678-AZERTY" } ] } ``` -------------------------------- ### List Transactions (GET with 'since') Source: https://docs.bridgeapi.io/docs/manage-your-transactions After receiving a webhook or performing a refresh, use this GET request with the 'since' parameter set to the previously stored 'updated_at' timestamp to fetch only the updated transactions. ```curl curl --request GET \ --url 'https://api.bridgeapi.io/v3/aggregation/transactions?limit=50&since=2024-11-24T12%3A46%3A18.971Z' \ --header 'accept: application/json' \ --header 'Bridge-Version: 2025-01-15' \ --header 'Client-Id: MY_CLIENT_ID' \ --header 'Client-Secret: MY_CLIENT_SECRET' \ --header 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' ``` -------------------------------- ### Create Connect Session with Callback URL Source: https://docs.bridgeapi.io/docs/end-of-the-connect-flow Use this cURL command to create a Connect session, specifying a callback URL for user redirection upon completion or exit. Ensure your 'Client-Id', 'Client-Secret', and 'Authorization' token are correctly set. ```curl curl --request POST \ --url https://api.bridgeapi.io/v3/aggregation/connect-sessions \ --header 'Bridge-Version: 2025-01-15' \ --header 'accept: application/json' \ --header 'content-type: application/json' \ --header 'Client-Id: MY_CLIENT_ID' \ --header 'Client-Secret: MY_CLIENT_SECRET' \ --header 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' \ --data \ '{ "user_email": "john.doe@acme.com", "callback_url": "https://www.acme.com" } ' ``` -------------------------------- ### Pagination Source: https://docs.bridgeapi.io/docs/basics Explains how to paginate through lists of resources using cursor-based pagination. ```APIDOC ## Pagination All endpoints that return a list of objects support pagination, with pagination information available within a pagination object. Bridge uses a cursor-based pagination via the `after` parameter. > ❗️ Do not forge or store the `after` cursors, as they may change over time. > 📘 By default, all objects are ordered and paginated in reverse chronological order, with a default limit of 50. ### Options * `limit` (*integer*) - Number of results per call. Accepted values: 1 - 500. Default 50. * `after` (*string*) - Cursor pointing to the start of the desired set. ``` -------------------------------- ### Payment Link Updated Webhook Example Source: https://docs.bridgeapi.io/docs/fund-information-status This JSON payload represents a webhook notification for a payment link update. It includes the payment link ID, its status, and crucially, the fund status, which is 'paid' in this example. ```json { "content": { "payment_link_id": "64e61033-be1e-4dd3-9564-f03e8a5b6874", "payment_link_status": "completed", "payment_link_client_reference": "INV124", "payment_link_fund_status": "paid" }, "timestamp": 1644507383234, "type": "payment.link.updated" } ``` -------------------------------- ### GET /v3/transactions Source: https://docs.bridgeapi.io/docs/basics Retrieves a paginated list of transactions. The response includes transaction resources and pagination details. ```APIDOC ## GET /v3/transactions ### Description Retrieves a paginated list of transactions. The response includes transaction resources and pagination details. ### Method GET ### Endpoint /v3/transactions ### Query Parameters - **limit** (integer) - Optional - Specifies the number of results to return per page. ### Request Headers - **Bridge-Version** (string) - Required - The API version to use (e.g., '2025-01-15'). - **Client-Id** (string) - Required - Your application's client ID. - **Client-Secret** (string) - Required - Your application's client secret. - **Authorization** (string) - Required - Bearer token for authentication (e.g., 'Bearer TOP_SECRET_ACCESS_TOKEN'). ### Request Example ```curl curl "https://api.bridgeapi.io/v3/transactions?limit=2" \ -X GET \ -H 'Bridge-Version: 2025-01-15' \ -H 'Client-Id: MY_CLIENT_ID' \ -H 'Client-Secret: MY_CLIENT_SECRET' \ -H 'Authorization: Bearer TOP_SECRET_ACCESS_TOKEN' ``` ### Response #### Success Response (200) - **resources** (array) - An array of transaction objects. - **pagination** (object) - An object containing pagination information. - **next_uri** (string) - A URI to fetch the next page of results. Can be null if no more results are available. #### Response Example ```json { "resources": [ { "id": 9 }, { "id": 8 } ], "pagination": { "next_uri": "/v3/transactions?limit=2&after=MzIx" } } ``` ``` -------------------------------- ### Create Bulk Payment Link Request Body Source: https://docs.bridgeapi.io/docs/bulk-payment-link Use this JSON structure to initiate a bulk payment. Include user details, transaction information with beneficiary IBANs and amounts, and a callback URL. ```json { "user": { "first_name": "John", "last_name": "DOE", "email": "john.doe@bridgeapi.io" }, "transactions": [ { "currency": "EUR", "beneficiary": { "iban": "FR4014508000406764668712J28", "first_name": "John", "last_name": "Dupont" }, "amount": 100 }, { "currency": "EUR", "beneficiary": { "iban": "FR2214508000408744765254O74", "company_name": "Bridge" }, "amount": 200 } ], "callback_url": "https://www.bridgeapi.io/" } ``` -------------------------------- ### Transaction Example with Operation Type 'card' Source: https://docs.bridgeapi.io/docs/operation-types This JSON object represents a typical card transaction, showing the 'operation_type' as 'card'. ```json { "id": 33000191035701, "clean_description": "CB Idfs G", "provider_description": "PAIEMENT PAR CARTE 25/11/2024 IDFS T2 G", "amount": -194, "date": "2024-11-25", "booking_date": "2024-11-25", "transaction_date": "2024-11-25", "value_date": "2024-11-25", "updated_at": "2024-11-25T16:10:10.144Z", "currency_code": "EUR", "deleted": false, "category_id": 247, "operation_type": "card", "account_id": 48178050, "future": false } ``` -------------------------------- ### Fetch Transactions with Filter Source: https://docs.bridgeapi.io/docs/financial-data-aggregation Retrieve new or updated transactions efficiently by using the 'since' filter with the GET /v3/aggregation/transactions endpoint. ```bash curl -X GET \ https://api.bridgeapi.io/v3/aggregation/transactions?item_id=your-item-id&since=2023-10-26T10:00:00Z \ -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' ``` -------------------------------- ### Item Deleted Webhook Example Source: https://docs.bridgeapi.io/docs/webhooks-events This event is triggered on item deletion, commonly used for data privacy automation like GDPR. ```json { "content": { "item_id": 4568477, "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672" }, "timestamp": 1612782588323, "type": "item.deleted" } ``` -------------------------------- ### Create Payment Link with Callback URL Source: https://docs.bridgeapi.io/docs/first-payment-link-from-the-api Use this cURL command to create a payment link. Provide a callback URL to redirect users after payment. Ensure to replace placeholders with your actual credentials and desired values. ```json curl 'https://api.bridgeapi.io/v3/payment/payment-links' \ -X POST \ -H 'Bridge-Version: 2025-01-15' \ -H 'Content-Type: application/json' \ -H 'Client-Id: MY_CLIENT_ID' \ -H 'Client-Secret: MY_CLIENT_SECRET' \ -d $'{ "user": { "first_name": "Thomas", "last_name": "Pichet", "external_reference": "REF-USER-1234_AZ" }, "callback_url": "https://myshop.com", "client_reference": "ABCDE_FG-HI_12345", "transactions": [ { "amount": 120.98, "currency": "EUR", "end_to_end_id": "E2E_ID-1234" } ] }' ``` -------------------------------- ### Account Deleted Webhook Example Source: https://docs.bridgeapi.io/docs/webhooks-events Triggered when a bank account is no longer updated by the bank. If the account is updated again, 'item.account.updated' events may follow. ```json { "content": { "user_uuid": "4568f180-03ea-4915-af47-f266f06b6949", "item_id": 8390176, "account_id": 38439071 }, "timestamp": 1694506737325, "type": "item.account.deleted" } ``` -------------------------------- ### User Deleted Webhook Example Source: https://docs.bridgeapi.io/docs/webhooks-events This event is triggered on user deletion, often used for GDPR automation. It includes the user's UUID. ```json { "content": { "user_uuid": "766b2f5d-a942-492c-9ea7-2e5aa88cb672" }, "timestamp": 1612782588323, "type": "user.deleted" } ``` -------------------------------- ### Configure BridgeAPI MCP Server for Cursor Source: https://docs.bridgeapi.io/docs/bridgeapi-for-ai-agents-llms Add this JSON configuration to your `~/.cursor/mcp.json` file to enable Cursor to access BridgeAPI documentation via MCP. ```json { "mcpServers": { "bridgeapidocs": { "url": "https://docs.bridgeapi.io/mcp" } } } ``` -------------------------------- ### Create Bridge Connect Session Source: https://docs.bridgeapi.io/docs/financial-data-aggregation Initiate the Bridge Connect flow by creating a session with POST /v3/aggregation/connect-sessions. Ensure the access token is included and a callback URL is provided for redirection. ```bash curl -X POST \ https://api.bridgeapi.io/v3/aggregation/connect-sessions \ -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "callback_url": "https://your-app.com/bridge/callback", "user_email": "user@example.com" }' ```