Endpoints that involve virtual-accounts have specific rate limits to ensure system stability and fair access for all clients.
- Endpoints affected: All endpoints with
virtual-accountsin the path.- Example:
POST …/virtual-accounts - Example:
GET …/virtual-accounts/{id}
- Example:
- How requests are counted: Limits are applied per client account.
| Scope | Applies To | Limit | What Happens If You Go Over |
|---|---|---|---|
| Per Client | All virtual-accounts endpoints | 3,000 requests per hour | You will receive a 429 Too Many Requests response. |
If you exceed 3,000 requests in a rolling 1-hour window, you’ll receive an HTTP 429 Too Many Requests response.
Example response
{
"error": "Rate limit exceeded",
"message": "You have exceeded the limit of 3000 requests per hour.",
"retry_after": "3600 seconds"
}- Monitor your usage: Keep track of your request volume to avoid hitting the cap.
- Implement Backoff: If you receive a 429, respect the
retry_afterheader or implement exponential backoff in your retry logic. - Batch Operations: Where possible, use batch endpoints or efficient querying to minimize the number of individual requests.