Parkleitsystem API vs Postcodes.io

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms109733
P95 · ms4508328
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedService MIT-licensed; postcode data license unverified
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished (no key; fair use)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Parkleitsystem API vs Postcodes.io: common questions

Which is more reliable, Parkleitsystem API or Postcodes.io?

Both are neck-and-neck — Parkleitsystem API and Postcodes.io 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, Parkleitsystem API or Postcodes.io?

Postcodes.io has the lower median latency in our checks — Parkleitsystem API responds in 1097 ms versus Postcodes.io at 33 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 Parkleitsystem API and Postcodes.io need an API key?

Neither needs a paid key — Parkleitsystem API is callable with no signup, and Postcodes.io is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Parkleitsystem API and Postcodes.io from the browser?

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

Are Parkleitsystem API and Postcodes.io free for commercial use?

Parkleitsystem API has unclear commercial terms, and Postcodes.io 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.