Eventbrite API vs FindLocal API

Two free Events APIs compared on access, reliability and developer ratings, using data from our daily health checks.

The verdict

Choose Eventbrite API if its data fits your use case better; on access and reliability it's level with FindLocal API.
Choose FindLocal API if you want to call it from browser JavaScript, faster responses.

	Eventbrite API	FindLocal API
What it does	Internal / public / partners API documentation, replacing Apiary.io.	Hyper-local US events: concerts, trivia, open mics, readings, storytimes.
Provider	Eventbrite	findlocal.community
API key	OAuth	Required
HTTPS	Yes	Yes
CORS (browser calls)	Unknown	Yes
Status today	Online · 3105 ms	Online · 685 ms
Uptime (30 days)	Up	Up
Developer rating	Not rated yet	Not rated yet
Price	Free / free tier	Free / free tier

Internal / public / partners API documentation, replacing Apiary.io.

Internal / public / partners API documentation, replacing Apiary.io

Strengths

Hyper-local US events: concerts, trivia, open mics, readings, storytimes.

Strengths

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.

Both require authentication (OAuth and apiKey).

FindLocal API supports CORS, so front-end JavaScript can call it directly. Call the other from a server.