How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Belvo

Belvo Payments (Brazil) API

Pix / Open Finance payment initiation in Brazil.

Documentation Provider Profile APIs.io OpenAPI GitHub

Belvo Payments (Brazil) API is one of 10 APIs that Belvo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payments (Brazil). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 6 operations across 4 paths, and defines 8 schemas. It is described by OpenAPI 3.0.1, at version 1.0.

Requests are made against 2 base URLs: https://api.belvo.com, https://sandbox.belvo.com.

6 operations 4 paths 8 schemas 4 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.1
API Version
1.0
Base URL
https://api.belvo.com/api
Authentication
HTTP Basic
Contact
Belvo Support
Terms of Service
View terms
Resource Areas
1

Authentication & Security 1

Belvo Payments (Brazil) API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic authentication using your Secret Key ID as the username and your Secret Key Password as the password.

Paths & Operations 6

Across 4 paths, the API surfaces 6 operations — 4 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Payments (Brazil) 6

Pix / Open Finance payment initiation in Brazil.

GET
/payments/br/payment-intents/
List all payment intents
listPaymentIntents → 200
POST
/payments/br/payment-intents/
Create a payment intent
createPaymentIntent body → 201
GET
/payments/br/payment-intents/{id}/
Get a payment intent's details
detailPaymentIntent 1 param → 200
GET
/payments/br/customers/
List all customers
listCustomers → 200
POST
/payments/br/customers/
Create a customer
createCustomer body → 201
GET
/payments/br/payment-institutions/
List all payment institutions
listPaymentInstitutions → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are PaymentIntent (8 properties), PaymentIntentRequest (6 properties), PaymentInstitution (5 properties), Customer (5 properties). Each schema is shown below with its type and property counts.

Customer
object
5 properties
Pagination
object
3 properties
PaymentIntentRequest
object
6 properties 3 required
PaginatedCustomers
CustomerRequest
object
3 properties 2 required
PaymentInstitution
object
5 properties
PaymentIntent
object
8 properties
PaginatedPaymentIntents

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

belvo-payments-brazil-api-openapi.yml Raw ↑

Other APIs Belvo publishes across the network.

Belvo Accounts API
AE Profile APIs.io
Belvo Balances API
AE Profile APIs.io
Belvo Incomes API
AE Profile APIs.io
Belvo Institutions API
AE Profile APIs.io
Belvo Links API
AE Profile APIs.io
Belvo Owners API
AE Profile APIs.io
Belvo Recurring Expenses API
AE Profile APIs.io
Belvo Transactions API
AE Profile APIs.io
Belvo Webhooks API
AE Profile APIs.io
#Payments (Brazil)
← Back to B APIs
API Details
ID
belvo:belvo-payments-brazil-api
Base URL
https://api.belvo.com/api
Docs
https://developers.belvo.com/apis/belvoopenapispec/links
Provider
Belvo
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=belvo-payments-brazil-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/belvo-payments-brazil-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Belvo Payments (Brazil) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.