Belvo API Docs (1.219.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

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

Employment Metrics Object

Employment Metrics details

idstring(uuid)required

Belvo's unique identifier for the current item.

Example: "0d3ffb69-f83b-456e-ad8e-208d0998d71d"
linkstring or null(uuid)required

The link.id the data belongs to.

Example: "30cb4806-6e00-48a4-91c9-ca55968576c8"
collected_atstring(date-time)required

The ISO-8601 timestamp when the data point was collected.

Example: "2022-02-09T08:45:50.406032Z"
created_atstring(date-time)required

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

Example: "2022-02-09T08:45:50.406032Z"
updated_atstring or null(date-time)required

The ISO-8601 timestamp of when the employment metrics calculation was last updated.

Example: "2023-08-30T15:31:35.728607Z"
reference_datestring or null(date)required

The reference_date your provided in your request. If you didn't provide one, this field will return null, indicating that the calculations are performed up until the date of the request.

Note: All calculations are relative to this date.

Example: "2023-06-01"
ageinteger(int32)required

The age of the individual.

Example: 32
current_statusstringrequired

Indicates the employment status of the individual. We return one of the following responses:

  • EMPLOYED
  • RETIRED
  • UNEMPLOYED
  • null
Enum"EMPLOYED""RETIRED""UNEMPLOYED""null"
Example: "EMPLOYED"
current_employer_countinteger or null(int32)required

The number of employers the individual has right now.

Example: 1
base_salary_lastnumber or null(float)required

The user's latest base salary. If current_status is EMPLOYED, this is the user's current base salary.

Example: 42.17
weeks_employed_last_jobnumber or null(float)required

The number of weeks the user was employed in their last job. If current_status is EMPLOYED, then this field indicates the number of weeks the user has been employed with his current job.

Example: 327.1429
weeks_since_last_jobnumber or null(float)required

The number of weeks since their last job. If the value of this field is 0, this indicates that the user is currently employed.

Example: 0
weeks_employed_totalnumber or null(float)required

The total number of weeks the user has been employed, according to the institution.

Note:

In the case that the user is employed at two or more places at the same time, we still calculate those weeks as one week. For example, if a user has three concurrent jobs for a month, this is calculated as 4 weeks.

Example: 148.2
weeks_with_multiple_employersnumber or null(float)required

The number of the weeks that the individual has had more than one employer at the same time.

Example: 0
employer_countinteger or null(int32)required

The total number of employers the user has had. Useful to indicate employment stability over the course of their lifetime.

Example: 14
unique_employer_countinteger or null(int32)required

The number of unique employers that the individual has had.

Note:

If the user left one company and returned, for example, six months later to the same company, this is counted as one employer.

Example: 3
employers_per_yearnumber or null(float)required

Number of employers per year. Useful to indicate employment stability over the course of a year.

Note:

If the user left one company and returned, for example, six months later to the same company, this is counted as one employer.

Example: 0.6326
weeks_between_jobsnumber or null(float)required

The total number of weeks the individual was unemployed.

Example: 687.2865
max_weeks_between_jobsnumber or null(float)required

The maximum number of weeks that the individual was unemployed.

Example: 249.8571
increases_last_jobinteger or null(int32)required

The total number of salary increases the user had in their last job. If current_status is EMPLOYED, this refers to the user's current job.

Note:

For all salary increases or decreases, we only take into account those where the change in salary is greater than 2%.

Example: 0
decreases_last_jobinteger or null(int32)required

The total number of salary increases the user had in their last job. If current_status is EMPLOYED, this refers to the user's current job.

Example: 0
increases_after_changeinteger or null(int32)required

The total number of salary increases between the individual's penultimate job and the last (or current) job.

Example: 0
decreases_after_changeinteger or null(int32)required

The total number of salary decreases between the individual's penultimate job and the last (or current) job.

Example: 0
increases_overallinteger or null(int32)required

The total number of salary increases throughout the individual's working career.

Example: 0
decreases_overallinteger or null(int32)required

The total number of salary decreases throughout the individual's working career.

Example: 0
increases_1yinteger or null(int32)required

The total number of salary increases throughout the individual's last year (YTD).

Example: 0
decreases_1yinteger or null(int32)required

The total number of salary decreases throughout the individual's last year (YTD).

Example: 0
increases_3yinteger or null(int32)required

The total number of salary increases throughout the individual's last three years.

Note:

If the individual's working career is less than three years, we return null.

Example: null
decreases_3yinteger or null(int32)required

The total number of salary decreases throughout the individual's last three years.

Note:

If the individual's working career is less than three years, we return null.

Example: null
increases_5yinteger or null(int32)required

The total number of salary increases throughout the individual's last five years.

Note:

If the individual's working career is less than five years, we return null.

Example: null
decreases_5yinteger or null(int32)required

The total number of salary decreases throughout the individual's last five years.

Note:

If the individual's working career is less than five years, we return null.

Example: null
yearly_change_1ynumber or null(float)required

The individual's salary percentage change for the last year (YTD).

Example: 0
yearly_change_3ynumber or null(float)required

The individual's salary percentage change for the last three years.

Note:

If the individual's working career is less than three years, we return null.

Example: null
yearly_change_5ynumber or null(float)required

The individual's salary percentage change for the last five years.

Note:

If the individual's working career is less than five years, we return null.

Example: null
min_monthly_salary_1ynumber or null(float)required

The individual's minimum monthly salary for the last year.

Example: 3402.88
min_monthly_salary_3ynumber or null(float)required

The individual's minimum monthly salary for the last three years.

Example: 3402.88
min_monthly_salary_5ynumber or null(float)required

The individual's minimum monthly salary for the last five years.

Example: 3402.88
average_monthly_salary_1ynumber or null(float)required

The individual's average monthly salary for the last year.

Example: 3402.88
average_monthly_salary_3ynumber or null(float)required

The individual's average monthly salary for the last three years.

Example: 3402.88
average_monthly_salary_5ynumber or null(float)required

The individual's average monthly salary for the last five years.

Example: 3402.88
max_monthly_salary_1ynumber or null(float)required

The individual's maximum monthly salary for the last year.

Example: 3402.88
max_monthly_salary_3ynumber or null(float)required

The individual's maximum monthly salary for the last three years.

Example: 3402.88
max_monthly_salary_5ynumber or null(float)required

The individual's maximum monthly salary for the last five years.

Example: 3402.88
{
  "id": "0d3ffb69-f83b-456e-ad8e-208d0998d71d",
  "link": "30cb4806-6e00-48a4-91c9-ca55968576c8",
  "collected_at": "2022-02-09T08:45:50.406032Z",
  "created_at": "2022-02-09T08:45:50.406032Z",
  "updated_at": "2023-08-30T15:31:35.728607Z",
  "reference_date": "2023-06-01",
  "age": 32,
  "current_status": "EMPLOYED",
  "current_employer_count": 1,
  "base_salary_last": 42.17,
  "weeks_employed_last_job": 327.1429,
  "weeks_since_last_job": 0,
  "weeks_employed_total": 148.2,
  "weeks_with_multiple_employers": 0,
  "employer_count": 14,
  "unique_employer_count": 3,
  "employers_per_year": 0.6326,
  "weeks_between_jobs": 687.2865,
  "max_weeks_between_jobs": 249.8571,
  "increases_last_job": 0,
  "decreases_last_job": 0,
  "increases_after_change": 0,
  "decreases_after_change": 0,
  "increases_overall": 0,
  "decreases_overall": 0,
  "increases_1y": 0,
  "decreases_1y": 0,
  "increases_3y": null,
  "decreases_3y": null,
  "increases_5y": null,
  "decreases_5y": null,
  "yearly_change_1y": 0,
  "yearly_change_3y": null,
  "yearly_change_5y": null,
  "min_monthly_salary_1y": 3402.88,
  "min_monthly_salary_3y": 3402.88,
  "min_monthly_salary_5y": 3402.88,
  "average_monthly_salary_1y": 3402.88,
  "average_monthly_salary_3y": 3402.88,
  "average_monthly_salary_5y": 3402.88,
  "max_monthly_salary_1y": 3402.88,
  "max_monthly_salary_3y": 3402.88,
  "max_monthly_salary_5y": 3402.88
}

List employment metrics

Request

▶️ Usage

With the List Employment Metrics method, you can:

  1. List employment metrics related to a specific link.id (using the link query parameter).
  2. Get the details of a specific employment-metric.id (using the id query parameter).
  3. [Not Recommended] List all employment metrics 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
linkstring(uuid)

The link.id you want to filter by.

ℹ️ We highly recommend adding the link.id filter in order to improve your performance.

Example: link=8848bd0c-9c7e-4f53-a732-ec896b11d4c4
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
link__inArray of strings(uuid)

Return results only for these link.ids.

Example: link__in=5722d0ba-69d7-42dc-8ff5-33767b83c5d6
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.

curl -i -X GET \
  -u <username>:<password> \
  'https://developers.belvo.com/_mock/apis/belvoopenapispec/api/employment-metrics/?fields=string&link=8848bd0c-9c7e-4f53-a732-ec896b11d4c4&link__in=5722d0ba-69d7-42dc-8ff5-33767b83c5d6&omit=string&page=1&page_size=100'

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 employment metric objects.

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

Retrieve employment metrics

Request

Retrieve employment metrics for an individual.

Note: Before requesting employment metrics, make sure to first make a POST Retrieve employment record details request.

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

Bodyapplication/jsonrequired
linkstring(uuid)required

The link.id you want to retrieve information for.

Example: "c81a1dea-6dd6-4999-8b9f-541ee8197058"
reference_datestring(date)

The date until which you want the employment metrics to be calculated, in YYYY-MM-DD format. For example, if you do not want to calculate employment metrics for all of 2023, the add 2022-12-31 as the reference_date.

If you do not provide a reference_date, we perform calcualtions up until the date you make the request.

Note: All calculations will be relative to this date.

Example: "2023-03-01"
save_databoolean

Indicates whether or not to persist the data in Belvo. By default, this is set to true and we return a 201 Created response.

When set to false, the data won't be persisted and we return a 200 OK response.

Default true
Example: true
curl -i -X POST \
  -u <username>:<password> \
  'https://developers.belvo.com/_mock/apis/belvoopenapispec/api/employment-metrics/?fields=string&omit=string' \
  -H 'Content-Type: application/json' \
  -d '{
    "link": "c81a1dea-6dd6-4999-8b9f-541ee8197058",
    "reference_date": "2023-03-01",
    "save_data": true
  }'

Responses

Ok

Bodyapplication/json
idstring(uuid)required

Belvo's unique identifier for the current item.

Example: "0d3ffb69-f83b-456e-ad8e-208d0998d71d"
linkstring or null(uuid)required

The link.id the data belongs to.

Example: "30cb4806-6e00-48a4-91c9-ca55968576c8"
collected_atstring(date-time)required

The ISO-8601 timestamp when the data point was collected.

Example: "2022-02-09T08:45:50.406032Z"
created_atstring(date-time)required

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

Example: "2022-02-09T08:45:50.406032Z"
updated_atstring or null(date-time)required

The ISO-8601 timestamp of when the employment metrics calculation was last updated.

Example: "2023-08-30T15:31:35.728607Z"
reference_datestring or null(date)required

The reference_date your provided in your request. If you didn't provide one, this field will return null, indicating that the calculations are performed up until the date of the request.

Note: All calculations are relative to this date.

Example: "2023-06-01"
ageinteger(int32)required

The age of the individual.

Example: 32
current_statusstringrequired

Indicates the employment status of the individual. We return one of the following responses:

  • EMPLOYED
  • RETIRED
  • UNEMPLOYED
  • null
Enum"EMPLOYED""RETIRED""UNEMPLOYED""null"
Example: "EMPLOYED"
current_employer_countinteger or null(int32)required

The number of employers the individual has right now.

Example: 1
base_salary_lastnumber or null(float)required

The user's latest base salary. If current_status is EMPLOYED, this is the user's current base salary.

Example: 42.17
weeks_employed_last_jobnumber or null(float)required

The number of weeks the user was employed in their last job. If current_status is EMPLOYED, then this field indicates the number of weeks the user has been employed with his current job.

Example: 327.1429
weeks_since_last_jobnumber or null(float)required

The number of weeks since their last job. If the value of this field is 0, this indicates that the user is currently employed.

Example: 0
weeks_employed_totalnumber or null(float)required

The total number of weeks the user has been employed, according to the institution.

Note:

In the case that the user is employed at two or more places at the same time, we still calculate those weeks as one week. For example, if a user has three concurrent jobs for a month, this is calculated as 4 weeks.

Example: 148.2
weeks_with_multiple_employersnumber or null(float)required

The number of the weeks that the individual has had more than one employer at the same time.

Example: 0
employer_countinteger or null(int32)required

The total number of employers the user has had. Useful to indicate employment stability over the course of their lifetime.

Example: 14
unique_employer_countinteger or null(int32)required

The number of unique employers that the individual has had.

Note:

If the user left one company and returned, for example, six months later to the same company, this is counted as one employer.

Example: 3
employers_per_yearnumber or null(float)required

Number of employers per year. Useful to indicate employment stability over the course of a year.

Note:

If the user left one company and returned, for example, six months later to the same company, this is counted as one employer.

Example: 0.6326
weeks_between_jobsnumber or null(float)required

The total number of weeks the individual was unemployed.

Example: 687.2865
max_weeks_between_jobsnumber or null(float)required

The maximum number of weeks that the individual was unemployed.

Example: 249.8571
increases_last_jobinteger or null(int32)required

The total number of salary increases the user had in their last job. If current_status is EMPLOYED, this refers to the user's current job.

Note:

For all salary increases or decreases, we only take into account those where the change in salary is greater than 2%.

Example: 0
decreases_last_jobinteger or null(int32)required

The total number of salary increases the user had in their last job. If current_status is EMPLOYED, this refers to the user's current job.

Example: 0
increases_after_changeinteger or null(int32)required

The total number of salary increases between the individual's penultimate job and the last (or current) job.

Example: 0
decreases_after_changeinteger or null(int32)required

The total number of salary decreases between the individual's penultimate job and the last (or current) job.

Example: 0
increases_overallinteger or null(int32)required

The total number of salary increases throughout the individual's working career.

Example: 0
decreases_overallinteger or null(int32)required

The total number of salary decreases throughout the individual's working career.

Example: 0
increases_1yinteger or null(int32)required

The total number of salary increases throughout the individual's last year (YTD).

Example: 0
decreases_1yinteger or null(int32)required

The total number of salary decreases throughout the individual's last year (YTD).

Example: 0
increases_3yinteger or null(int32)required

The total number of salary increases throughout the individual's last three years.

Note:

If the individual's working career is less than three years, we return null.

Example: null
decreases_3yinteger or null(int32)required

The total number of salary decreases throughout the individual's last three years.

Note:

If the individual's working career is less than three years, we return null.

Example: null
increases_5yinteger or null(int32)required

The total number of salary increases throughout the individual's last five years.

Note:

If the individual's working career is less than five years, we return null.

Example: null
decreases_5yinteger or null(int32)required

The total number of salary decreases throughout the individual's last five years.

Note:

If the individual's working career is less than five years, we return null.

Example: null
yearly_change_1ynumber or null(float)required

The individual's salary percentage change for the last year (YTD).

Example: 0
yearly_change_3ynumber or null(float)required

The individual's salary percentage change for the last three years.

Note:

If the individual's working career is less than three years, we return null.

Example: null
yearly_change_5ynumber or null(float)required

The individual's salary percentage change for the last five years.

Note:

If the individual's working career is less than five years, we return null.

Example: null
min_monthly_salary_1ynumber or null(float)required

The individual's minimum monthly salary for the last year.

Example: 3402.88
min_monthly_salary_3ynumber or null(float)required

The individual's minimum monthly salary for the last three years.

Example: 3402.88
min_monthly_salary_5ynumber or null(float)required

The individual's minimum monthly salary for the last five years.

Example: 3402.88
average_monthly_salary_1ynumber or null(float)required

The individual's average monthly salary for the last year.

Example: 3402.88
average_monthly_salary_3ynumber or null(float)required

The individual's average monthly salary for the last three years.

Example: 3402.88
average_monthly_salary_5ynumber or null(float)required

The individual's average monthly salary for the last five years.

Example: 3402.88
max_monthly_salary_1ynumber or null(float)required

The individual's maximum monthly salary for the last year.

Example: 3402.88
max_monthly_salary_3ynumber or null(float)required

The individual's maximum monthly salary for the last three years.

Example: 3402.88
max_monthly_salary_5ynumber or null(float)required

The individual's maximum monthly salary for the last five years.

Example: 3402.88
Response
application/json
{
  "id": "0d3ffb69-f83b-456e-ad8e-208d0998d71d",
  "link": "30cb4806-6e00-48a4-91c9-ca55968576c8",
  "collected_at": "2022-02-09T08:45:50.406032Z",
  "created_at": "2022-02-09T08:45:50.406032Z",
  "updated_at": "2023-08-30T15:31:35.728607Z",
  "reference_date": "2023-06-01",
  "age": 32,
  "current_status": "EMPLOYED",
  "current_employer_count": 1,
  "base_salary_last": 42.17,
  "weeks_employed_last_job": 327.1429,
  "weeks_since_last_job": 0,
  "weeks_employed_total": 148.2,
  "weeks_with_multiple_employers": 0,
  "employer_count": 14,
  "unique_employer_count": 3,
  "employers_per_year": 0.6326,
  "weeks_between_jobs": 687.2865,
  "max_weeks_between_jobs": 249.8571,
  "increases_last_job": 0,
  "decreases_last_job": 0,
  "increases_after_change": 0,
  "decreases_after_change": 0,
  "increases_overall": 0,
  "decreases_overall": 0,
  "increases_1y": 0,
  "decreases_1y": 0,
  "increases_3y": null,
  "decreases_3y": null,
  "increases_5y": null,
  "decreases_5y": null,
  "yearly_change_1y": 0,
  "yearly_change_3y": null,
  "yearly_change_5y": null,
  "min_monthly_salary_1y": 3402.88,
  "min_monthly_salary_3y": 3402.88,
  "min_monthly_salary_5y": 3402.88,
  "average_monthly_salary_1y": 3402.88,
  "average_monthly_salary_3y": 3402.88,
  "average_monthly_salary_5y": 3402.88,
  "max_monthly_salary_1y": 3402.88,
  "max_monthly_salary_3y": 3402.88,
  "max_monthly_salary_5y": 3402.88
}

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

Payment Authorizations (Brazil)

A Payment Authorization is the consent that your user gives you to charge (debit money from) their accounts. You need to perform one Payment Authorization per ‘contract’ (for example, if your company does both electricity and water but they are billed separately, then you will create two separate Payment Authorizations).

Once the user confirms the authorization, you will need to listen for a a PAYMENT_AUTHORIZATION webhook with the status set to AUTHORIZED. Once you receive this webhook, the authorization process is complete, and you will be able to charge your user.

What is a charge?

A charge represents the individual payment (debit) that your customer will make.

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