Loket.nl API vs PostcodeData.nl
Same instrument, two spec sheets — measured, not claimed.
Loket.nl API vs PostcodeData.nl: common questions
Which is more reliable, Loket.nl API or PostcodeData.nl?
Both are neck-and-neck — Loket.nl API and PostcodeData.nl each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, Loket.nl API or PostcodeData.nl?
Loket.nl API has the lower median latency in our checks — Loket.nl API responds in 361 ms versus PostcodeData.nl at 692 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 PostcodeData.nl need an API key?
Neither needs a paid key — Loket.nl API is callable with no signup, and PostcodeData.nl is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Loket.nl API and PostcodeData.nl from the browser?
Only Loket.nl API is browser-friendly — it returns CORS headers over HTTPS. PostcodeData.nl needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are Loket.nl API and PostcodeData.nl free for commercial use?
Loket.nl API has unclear commercial terms, and PostcodeData.nl 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.