Rate Limiting

To ensure API stability and fair usage, we apply rate limiting to all requests. Our rate limiter operates on a sliding window basis.

The Limits

The primary rate limit is based on the API key used for the request. Currently, the limit is 10 requests per 10 seconds.

If you exceed this limit, the API will respond with an HTTP 429 Too Many Requests error.

json

{ "error": "Too Many Requests." }

Rate Limit Headers

Every API response includes the following headers to help you track your current rate limit status.

X-RateLimit-Limit: The maximum number of requests allowed in the current window.
X-RateLimit-Remaining: The number of requests remaining in the current window.
X-RateLimit-Reset: The timestamp (in seconds since the epoch) when the rate limit window will reset.

Note

Handle 429 errors gracefully

We recommend building a small utility in your application that gracefully handles 429 errors, potentially with an exponential backoff retry strategy, using these headers.

Plan-Based Usage Quotas

In addition to rate limiting, your account is subject to a monthly usage quota based on your subscription plan (e.g., total post views). If you exceed your plan's soft limit, your requests will still succeed, but they will include a X-Usage-Warning header. If you exceed the hard limit (your plan's quota + a small buffer), your requests will be blocked with a 403 Forbidden error.