Open-Elevation API vs PostcodeData.nl

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

Uptime · 30d
Uptime · 90d92.2%100%
Uptime · 30d88.3%100%
P50 · ms739692
P95 · ms42871989
Authnonenone
CORSyesyes
HTTPSyesno
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

Open-Elevation API vs PostcodeData.nl: common questions

Which is more reliable, Open-Elevation API or PostcodeData.nl?

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

PostcodeData.nl has the lower median latency in our checks — Open-Elevation API responds in 739 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 Open-Elevation API and PostcodeData.nl need an API key?

Neither needs a paid key — Open-Elevation 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 Open-Elevation API and PostcodeData.nl from the browser?

Only Open-Elevation 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 Open-Elevation API and PostcodeData.nl free for commercial use?

Open-Elevation 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.