Welcome

Trio is a complete banking solution for companies, designed to automate financial operations, move money at scale and manage corporate treasury. Trio is authorized by the Central Bank of Brazil (No. 619, ISPB 49931906) and exposes its infrastructure through a REST API, so you can embed Pix, boleto, payments and corporate cards directly in your product. It walks you from your first sandbox request to a production integration, and it is organized so that each section answers one kind of question.

Start here

Plan your integration

What an integration involves, how long it takes and the steps in order.

Sandbox account

Create a free sandbox account and explore the Trio App.

First API credential

Generate the client ID and secret every request authenticates with.

First webhook

Receive events instead of polling the API.

How the documentation is organized

Get Started explains the basics every request depends on: environments, authentication, the core objects, error handling, pagination, dates and rate limits, plus how webhooks work.
Guides are task-oriented walkthroughs grouped by what you want to do: onboard customers, receive money (Pix, boleto, Pix Automático, fees, split payments), pay money, run operations, connect an AI agent through Trio MCP and use the Trio SDK.
API reference is the complete catalog of V2 endpoints, generated from the OpenAPI specification, with request and response schemas and an interactive playground.
FAQ collects the questions integrators ask most, about the sandbox, credentials, webhooks and boletos.

What changed in V2

If you integrated with the V1 API, these are the differences you will meet first. Each guide also carries a short “Coming from V1?” note where it matters.

Area	V1	V2
Paths	`/banking/...`, `/webhooks`	Every path starts with `/v2`
Accounts	Bank accounts and virtual accounts (`virtual_account_id`)	Bank accounts only. Every receivable and payment names its `bank_account_id`
Transactions	Collecting and payment documents	In documents, out documents and transfer documents under `/v2/documents`, each with its refunds
Response shapes	Flat ids and timestamps (`counterparty_id`, `origin_type`, `timestamp`)	Nested objects (`counterparty`, `origin`, `reference`, `fee`) and `inserted_at` / `updated_at`. Money is `{ "amount", "currency" }`
Pix payouts	One endpoint with `reference`	An asynchronous endpoint with `reference`, or a check-then-pay flow with `check_id`. Payments to a bank account send a `counterparty`
Boleto and Pix Automático	Flat discount, fine and interest fields	Structured `due_detail` rules with a `calculation_type` and percentages in basis points
Split payments	`split`	`splits`, with the same items
Updates and cancellations	Returned the object	Return `204 No Content`; read the resource back or wait for the webhook
Validation errors	`400`	`422`, with the rule code in `error_code`
Pagination	`has_next`	`has_more`, with `before` and `after` cursors
Webhooks	One payload version	`api_version` chooses `v100` or `v200` payloads; webhooks can be limited to an entity or a group

Pix biometrics and virtual accounts have no V2 endpoints.

Environments

Environment	Base URL
Sandbox	`https://api.sandbox.trio.com.br`
Production	`https://api.trio.com.br`

Every example in this documentation uses the sandbox. See Environments and Authentication before your first request.

Need help?

The Support page lists the channels, their availability and what to include when you report an issue.

Getting started

API basics

Webhooks

Start here

Plan your integration

Sandbox account

First API credential

First webhook

How the documentation is organized

What changed in V2

Environments

Need help?

​Start here

Plan your integration

Sandbox account

First API credential

First webhook

​How the documentation is organized

​What changed in V2

​Environments

​Need help?

Start here

How the documentation is organized

What changed in V2

Environments

Need help?