Rate Limiting

SMARTe Discover APIs enforce rate limits to ensure platform stability, fair usage, and consistent performance across all clients.

Rate limits are applied at the api key level and are evaluated across all API requests made using that organization’s credentials.

Requests are validated against rate limits before processing begins. If a request exceeds the allowed threshold, it is rejected immediately. Rate-limited requests do not consume credits.

How Rate Limiting Works

• Each request is checked against configured limits before execution
• Limits apply across all Discover API endpoints
• Requests exceeding the limit are blocked instantly
• No data retrieval or processing is performed for blocked requests

Rate Limit Response

When a rate limit is exceeded, the API returns:

• HTTP Status: 429 Too Many Requests
• Error Code: rate_limit_exceeded

{
  "error": {
    "code": "rate_limit_exceeded",
    "message": "Too many requests. Please try again after some time.",
    "status": 429
  }
}

Retry Guidance

Treat 429 responses as temporary failures. To handle them effectively:

• Use exponential backoff for retries
• Avoid immediate or aggressive retry attempts
• Respect any delay before retrying
• Distribute high-volume requests evenly over time

Best Practices

To avoid hitting rate limits:

• Avoid sending large bursts of concurrent requests
• Use Stats API to estimate data size before extraction
• Use Preview mode to validate filters before full requests
• Cache responses where possible to reduce repeated calls

Rate Limit Configuration

Rate limits vary based on your contract and usage tier.

If your integration requires higher throughput:

• Contact SMARTe Support
• Share expected request volume and usage patterns

Rate limits can be adjusted based on your application needs.