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, in the API Commons Rate Limits shape.

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

Limit state is signalled in the limit, remaining, over, and reset response headers, and an exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429 limitremainingoverreset
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/ticketmaster-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.