Rate Limits

Coming soon

Rate limiting is not enforced in V1 of the API. This page will be updated when limits are introduced.

What to expect

When rate limiting is enabled, the API will return standard headers on every response:

Header	Description
X-RateLimit-Limit	Maximum requests allowed per window
X-RateLimit-Remaining	Requests remaining in the current window
X-RateLimit-Reset	Unix timestamp when the window resets

If you exceed the limit, the API will respond with:

HTTP/1.1 429 Too Many Requests

{
  "error": "Rate limit exceeded. Try again in 30 seconds."
}

Recommendations

Even without enforced limits, we recommend:

• Avoid polling endpoints in tight loops -- use reasonable intervals
• Cache responses when the data doesn't change frequently
• Use bulk operations where available instead of many individual calls