Ticketmaster · Rate Limits

Ticketmaster Rate Limits

Ticketmaster's developer documentation publishes a default Discovery API quota of 5,000 requests per day at 5 requests per second per API key. The FAQ describes the same Discovery quota as "2 requests per second and 5000 requests per day"; the higher 5/sec figure appears in the Getting Started guide and is the more permissive published number. Higher limits are granted case by case after compliance and branding review. Usage is exposed via Rate-Limit response headers, with HTTP 429 returned on overage.

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

It captures 3 rate-limit definitions, measuring requests_per_day and requests_per_second.

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

Tagged areas include Events, Tickets, and Rate Limiting.

3 Limits Throttle: 429
EventsTicketsRate Limiting

Limits

Discovery API daily quota (default) api-key
requests_per_day · day
5000
Documented in Getting Started and FAQ as the default per-key daily quota.
Discovery API throughput (default) api-key
requests_per_second · second
5
Getting Started guide documents 5 requests/second; the FAQ cites 2 requests/second for the Discovery API. Treat 5 rps as the upper documented default and back off on 429.
Discovery Feed (Partner) partner-account
requests_per_day
see partner agreement
Partner-only Discovery Feed has "no call restrictions" with hourly data refresh; effectively unmetered for approved partners.

Policies

Quota Increase Process
Higher rate limits are granted case by case after Ticketmaster verifies compliance with Terms of Service, branding guidelines, and accurate representation of Ticketmaster data.
Backoff Strategy
Honor the Rate-Limit-Reset timestamp on 429 responses; the Rate-Limit-Available header lets clients pace requests proactively.
Partner Tier Alternative
Applications that consistently exceed the public Discovery quota should apply for the Discovery Feed instead of repeatedly polling the Discovery API.

Sources