Loket.nl API vs Open Topo Data

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

Uptime · 30d
Uptime · 90d100%91.7%
Uptime · 30d100%95.0%
P50 · ms118187
P95 · ms10391260
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Loket.nl API vs Open Topo Data: common questions

Which is more reliable, Loket.nl API or Open Topo Data?

On our scheduled checks, Loket.nl API leads on measured uptime — Loket.nl API at 100% versus Open Topo Data at 91.7% 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, Loket.nl API or Open Topo Data?

Loket.nl API has the lower median latency in our checks — Loket.nl API responds in 118 ms versus Open Topo Data at 187 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 Loket.nl API and Open Topo Data need an API key?

Neither needs a paid key — Loket.nl API is callable with no signup, and Open Topo Data is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Loket.nl API and Open Topo Data from the browser?

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

Are Loket.nl API and Open Topo Data free for commercial use?

Loket.nl API has unclear commercial terms, and Open Topo Data 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.