Recurring expenses
Reference information for our recurring expenses webhook events.
Historical update
With single links, you can choose to add fetch_resources: ["RECURRING_EXPENSES", "TRANSACTIONS"]
when you create the link so that Belvo asynchronously performs an enrichment analysis of the user's transactions to identify any recurring expenses. You will receive a historical_update
notification whenever the recurring expenses analysis is available for you to access.
{
"webhook_id": "aadf41a1fc8e4f79a49f7f04027ac999",
"webhook_type": "RECURRING_EXPENSES",
"webhook_code": "historical_update",
"link_id": "16f68516-bcbc-4cf7-b815-c500d4204e28",
"request_id": "4363b08b-51eb-4350-9c74-5df5ac92a7f6",
"external_id": "your_external_id",
"data": {
"total_recurring_expenses": 23 // Count of identified recurring expenses.
}
}
Once you receive the notification, you can get further details by making the following request:
curl --request GET 'https://api.belvo.com/api/recurring-expenses/?link={id}' \
-u [Secret Key ID]:[Secret Key PASSWORD]
Where:
{id}
is thelink_id
you receive in yourhistorical_update
notification.
Updated 2 months ago