Paginate and sort large SeatGeek Platform API result sets efficiently
domain: seatgeek.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use per_page (default 10) and page (1-indexed) query params on any bulk endpoint (/events, /venues, /performers).
Read meta.total, meta.page, and meta.per_page in the response to drive your pagination loop.
Add sort=<field>.<asc|desc> to control ordering — events default to datetime_utc.asc, while venues/performers default to score.desc.
Use the id argument (comma-separated or repeated) to bulk-fetch known records instead of paging through unrelated results.
Known gotchas
Passing the id argument overrides all other filters on that request — don't mix it with search filters and expect them to combine.
SeatGeek's own developer forum notes the docs don't publish a hard maximum for per_page — don't assume very large page sizes are safe or performant; test empirically and prefer looping with page for big result sets.
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?