canonical: https://jentic.com/apis/sandbox.belvo.com/sandbox-belvo

# Sandbox Belvo Belvo API Docs

Introduction 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: - **Bank information** such as account information, real-time balance, historical transactions, and account owner identification. - **Fiscal information** such as received and sent invoices and tax returns. <im. The API exposes 80 endpoints secured with basic authentication.

## For AI agents

Programmatically register a new link, list all links. Covers 80 operations with basic authentication.

## Scope

Does not handle communications, crm, or developer tools - use for payments only.

## Capabilities

- Register a new link
- List all links
- Complete a links request
- Get a link's details
- Update a link's credentials
- Change a link's access mode
- Delete a link

## Use cases

### Payments Operations

Use the Belvo API Docs to perform payments operations programmatically. The API provides 80 endpoints covering core functionality including register a new link, list all links, complete a links request.

Example prompt: Call POST `/api/links` to register a new link

### Automated Links Management

Automate links operations by combining multiple Belvo API Docs endpoints. Agents can list all links and then complete a links request in a single workflow.

Example prompt: Call GET `/api/links` to list all links, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Belvo API Docs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Example prompt: Search Jentic for 'register a new link', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/links` | Register a new link |
| GET | `/api/links` | List all links |
| PATCH | `/api/links` | Complete a links request |
| GET | `/api/links/{id}` | Get a link's details |
| PUT | `/api/links/{id}` | Update a link's credentials |
| PATCH | `/api/links/{id}` | Change a link's access mode |
| DELETE | `/api/links/{id}` | Delete a link |
| POST | `/api/accounts` | Retrieve accounts for a link |

## Key resources

- **Links** — A **Link** is a set of credentials associated to an end-user's access to an **institution**.

<div s
- **Accounts** — An **account** is the representation of a bank account inside a financial institution. A user can ha
- **Transactions** — A **transaction** contains the detailed information of each movement inside an account. For example,
- **Balances** — A **balance** represents the amount of funds available in a checking or savings account over a perio
- **Owners** — An **owner** represents the person who has access to a Link and is the owner of all the accounts ins

## Why Jentic

- **Setup:** Wiring the Belvo API by hand means sending basic auth with your secret id and password to the sandbox or development belvo.com host and handling link paging and retries yourself. Through Jentic you install once, import Belvo from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Belvo puts the link id in the URL path (`/api/links/{id}`), so a rule can pin your agent to specific links: it can read or update the ones you allow and nothing else. You choose the operations it may call, so actions like deleting a link are not included unless you add them.
- **Credential handling:** Your Belvo credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'register a new link' or 'list accounts', and Jentic returns the matching Belvo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Belvo API Docs use?

The Belvo API Docs uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I register a new link with the Belvo API Docs?

Yes. Use the POST `/api/links` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Belvo API Docs?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I register a new link through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'register a new link'. Jentic returns the matching Belvo API Docs operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Belvo API Docs have?

The Belvo API Docs exposes 80 endpoints covering links, accounts, transactions operations.

### Can I limit what my agent is allowed to do with the Belvo API?

Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which Belvo operations and credentials the agent may use. Since Belvo puts the link id in the URL path (`/api/links/{id}`), you can pin the agent to specific links so it only reads or updates the ones you allow and nothing else. You also choose which operations it may call, so a destructive action like DELETE `/api/links/{id}` is off limits unless you explicitly add it.