Fixer API vs Open Data Minneapolis

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d99.44%98.3%
Uptime · 30d100%96.7%
P50 · ms286382
P95 · ms8303677
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fixer API vs Open Data Minneapolis: common questions

Which is more reliable, Fixer API or Open Data Minneapolis?

On our scheduled checks, Fixer API leads on measured uptime — Fixer API at 99.44% versus Open Data Minneapolis at 98.3% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Fixer API or Open Data Minneapolis?

Fixer API has the lower median latency in our checks — Fixer API responds in 286 ms versus Open Data Minneapolis at 382 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Fixer API and Open Data Minneapolis need an API key?

Open Data Minneapolis needs no key, while Fixer API requires a free API key. If you want to start calling without signup, reach for Open Data Minneapolis first.

Can I call Fixer API and Open Data Minneapolis from the browser?

Only Open Data Minneapolis is browser-friendly — it returns CORS headers over HTTPS. Fixer API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Fixer API and Open Data Minneapolis free for commercial use?

Fixer API has unclear commercial terms, and Open Data Minneapolis has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.