shipapis
StarSubmit an APISubmit API

Parkleitsystem API vs Administrative Divisions DB

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

APIParkleitsystem APINEW—Administrative Divisions DBNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (see repo)
Free tierFree — limits not publishedFree, no API key required (static JSON via CDN)
Rate limitUnpublishedNone (static files served over CDN)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Parkleitsystem API vs Administrative Divisions DB: common questions

Which is more reliable, Parkleitsystem API or Administrative Divisions DB?

On our scheduled checks, Administrative Divisions DB leads on measured uptime — Parkleitsystem API at —% versus Administrative Divisions DB 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 Parkleitsystem API and Administrative Divisions DB need an API key?

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

Can I call Parkleitsystem API and Administrative Divisions DB from the browser?

Only Administrative Divisions DB 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 Administrative Divisions DB free for commercial use?

Parkleitsystem API has unclear commercial terms, and Administrative Divisions DB 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.