Handle Ticketmaster Discovery API rate limits and deep-paging constraints in a production integration
domain: developer.ticketmaster.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Track the default quota (5000 calls/day, 5 requests/second) and back off before hitting it.
Read the Rate-Limit and Rate-Limit-Reset response headers to monitor remaining quota and reset time.
Handle HTTP 429 responses by waiting until the reset time before retrying.
Respect the deep-paging ceiling: size × page must stay under 1000, so shrink size if you need to reach deeper pages.
Follow the HAL-style _links.next link in responses to paginate rather than hand-building page URLs.
Known gotchas
Once size × page exceeds the 1000-item ceiling, the API stops returning results no matter how you split page/size — you have to narrow your query (date range, filters) to go deeper instead.
Rate limit increases are granted case-by-case and require passing Ticketmaster's Terms of Service and branding-guide compliance review.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?