shipapis
StarSubmit an APISubmit API

StayingAPI vs Transport for Sweden

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

APIStayingAPIREACHABLE100Transport for SwedenHEALTHY71
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms143518
P95 · ms9131762
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key required
Rate limit60 req/window · 58 remaining
In directory since2026-09-212026-07-05
operationalpartialdownno data

StayingAPI vs Transport for Sweden: common questions

Which is more reliable, StayingAPI or Transport for Sweden?

Both are neck-and-neck — StayingAPI and Transport for Sweden 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, StayingAPI or Transport for Sweden?

StayingAPI has the lower median latency in our checks — StayingAPI responds in 143 ms versus Transport for Sweden at 518 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 StayingAPI and Transport for Sweden need an API key?

Both ask you to authenticate — StayingAPI uses an API key and Transport for Sweden uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call StayingAPI and Transport for Sweden from the browser?

Only Transport for Sweden is browser-friendly — it returns CORS headers over HTTPS. StayingAPI needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are StayingAPI and Transport for Sweden free for commercial use?

StayingAPI has unclear commercial terms, and Transport for Sweden 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.