SeatGeek API
Search events, venues and performers.
Strengths
- HTTPS
vs
SeatGeek API vs Ticketmaster API
Two free Events APIs compared on access, reliability and developer ratings, using data from our daily health checks.
The verdict
- Choose SeatGeek API if you want faster responses.
- Choose Ticketmaster API if its data fits your use case better; on access and reliability it's level with SeatGeek API.
Side by side
| SeatGeek API | Ticketmaster API | |
|---|---|---|
| What it does | Search events, venues and performers. | Search events, attractions, or venues. |
| Provider | platform.seatgeek.com | The Ticketmaster |
| API key | Required | Required |
| HTTPS | Yes | Yes |
| CORS (browser calls) | Unknown | Unknown |
| Status today | Online · 569 ms | Online · 1912 ms |
| Uptime (30 days) | Up | Up |
| Developer rating | Not rated yet | Not rated yet |
| Price | Free / free tier | Free / free tier |
About each API
Ticketmaster API
Search events, attractions, or venues.
Everything you need to start playing with the Ticketmaster API
Strengths
- HTTPS
How to choose between them
- Prototyping or a tutorial? Pick the one that needs no API key (neither does, so compare their free tiers).
- Calling from a web page? You need CORS. Otherwise route requests through your own server or a serverless function.
- Going to production? Favour HTTPS, a strong uptime record and a provider with clear rate limits and terms. Check each API's docs before you commit.
- Still unsure? Both are free to try: send one request to each and compare the data you get back.
SeatGeek vs Ticketmaster FAQ
Do SeatGeek API and Ticketmaster API need an API key?
Both require authentication (apiKey and apiKey).
More comparisons
SeatGeek API alternatives · Ticketmaster API alternatives · best Events APIs