canonical: https://jentic.com/apis/inter.co/inter

# Inter Banco Inter API

Jentic publishes the only available OpenAPI specification for Banco Inter API, keeping it validated and agent-ready. Banco Inter API exposes the bank's Empresas (business banking) endpoints for Brazilian companies, covering account statements, balance retrieval, scheduled payments, Pix instant transfers, boleto issuance, and CNAB file processing. Authentication uses OAuth 2.0 client credentials with scoped tokens (extrato.read, pix.write, boleto.write) plus a per-account x-inter-conta-corrente header. The 17 operations cover the day-to-day flows a Brazilian business needs to automate cash-in and cash-out without touching the bank's web UI.

## For AI agents

Issue Pix charges, generate boletos, schedule payments, and pull statements from Banco Inter business accounts in Brazil.

## Scope

Does not handle retail consumer accounts, card issuing, lending origination, or non-Brazilian payment rails - use for Banco Inter Empresas business banking, Pix, and boleto operations only.

## Capabilities

- Generate Pix dynamic and static charges and read settled Pix transactions by end-to-end ID
- Issue and cancel boletos through the Cobranca endpoints with custom Nosso Numero references
- Pull account statements and current balance for reconciliation against ERP records
- Schedule and track outbound payments via `/banking/v2/pagamento` with status lookup by codigoPagamento
- Submit CNAB 240/400 batch files for bulk billing and retrieve processing results
- Mint scoped OAuth 2.0 access tokens for Pix, boleto, or statement-only agent permissions

## Use cases

### Brazilian E-Commerce Pix Checkout

Online merchants in Brazil accept Pix instant payments by creating dynamic charges through `/pix/v2/cob` and polling `/pix/v2/pix/{e2eid}` for settlement confirmation. Banco Inter returns the QR code and copy-paste payload that the storefront renders at checkout, and the webhook or polling flow confirms receipt within seconds. Integration takes a few days end-to-end including OAuth onboarding with the bank.

Example prompt: Create a Pix dynamic charge for R$ 250.00 with txid order-9914 and return the QR code payload to the checkout page

### Accounts Receivable Boleto Automation

Finance teams generate boletos for B2B invoices through `/cobranca/v2/boletos`, monitor settlement status with the Nosso Numero lookup, and reconcile paid items against the ERP daily. Banco Inter supports both the per-invoice REST flow and bulk CNAB submission for high-volume billers. End-to-end automation removes manual register entry from the AR cycle.

Example prompt: Generate a boleto for invoice 4421 with R$ 3,200.00 due on 2026-07-15 and store the returned linhaDigitavel

### Treasury Reconciliation

Treasury and accounting agents pull `/banking/v2/extrato` statements and `/banking/v2/saldo` balance snapshots on a daily schedule to match recorded transactions against bank truth. The OAuth scope extrato.read isolates this read-only flow from any payment-creation permission. Reconciliation jobs that took half a day manually run in minutes.

Example prompt: Fetch the account statement between 2026-06-01 and 2026-06-09 and emit one CSV row per transaction

### Agent-Driven Vendor Payouts

An AI agent triggered by an approved purchase order calls `/banking/v2/pagamento` to schedule the vendor disbursement, then polls `/banking/v2/pagamento/{codigoPagamento}` until status confirms execution. Jentic isolates the OAuth client credentials in your Jentic One instance so the agent only ever sees a short-lived scoped token. The full approval-to-payout loop is a single workflow rather than a procurement-to-banking handoff.

Example prompt: Schedule a R$ 8,750 payment to vendor CNPJ 12.345.678/0001-90 for invoice INV-3392 and confirm status reaches EXECUTADO

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/oauth/v2/token` | Exchange client credentials for a scoped access token |
| POST | `/pix/v2/cob` | Create a Pix dynamic charge with QR code payload |
| GET | `/pix/v2/pix/{e2eid}` | Retrieve a settled Pix transaction by end-to-end ID |
| POST | `/cobranca/v2/boletos` | Issue a new boleto |
| GET | `/banking/v2/extrato` | Pull the account statement for a date range |
| GET | `/banking/v2/saldo` | Read the current account balance |
| POST | `/banking/v2/pagamento` | Schedule an outbound payment |
| POST | `/cnab/v2/arquivos` | Submit a CNAB batch billing file |

## Key resources

- **Pix** — Create dynamic and static Pix charges, read transactions and settlement status by txid or end-to-end ID
- **Cobranca (Boletos)** — Issue, list, retrieve, and cancel boleto invoices with Nosso Numero referencing
- **Banking** — Account statement, balance lookup, and payment scheduling for the corporate account
- **CNAB** — Submit and retrieve batch billing files for high-volume operations
- **OAuth** — Token exchange endpoint at `/oauth/v2/token` with scope-based permissions

## Why Jentic

- **Setup:** Wiring the Banco Inter API by hand means running its OAuth2 client-credentials flow against `/oauth/v2/token`, passing the x-inter-conta-corrente value, and tracking Pix, boleto, and banking paths. Through Jentic you install once, import the Banco Inter API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Banco Inter scopes access through OAuth2 scopes such as pix.write and extrato.read with the target carried in the request body, so limit the agent to the operations it needs, such as issuing a Pix charge or reading a statement. You choose the operations it may call, so payments are not included unless you add them.
- **Credential handling:** Your Banco Inter client credentials and account value are stored once, encrypted, by your own Jentic One instance and exchanged for a short-lived scoped token at execution time. The client secret never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'issue a Pix charge' or 'read the account statement', and Jentic returns the matching Banco Inter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Flutterwave API** — Africa-focused payment processor versus Brazil-focused Banco Inter
- **Stripe API** — Global card processor versus Brazil-native Pix and boleto rails
- **Plaid API** — Bank account aggregation that pairs with direct bank APIs for full reconciliation

## FAQ

### Why is there no official OpenAPI spec for Banco Inter API?

Banco Inter does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Banco Inter API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Banco Inter API use?

Banco Inter API uses OAuth 2.0 client credentials issued via `/oauth/v2/token`, returning a scoped access token (extrato.read, pix.read, pix.write, boleto.write). Every request also requires the x-inter-conta-corrente header carrying the corporate account number. Through Jentic, the OAuth client_id and client_secret are stored in your Jentic One instance and the agent only ever receives a short-lived scoped token.

### Can I issue Pix charges with the Banco Inter API?

Yes. POST `/pix/v2/cob` creates a dynamic Pix charge with a txid you supply, returning the QR code payload and copy-paste string. GET `/pix/v2/cob/{txid}` retrieves the charge and GET `/pix/v2/pix/{e2eid}` confirms a settled transaction by its end-to-end ID.

### What are the rate limits for the Banco Inter API?

The OpenAPI spec does not declare numeric rate limits. Banco Inter applies per-tenant throttling on the production environment and provides a sandbox at https://sandbox.inter.co for unrestricted testing during development. Treat HTTP 429 as the canonical signal and back off.

### How do I generate a boleto with the Banco Inter API through Jentic?

Search Jentic for 'issue a boleto'. The SDK returns the POST `/cobranca/v2/boletos` operation with its input schema (payer, amount, due date). Run pip install jentic, await client.search('issue a boleto'), then await client.execute(...) with the boleto payload.

### Does the Banco Inter API support CNAB batch processing?

Yes. POST `/cnab/v2/arquivos` accepts a CNAB file for bulk billing and returns a processing reference. GET `/cnab/v2/arquivos` lists submitted files and their statuses, which is the standard route for billers issuing thousands of boletos in one run.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Banco Inter operations and credentials your agent may use, and the Banco Inter API itself gates access through OAuth 2.0 scopes such as pix.write, boleto.write, and extrato.read. You can restrict the agent to read-only work, like pulling statements from `/banking/v2/extrato` and balances from `/banking/v2/saldo`, without granting any charge or payment ability. If you only enable the scoped operations for issuing a Pix charge or a boleto, the agent cannot schedule outbound payments through `/banking/v2/pagamento` unless you explicitly add that operation.