This page explains how to use our APIs in a stable, efficient, and predictable way. To maintain consistent performance for all clients, the platform applies several usage controls and operational limits. The sections below describe these limits and outline recommended integration practices.
1. Recommended Usage Practices
To ensure efficient use of the API and avoid unnecessary load, we recommend the following:
- Use Webhooks for real-time updates
Webhooks deliver status changes and events as they happen, removing the need for repeated polling. - Avoid time-based polling
Do not schedule fixed-interval jobs (e.g., every minute or every 5 minutes) to query the same endpoint repeatedly.Polling quickly consumes your request allocation and increases platform load without providing additional value.
- Reconciliation Frequency
For reconciliation use cases:
- Retrieve reconciliation data 1–2 times per day.
- Accounting entries are strictly ordered, so once a period is reconciled, there is no need to re-fetch historical data.
- Use pagination and date range efficiently to fetch only new entries.
- Design for efficient API consumption
To avoid unnecessary repeated requests:
- Cache non-sensitive static or infrequently changing data.
- Reuse resource IDs (accounts, payments, customers).
- Consolidate queries instead of repeatedly fetching the same information from multiple endpoints.
- These practices help maintain consistent performance and improve integration reliability.
2. Request Rate Recommendations
Recommended per-second request rates per DevApp:
| API Category | Recommended Rate | Description |
| Payment-related POST endpoints | Up to 5 req/s | Suitable for payment initiation and high-throughput operational flows. |
| All other API endpoints (GET, POST, PATCH, etc.) | Up to 2 req/s | Applies to accounts, balances, onboarding status, card information and similar resources. |
These values are defined as average sustained rates per DevApp and are measured over a rolling 15-minute window. Short bursts above these rates are acceptable, as long as the average rate over the window remains within the stated limits. Prolonged excess may result in throttling (429 Too Many Requests) or temporary rate limiting.
3. Daily Usage Limit
Each DevApp can perform up to 10,000 API requests per day, across all endpoints combined.
The limit resets every 24 hours.
This limit protects the platform from unintentional high-volume usage, often caused by polling or misconfigured scripts. If your integration requires a higher daily allocation, please contact us to discuss an appropriate usage profile.