Belvo API Docs (1.218.0)

Introduction

Reach new audiences and convert more users by easily and safely connecting to their financial data, understanding their behavior and enabling instant payments with open finance. Through our API, you can access:

Available Information and Payment Methods

Belvo is an open banking API for Latin America that allows companies to access banking and fiscal information in a secure as well as agile way.

Through our API, you can access:

  • Banking Information in Brazil
  • Employment Information in Brazil
  • Employment Information in Mexico
  • Fiscal Information in Mexico
  • Fiscal Information in Chile

You can also use our API to make payments in:

  • Brazil
  • Mexico

Data Dictionaries

If you woud like the response documentation in Excel or CSV form, please download them from our public GitHub Reposiitory: Belvo Open Finance Data Dictionaries.

Our EXCEL and CSV files are additionally localized into Spanish and Portuguese (Brazil).

Environments

We currently offer two environments: sandbox and production.

Sandbox

Available for:

  • 🟢 Aggregation and Enrichment
  • ⚪️ Payment Initiation

Use our Sandbox environment to build your integration. We offer dummy data that mimics that of real-world use cases, which means you can test out all the endpoints, use the widget, and implement webhooks - just as you would with real-world data!

All you need to get started with the Sandbox environment is to get your API keys. We really recommend that you start creating your integration in this environment.

Production

Available for:

  • 🟢 Aggregation and Enrichment
  • 🟢 Payment Initiation

After you have tested your integration in the Sandbox environment and are ready to go live, you'll need to request access to our Production environment. After you request access, our Sales Team will get in contact with you to schedule a meeting just to ensure your needs are met, and then you'll just need to go through a certification process with one of our engineers to make sure that your integration is running optimally. To prepare for the certification meeting, just follow our Integration checklist.

Once your integration is certified, all you'll need to do is:

  • Request Production API keys (and change your Sandbox API keys in the code to these new ones).
  • Change the base URL that you make requests to from sandbox.belvo.com to api.belvo.com.
  • If you're using webhooks, make sure to set a Production URL for your webhooks.

Response codes

We use the following HTTP status code in the response depending on the success or failure:

Status CodeDescription
200✅ Success - The content is available in the response body.
201✅ Success - The content was created successfully on Belvo.
204✅ Success - No content to return.
400❌ Bad Request Error - Request returned an error, detail in the content.
401❌ Unauthorized - The Belvo credentials provided are not valid.
404❌ Not Found - The resource you try to access cannot be found.
405❌ Method Not Allowed - The HTTP method you are using is not accepted for this resource.
408❌ Request Timeout - The request timed out and was terminated by the server.
428❌ MFA Token Required - MFA token was required by the institution to connect.
500❌ Internal Server Error - The detail of the error is available in the response body.

Error handling

Belvo API errors are returned in JSON format. For example, an error might look like this:

[
    {
      "request_id": "a6e1c493d7a29d91aed4338e6fcf077d",
      "message": "This field is required.",
      "code": "required",
      "field": "link"
    }
]

Typically, an error response will have the following parameters:

  • request_id: a unique ID for the request, you should share it with the Belvo support team for investigations.
  • message: human-readable description of the error.
  • code: a unique code for the error. Check the table below to see how to handle each error code.
  • field (optional): The specific field in the request body that has an issue.

Request identifier

When you need help with a specific error, include the request identifier (request_id) in your message to the Belvo support team. This will speed up investigations and get you back up and running in no time at all.

Error codes and troubleshooting

For a full list of errors and how to troubleshoot them, please see our dedicated Error Handling article.

Retry policy

50x errors

Implement an automated exponential backoff of up to five retries. We recommend using a base interval of three seconds with a factor of two. For example, the first retry should be after three seconds, the second retry after six seconds (2 * 3), the third retry after 12 seconds (2 * 6), the fourth retry after 24 seconds (2 * 12), and the fifth retry after 48 seconds (2 * 24).

40x errors

You should not retry making requests if you receive a 40x response, as this is a client error.

The only exception is the “Too Many Sessions” error, as it means that your end-user is accessing the account from another browser at the same time. In this case, please implement the same retry policy as with 50x errors.

Deprecated fields

In our schema, you may see that a field has been marked as deprecated. This means that this field is no longer maintained by the Belvo team. You may still receive data for this field depending on the institution, however, you should not rely on this field.

OpenAPI: required and nullable fields

In our API specification, you'll see that some response parameters will have a required annotation. According to the OpenAPI specification, when a response parameter is marked as required, this means that the response key must be returned. However, the value of that response parameter can be null.

📘 Info

In short, any response parameter marked as required will be returned by our API, but the value can be set to null.

Download OpenAPI description
BelvoOpenApiSpec.json
BelvoOpenApiSpec.yaml
Overview
URL

https://developers.belvo.com

Need help?

support@belvo.com

Languages
Servers
Mock server

https://developers.belvo.com/_mock/apis/belvoopenapispec/

Sandbox

https://sandbox.belvo.com/

Institutions

An institution is an entity that Belvo can access information from. It can be a:

  • bank institution, such as Nubank Brazil.
  • fiscal institution, such as the Servicio de Administración Tributaria (SAT) in Mexico.
  • employment institutions, such as Instituto Mexicano del Seguro Social (IMSS) in Mexico or Instituto Nacional do Seguro Social (INSS) in Brazil.
Operations

Links

A Link is a set of credentials associated to an end-user's access to an institution. You will need to register a Link before accessing information from that specific end-user, such as account or transaction details.

We recommend using the Belvo Hosted Widget to manage the connection process.

Operations

Widget Access Token

Operations

Consents

A consent is a permission given by the end user to access their financial data in the Open Finance Network in Brazil.

Operations

Consents Object (Brazil)

The OFDA consents schema

idstring(uuid)

Belvo's unique identifier for the current item.

Example: "0d3ffb69-f83b-456e-ad8e-208d0998d71d"
display_namestring or null<= 128 characters^[\w\W]{0,128}$

The full name of the individual that initiated the consent, as provided by the institution.

Example: "Jack Oswald White"
document_numberstring

The document number (CPF) of the individual.

Example: "76109277673"
belvo_institution_namestring

Belvo's name for the open finance institution that the consent is related to.

Example: "ofmockbank_br_retail"
expired_atstring(date-time)

The ISO-8601 timestamp when the consent will expire. In the case that undefined_consent_expiration is true, this field will be null.

Example: "2021-02-27T13:01:41.941Z"
undefined_consent_expirationboolean

Indicated whether the consent is for an undefined period, that is, that there is no expiration for the consent.

Example: false
created_atstring(date-time)

The ISO-8601 timestamp of when the data point was created in Belvo's database.

Example: "2022-02-09T08:45:50.406032Z"
statusstring or null

The status of the consent in the open finance network. Can be either:

  • AUTHORISED: The consent is still valid for use until the expired_at date.
  • AWAITING_AUTHORISATION_CONFIRMATION: The user must confirm within their institution.
  • AWAITING_AUTHORISATION: The user has been redirected to their institution to grant consent.
  • REJECTED: The user has not granted consent within their institution.
  • EXPIRED: The consent has expired as of the expired_at date.
  • null
Enum"AUTHORISED""AWAITING_AUTHORISATION_CONFIRMATION""AWAITING_AUTHORISATION""REJECTED""EXPIRED"null
Example: "AUTHORISED"
permissionsobject

Details regarding the permissions attached to the consent.

{
  "id": "0d3ffb69-f83b-456e-ad8e-208d0998d71d",
  "display_name": "Jack Oswald White",
  "document_number": "76109277673",
  "belvo_institution_name": "ofmockbank_br_retail",
  "expired_at": "2021-02-27T13:01:41.941Z",
  "undefined_consent_expiration": false,
  "created_at": "2022-02-09T08:45:50.406032Z",
  "status": "AUTHORISED",
  "permissions": {
    "ACCOUNTS": [ … ],
    "CREDIT_CARDS": [ … ],
    "CREDIT_OPERATIONS": [ … ],
    "REGISTER": [ … ],
    "RESOURCES": [ … ]
  }
}

List consents

Request

▶️ Usage

With the Consents method, you can:

  1. List all consents related to your Belvo account (without using any query parameters).

📖 Pagination

This method returns a paginated response (default: 100 items per page). You can use the page_size query parameter to increase the number of items returned to a maximum of 1000 items. You can use the page query parameter to navigate through the results. For more details on how to navigate Belvo's paginated responses, see our Pagination Tips article.

🔦 Filtering Responses

Please see the query list below for a list of fields that you can filter your responses by. For more information on how to use filters, see our Filtering responses article.

Query
page_sizeinteger(int32)[ 1 .. 1000 ]

Indicates how many results to return per page. By default we return 100 results per page.

ℹ️ The minimum number of results returned per page is 1 and the maximum is 1000. If you enter a value greater than 1000, our API will default to the maximum value (1000).

Default 100
Example: page_size=100
pageinteger(int32)>= 1

A page number within the paginated result set.

Example: page=1
omitstring

Omit certain fields from being returned in the response. For more information, see our Filtering responses DevPortal article.

fieldsstring

Return only the specified fields in the response. For more information, see our Filtering responses DevPortal article.

user_documentstring[ 11 .. 14 ] charactersrequired

The CPF or CNPJ number of the user you want to get consent information for.

Example: user_document=12345678900
curl -i -X GET \
  -u <username>:<password> \
  'https://developers.belvo.com/_mock/apis/belvoopenapispec/api/consents/?fields=string&omit=string&page=1&page_size=100&user_document=12345678900'

Responses

Ok

Bodyapplication/json
countinteger(int32)

The total number of results in your Belvo account.

Example: 130
nextstring or null(uri)

The URL to next page of results. Each page consists of up to 100 items. If there are not enough results for an additional page, the value is null.

In our documentation example, we use {endpoint} as a placeholder value. In production, this value will be replaced by the actual endpoint you are currently using (for example, accounts or owners).

Example: "https://sandbox.belvo.com/api/{endpoint}/?link=1bd948f7-245d-4313-b604-34d1044cb908page=2"
previousstring or null(uri)

The URL to the previous page of results. If there is no previous page, the value is null.

Example: null
resultsArray of objects

Array of consent objects.

Response
application/json
{
  "count": 130,
  "next": "https://sandbox.belvo.com/api/{endpoint}/?link=1bd948f7-245d-4313-b604-34d1044cb908page=2",
  "previous": null,
  "results": [
    { … }
  ]
}

Get a consent's details

Request

Get the details of a specific consent.

Path
idstring(uuid)required

The consent.id you want to get detailed information about.

curl -i -X GET \
  -u <username>:<password> \
  'https://developers.belvo.com/_mock/apis/belvoopenapispec/api/consents/{id}/'

Responses

Ok

Bodyapplication/json
idstring(uuid)

Belvo's unique identifier for the current item.

Example: "0d3ffb69-f83b-456e-ad8e-208d0998d71d"
display_namestring or null<= 128 characters^[\w\W]{0,128}$

The full name of the individual that initiated the consent, as provided by the institution.

Example: "Jack Oswald White"
document_numberstring

The document number (CPF) of the individual.

Example: "76109277673"
belvo_institution_namestring

Belvo's name for the open finance institution that the consent is related to.

Example: "ofmockbank_br_retail"
expired_atstring(date-time)

The ISO-8601 timestamp when the consent will expire. In the case that undefined_consent_expiration is true, this field will be null.

Example: "2021-02-27T13:01:41.941Z"
undefined_consent_expirationboolean

Indicated whether the consent is for an undefined period, that is, that there is no expiration for the consent.

Example: false
created_atstring(date-time)

The ISO-8601 timestamp of when the data point was created in Belvo's database.

Example: "2022-02-09T08:45:50.406032Z"
statusstring or null

The status of the consent in the open finance network. Can be either:

  • AUTHORISED: The consent is still valid for use until the expired_at date.
  • AWAITING_AUTHORISATION_CONFIRMATION: The user must confirm within their institution.
  • AWAITING_AUTHORISATION: The user has been redirected to their institution to grant consent.
  • REJECTED: The user has not granted consent within their institution.
  • EXPIRED: The consent has expired as of the expired_at date.
  • null
Enum"AUTHORISED""AWAITING_AUTHORISATION_CONFIRMATION""AWAITING_AUTHORISATION""REJECTED""EXPIRED"null
Example: "AUTHORISED"
permissionsobject

Details regarding the permissions attached to the consent.

Response
application/json
{
  "id": "0d3ffb69-f83b-456e-ad8e-208d0998d71d",
  "display_name": "Jack Oswald White",
  "document_number": "76109277673",
  "belvo_institution_name": "ofmockbank_br_retail",
  "expired_at": "2021-02-27T13:01:41.941Z",
  "undefined_consent_expiration": false,
  "created_at": "2022-02-09T08:45:50.406032Z",
  "status": "AUTHORISED",
  "permissions": {
    "ACCOUNTS": [ … ],
    "CREDIT_CARDS": [ … ],
    "CREDIT_OPERATIONS": [ … ],
    "REGISTER": [ … ],
    "RESOURCES": [ … ]
  }
}

Owners

An owner represents the person who has access to a Link and is the owner of all the accounts inside the Link.

You can use this endpoint in order to get useful information about your client, such as:

  • their full name
  • key contact information
  • information about the ID document they used when opening the account
Operations

Accounts

An account is the representation of a bank account inside a financial institution. A user can have one or more accounts in an institution.

For example, one user (or link) can have a checking account, several credit cards, and a loan account.

Querying for a user's account information is useful as you can get information regarding:

  • what types of accounts the user has.
  • the balance for each account (savings, checking, credit card, loan, and so on).
  • detailed information regarding their credit card spending.
  • the current situation of any loans they may have.
Operations

Balances

A balance is the amount of money available in a given bank account (checking or savings) at a given time.

Operations

Transactions

A transaction contains the detailed information of each movement inside an account. For example, a purchase at a store or a restaurant.

Operations

Bills

A bill refers to the credit card bill a user receives for a given account.

Operations

Investments Brazil

Operations

Investment Transactions Brazil

Operations

Employments Brazil

Our employments resource for Brazil lets you get a comprehensive view of your user's current employment history and salary information.

For each user, we return the:

  • work history (including occupations and employer data)
  • historical and current salary information (per employer)

At the moment, the employments resource is available for:

  • 🇧🇷 Brazil (INSS)
Operations

Employment Records Mexico

Our employment records resource for Mexico lets you get a comprehensive view of your user’s current social security contributions and employment history.

With Belvo's employment records resource for Mexico, you can access information about your user's current social security contributions and employment history. For the each user, we return the:

  • personal data
  • work history
  • historical and current daily base salary
  • and more!

At the moment, the employment records resource is available for:

  • 🇲🇽 Mexico (IMSS)
  • 🇲🇽 Mexico (ISSSTE)
Operations

Invoices

Operations

Tax compliance status

Operations

Tax returns

Operations

Tax retentions

Operations

Tax status

Operations

Financial Statements

Operations

Invoices Chile

Operations

Tax Status Chile

Operations

Debt Reports Chile

Operations

Incomes

Use the Incomes endpoint to gather insights on an account's income sources for the past 365 days. The endpoint is particularly useful when you want to verify a person's income.

📘 Info

The incomes resource is only available for Checking and Savings accounts associated with banking links.

Operations

Recurring Expenses

Belvo's Recurring Expenses API allows you to identify a user's regular payments for subscription services, such as Netflix or gym memberships, as well as utility payments, such as electricity or phone bills. We return information for up to 365 days.

📘 Info

The recurring expenses resource is only available for Checking, Savings and Credit Card accounts associated with banking links.

Operations

Risk Insights

Operations

Employment Metrics

Operations

Payment Institutions (Brazil)

A payment institution is an entity that Belvo can access information from. You can see a complete list of institutions available for payments by making a List request to this endpoint.

Operations

Customers (Brazil)

A customer is the payer that's going to push funds into your bank account. You need to create a customer in order to receive inflow payments to your organization's bank account.

Operations

Bank Accounts (Brazil)

To receive inflow payments to your organization's bank account, you must register the bank accounts (individual and business) using Belvo's Payments API.

  • Individual bank accounts must be created for each payer (your customer).
  • Business bank accounts need to be created for the beneficiary of the payment (your organization).
Operations

Payment Links (Brazil)

This is a Payment link.

Operations

Payment Intents (Brazil)

A payment intent is a single point of access to create payments using any payment method offered by Belvo.

A payment intent captures all payment information (such as the amount to be charged, the description of the payment, the provider, and so on) and guides your customers through the payment flow.

Note: For institutions that require the username_type in the form_fields array, you must send through this value in your PATCH request.

Operations

Biometric Pix Widget Access Token (Brazil)

Use the Biometric Pix Widget Token requests to create a access token for Biometric Payments.

Operations

Payment Transactions (Brazil)

Each time you receive an inflow payment from your customer, a transaction is created in the Belvo database.

You can use the Payment Transactions resource in order to get useful information about a transaction as well as the specific charge associated with it.

Operations
Copyright © 2020-2025 Belvo. All rights reserved