Current API Limits#
| API Endpoint | Rate limit | Notes |
|---|
| Ping | 1 op/min | The usage limit is low for testing purposes, allowing testing of limit overflow behavior. |
| Deposit (PIX ➔ DePix) | 15 ops/min | Low limit due to restrictions imposed by the Central Bank. Contact support for adjustments. |
| Deposits | 12 ops/min | - |
| Deposit Status | 60 ops/min | This method should not be used often, and preferably only as a fallback to the webhook. |
| Withdraw | 10 ops/min | - |
| Withdrawal Status | 60 ops/min | This method should not be used often, and preferably only as a fallback to the webhook. |
| User Info | 15 ops/min | - |
These are the default limits. Your account may be configured with higher ones — contact our support team if your integration needs them.Amount Limits#
Rate limits are not the only limits. Amounts are bounded too. Read each bound below for what it applies to: the withdrawal range is per operation and never a daily total, while what caps deposits is the daily volume on your account.Withdraw#
| Limit | Value in reais |
|---|
| Minimum per withdrawal | 2,00 |
| Maximum per withdrawal | 6.000,00 |
| Withdrawal fee floor | 1,00 |
The range is checked on whichever amount parameter you send, depositAmountInCents or payoutAmountInCents. Outside it the request is rejected with 'depositAmountInCents' must be between the allowed min (200) and max (600000) withdrawal amounts, or with the same message naming 'payoutAmountInCents'.The fee floor is what makes small withdrawals expensive. Whichever is larger between your percentage rate and R$ 1,00 is deducted, so on a small withdrawal the percentage is not what you pay. The rate in force on your account is answered by /help on Telegram.Deposit#
| Limit | Value |
|---|
| Minimum per QR code | the fixed deposit fee charged on the network |
| Maximum per QR code | your daily limit |
splitFee | greater than 0%, at most 20%, plus a further ceiling on small deposits |
The deposit minimum is not a round number, and it is not printed here because it is the deposit fee itself and it is configured per account. A request below it is rejected with The amount provided is below the minimum of <fee>, and that message names the value in force. When splitFee is used, the check runs on amountInCents minus the split portion.There is no fixed maximum per QR code. What binds is the daily volume on your account: read maxDailyInCents, dailyVolumeInCents and dailyLimitResetTime from GET /api/user-info.Funding a withdrawal#
The DePix you send to fund a withdrawal must match what that withdrawal expects, within 5%. Within the tolerance the payout is recalculated from what actually arrived; above it the deposit is ignored. The full rules are on Withdraw.Rate Limiting#
To ensure fair usage and maintain the stability of our API, rate limiting is applied per account and per endpoint. Each endpoint has its own allowance, so requests to one endpoint never consume another endpoint's budget.The limit is the number of requests allowed per minute. It is not reset in one block at the top of each minute: the allowance refills continuously, one request every 60 / limit seconds. You may spend a full minute's worth back to back, and from then on each further request becomes available as the window advances.Example#
With Deposit Status at 60 ops/min, one request becomes available every second:1.
Starting from an idle integration, you can send 60 requests back to back.
2.
The next request is rejected until the window advances.
3.
From then on, one further request is accepted per second.
When you exceed a limit#
The API responds with 429 Too Many Requests and a Retry-After header holding the number of seconds to wait:Wait the number of seconds given in Retry-After before sending the next request.Handling Rate Limits#
To avoid hitting these limits:Space out your requests to stay within the sustained rate limit.
Honour the Retry-After header instead of retrying immediately.
Monitor your usage and adjust your application's behavior accordingly.
If your application requires higher limits, contact our support team to discuss your needs.
By adhering to these limits, you help ensure a reliable and consistent experience for all users of the API.Modified at 2026-08-24 16:08:13