Skip to main content

Rate Limiting

The Nexus API implements rate limiting to ensure fair usage and maintain service quality for all users. This guide explains our rate limits, how to work with them, and strategies for optimizing your API usage.

Rate Limit Overview

Current Limits

Rate limits may vary based on your subscription plan. Contact support for higher limits.

Rate Limit Headers

Every API response includes headers that help you track your rate limit usage:

Header Definitions

  • X-RateLimit-Limit: Maximum requests allowed in the current window
  • X-RateLimit-Remaining: Number of requests remaining in the current window
  • X-RateLimit-Reset: Unix timestamp when the rate limit window resets

Handling Rate Limits

Reading Rate Limit Headers

Implementing Backoff Strategies

Exponential Backoff

Adaptive Rate Limiting

Optimization Strategies

1. Request Batching

Instead of making multiple individual requests, batch operations when possible:

2. Caching Responses

3. Connection Pooling

4. Request Prioritization

Monitoring Rate Limit Usage

Best Practices

  • Always check rate limit headers
  • Implement backoff strategies from day one
  • Plan for rate limit increases as you scale
  • Cache responses when appropriate
  • Batch operations to reduce request count
  • Use pagination efficiently
  • Avoid unnecessary requests
  • Queue requests during rate limit periods
  • Provide user feedback about delays
  • Implement circuit breakers
  • Have fallback strategies
  • Track rate limit usage metrics
  • Set up alerts before hitting limits
  • Monitor for patterns in rate limit hits
  • Review and optimize regularly

Rate Limit Calculator

Use this to estimate your rate limit needs:

Next Steps

Error Handling

Learn how to handle rate limit errors effectively

Best Practices

Explore production-ready patterns