API Rate Limiting (200 Requests/Minute)

⚠️ Sign up for our API Mailing list here to receive updates about future API changes.

API Rate Limiting Update

To ensure fast and reliable performance for all customers, the Dash Platform will now enforce an API rate limit of 200 requests per minute per user on February 2nd, 2026.

New Response Headers

All successful API responses include:

• X-RateLimit-Limit – Total number of requests allowed per minute
• X-RateLimit-Remaining – Number of requests still available in the current window

When the rate limit is exceeded, the API returns HTTP 429 – Too Many Requests along with:

• Retry-After – Number of seconds until the request may be retried
• X-RateLimit-Reset – Timestamp indicating when the current rate-limit window resets

Normal access resumes automatically once request volume drops below the threshold.

Required Integration Updates

Please ensure your integration:

• Handles HTTP 429 responses gracefully
• Implements retry logic with exponential or incremental backoff
• Monitors rate-limit headers to avoid unnecessary throttling

These changes protect overall system stability and provide a more consistent experience for all users.

FAQ:

1. What is the new rate limit?
   1. 200 requests per minute per account.
2. How do I know my remaining quota?
   1. Check response headers:
      1. X-RateLimit-Limit
      2. X-RateLimit-Remaining
3. What happens if I exceed the limit?
   1. You’ll receive HTTP 429 with:
      1. Retry-After (seconds to wait)
      2. X-RateLimit-Reset (reset timestamp)
4. What should my integration do?
   1. Handle 429 responses
   2. Wait the Retry-After duration
   3. Use retry logic with backoff
   4. Avoid tight polling or rapid bursts
5. Does this apply to all endpoints?
   1. Yes — the limit is per account across all API routes.
6. What if I need higher limits?
   1. Optimize request patterns, then contact our team to discuss your use case.