Rate Limiting

Understand how the Pixelbase API rate limits work and how to handle them gracefully.

Overview

The Pixelbase API implements rate limiting to ensure fair usage and maintain service stability for all users. Rate limits are applied on a per-API-key basis.

The default rate limit is 60 requests per minute per organization. If you need higher limits for your use case, please .

Rate Limit Headers

Every API response includes headers to help you track your current rate limit status:

X-RateLimit-LimitThe maximum number of requests allowed per minute.

X-RateLimit-RemainingThe number of requests remaining in the current rate limit window.

X-RateLimit-ResetUnix timestamp indicating when the rate limit window resets.

Handling Rate Limits

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

json

{
  "message": "Too Many Requests",
  "err": "Rate limit exceeded. Please try again later.",
  "retryAfter": 45
}

The response also includes a Retry-After header with the same value as the retryAfter field, indicating how many seconds to wait before retrying your request.

Best Practices

✓Implement exponential backoff. When receiving a 429 response, wait progressively longer between retries.
✓Cache responses when possible. Reduce API calls by caching data that doesn't change frequently.
✓Monitor rate limit headers. Proactively slow down requests before hitting the limit.
✓Use bulk endpoints. When available, use batch operations instead of multiple individual requests.