Currents vs Data.parliament.uk API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Currents vs Data.parliament.uk API: common questions

Which is more reliable, Currents or Data.parliament.uk API?

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

Do Currents and Data.parliament.uk API need an API key?

Both ask you to authenticate — Currents uses an API key and Data.parliament.uk API uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Currents and Data.parliament.uk API from the browser?

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

Are Currents and Data.parliament.uk API free for commercial use?

Currents has unclear commercial terms, and Data.parliament.uk API 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.