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.