Track a team’s whole season or an artist’s whole tour

Find every upcoming date with one search, then capture each one on a schedule — and work out how many requests it takes.

1. Every date in one search

Search by team or artist without from and to to get every upcoming event. events[] groups each date across marketplaces with its ID on each.

2. Budget your requests

Requests = events × captures per event. A 41-game home season captured once a day for 30 days is about 1,230 requests a month; capturing only the next 10 games daily is about 300.

Limiting a search to one marketplace with the marketplaces parameter makes it use one request instead of five.

3. Capture on a schedule

Capture each event, spacing calls to stay inside your hourly limit. Use wait: 0 and a webhook for large events so your job doesn’t block.