Ticket Tailor · Rate Limits

Tickettailor Rate Limits

The Ticket Tailor API publishes an explicit rate limit of 5000 requests per 30 minutes per box office (API key). One endpoint, POST /v1/issued_memberships, is further limited to 30 requests per hour. Rate-limit state is returned on responses via the X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset headers, and a Retry-After header is returned when a limit is exceeded. List endpoints use cursor-based pagination (starting_after / ending_before) with a maximum of 100 results per page, which bounds the amount of data returned per request.

Tickettailor Rate Limits is the machine-readable rate-limit profile for Ticket Tailor on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and results.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Event Ticketing, Ticketing, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Event TicketingTicketingRate LimitingQuotas

Limits

Global API Requests box office (API key)
requests
5000 per 30 minutes
Applies across all endpoints for a given API key.
Issued Memberships Creation box office (API key)
requests
30 per hour
POST /v1/issued_memberships is limited more tightly than the global rate.
Pagination Page Size request
results
100 per page
List endpoints return at most 100 objects per page via cursor pagination.

Policies

Rate Limit Headers
Responses include X-Rate-Limit-Limit, X-Rate-Limit-Remaining, and X-Rate-Limit-Reset so clients can track remaining budget.
Retry-After
A Retry-After header is returned when a limit is exceeded, indicating how long to wait before retrying.
Backoff Strategy
Clients should implement exponential backoff with jitter and respect Retry-After on 429 responses.

Sources