To maintain system stability and protect our partners (e.g. banks), certain API endpoints are subject to rate limits.
If your integration sends too many requests in a short period, the API will respond with HTTP 429 Too Many Requests.
Affected Endpoints
| Endpoint | Limit | Description |
|---|---|---|
POST /payouts | 50 requests/second | Create Payout |
POST /payouts/{id}/approve | 50 requests/second | Approve Payout |
POST /account/validate | 50 requests/second | Bank Account Validation |
Notes:
- Limits are applied per merchant (API key / credentials).
- Each endpoint’s quota is counted independently.
- All requests (success and error) are counted.
Error Response
When the rate limit is exceeded, you will receive HTTP 429 Too Many Requests without a JSON body
Best Practices
- Spread requests over time instead of sending them in bursts.
- Implement retry logic with exponential backoff and a small random delay (jitter).
- Do not immediately retry after a 429.
- Monitor your traffic and ensure your integration stays within the defined limits.
Example Scenario
If your system sends more than 50 requests to POST /account/validate within 1 second:
- Requests beyond the limit will be rejected with HTTP 429.
- You should pause sending new requests and retry after the specified wait time.