Skip to main content

Rate Limit Summary

Rate Limit Headers

Every API response includes rate limit information:

Handling 429 Responses

When you exceed a rate limit, the API returns 429 Too Many Requests:

Exponential Backoff Pattern

High-Volume Integration Patterns

Pattern 1 — Use Batch Endpoints

If you’re hitting single-event rate limits, switch to batch:

Pattern 2 — Queue and Flush

Buffer events in memory and flush in batches:

Pattern 3 — Multiple API Keys

For very high-volume operations, you can create multiple API keys (one per service/worker) to distribute load across separate rate limit buckets.
Contact platform@atlas.io if you need higher rate limits for your use case. Enterprise plans include custom limits.