shipapis
StarSubmit an APISubmit API

Parkleitsystem API vs SLF

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

APIParkleitsystem APIHEALTHY86SLFHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1097213
P95 · ms4508668
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — static file, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Parkleitsystem API vs SLF: common questions

Which is more reliable, Parkleitsystem API or SLF?

Both are neck-and-neck — Parkleitsystem API and SLF 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 SLF?

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

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

Can I call Parkleitsystem API and SLF from the browser?

Only SLF 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 SLF free for commercial use?

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