SeatDataDocs

Rate Limits

How SeatData API rate limits work — discovering your current limits and handling 429 responses.

Rate limits apply per API key.

Discovering Your Limits

Current limits for each endpoint are returned at runtime:

  • The rate_limits object from GET /v1/account lists the limit and time window for every endpoint group.
  • Each response includes X-RateLimit-Limit and X-RateLimit-Remaining headers (rolling out).

Treat the /v1/account catalog and the response headers as the authoritative source — limit values are subject to change and should not be hard-coded from documentation.

Handling 429 Responses

When a request exceeds a limit:

  • v1 endpoints return a structured error envelope including a Retry-After header.
  • v0.x endpoints return plain text Too Many Requests with the same Retry-After semantics.

Use exponential backoff with jitter when retrying.

Support

For questions about rate limits, contact support@seatdata.io.

On this page