recipient). Through the public API you can query balance, summary, and statement by recipient, and request/track payouts (withdrawals).
Internally, a recipient may have multiple physical wallets (one per gateway/PSP + currency). The public API does not expose this dimension: you see a single “virtual” wallet per currency, aggregating all of the recipient’s physical wallets. That is why there are no endpoints by
walletId — everything is by ownerId (the recipient) or recipientId.All monetary values (
availableBalance, amount, etc.) are integers in cents: 152030 = BRL 1,520.30. Dates are ISO 8601 with timezone (2026-06-01T00:00:00-03:00). See Conventions.x-api-key header. See Authentication.
Endpoints
| Method | Route | Description |
|---|---|---|
GET | /wallets/owner/{ownerId}/balance | Aggregated balance by currency |
GET | /wallets/owner/{ownerId}/summary | Statement summary by period |
GET | /wallets/owner/{ownerId}/transactions | Paginated recipient statement |
GET | /withdrawals/config | Withdrawal configuration (fees and minimum) |
GET | /withdrawals | List withdrawals |
GET | /withdrawals/{id} | Retrieve withdrawal by ID |
POST | /withdrawals | Request a withdrawal |
POST | /withdrawals/{id}/cancel | Cancel a withdrawal |
Aggregated balance by currency
Recipient ID (e.g.
rec_123). Passed in the URL.ID of the queried recipient.
One item per currency in which the recipient has a wallet.
Statement summary by period
Recipient ID. Passed in the URL.
Filters (query params)
Filters by entry type.
Filters by entry source.
Filters by currency (ISO 4217).
Release status. Accepted values:
released or pending.Start of the period, ISO 8601 with timezone. E.g.
2026-06-01T00:00:00-03:00.End of the period, ISO 8601 with timezone.
ID of the queried recipient.
One item per currency with the period summary. Each item contains
currency, byType (a list of { type, total, credits, debits, count }), totalCredits, totalDebits, and net. credits and debits are separated by the sign of the entry; net = totalCredits + totalDebits. All values in cents.Recipient statement
Recipient ID. Passed in the URL.
Pagination (query params)
Current page.
Items per page.
Filters (query params)
The filters are the same as the summary endpoint:type, source, currency, releaseStatus (released or pending), startDate, and endDate (ISO 8601 with timezone). All are optional.
The response uses the Core API’s standard pagination envelope:
data (list of entries) + pagination. See Conventions for the full format.Withdrawals (payouts)
A withdrawal is requested by recipient + currency: the system aggregates the withdrawable balance from all wallets in that currency. The status flow is:A withdrawal created via the API enters as
requested and awaits manual approval in the dashboard before being processed.Withdrawal configuration
Currency in ISO 4217 format (exactly 3 letters, e.g.
BRL). Optional.Percentage fee applied to the withdrawal amount.
Fixed fee per withdrawal, in cents.
Minimum withdrawal amount, in cents.
List withdrawals
Filters by status. Possible values:
requested, approved, processing, paid, cancelled, rejected, failed. Optional.Current page.
Items per page.
Retrieve withdrawal by ID
Withdrawal ID. Passed in the URL.
404. See Errors.
Request a withdrawal
recipientId, aggregating the balance from all wallets in that currency. The withdrawal enters as requested and awaits approval. Returns 201.
ID of the recipient making the withdrawal.
Withdrawal amount in cents. Integer, minimum
1.Currency in ISO 4217 format (exactly 3 letters). Optional — when omitted, defaults to
BRL.The returned withdrawal includes
walletId (the physical wallet debited — chosen automatically when there is more than one for the currency), amount (gross), fee, and netAmount (amount - fee). The recipient provided in the request is not echoed back in the response body.Cancel a withdrawal
requested status).
ID of the withdrawal to cancel. Passed in the URL.
Cancellation reason. Optional (minimum 1 character when provided).
404— withdrawal not found.409— the withdrawal cannot be cancelled in its current status (already moved pastrequested).
See also
Recipients
Register the recipients who own the wallets.
Splits
How balance flows into wallets from sales.
Settlement
When and how balance is released for withdrawal.
Webhooks
Receive withdrawal events (
withdrawal.*) in your system.
