shipapis
StarSubmit an APISubmit API

Passantenfrequenzen Zürich vs restful-api.dev

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

APIPassantenfrequenzen ZürichNEW—restful-api.devNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
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

Passantenfrequenzen Zürich vs restful-api.dev: common questions

Which is more reliable, Passantenfrequenzen Zürich or restful-api.dev?

On our scheduled checks, restful-api.dev leads on measured uptime — Passantenfrequenzen Zürich at —% versus restful-api.dev 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 Passantenfrequenzen Zürich and restful-api.dev need an API key?

Neither needs a paid key — Passantenfrequenzen Zürich is callable with no signup, and restful-api.dev is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Passantenfrequenzen Zürich and restful-api.dev from the browser?

Yes — both Passantenfrequenzen Zürich and restful-api.dev send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Passantenfrequenzen Zürich and restful-api.dev free for commercial use?

Passantenfrequenzen Zürich has unclear commercial terms, and restful-api.dev 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.