BVG transport.rest vs StayingAPI
Same instrument, two spec sheets — measured, not claimed.
BVG transport.rest vs StayingAPI: common questions
Which is more reliable, BVG transport.rest or StayingAPI?
On our scheduled checks, StayingAPI leads on measured uptime — BVG transport.rest at 67.2% versus StayingAPI at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, BVG transport.rest or StayingAPI?
StayingAPI has the lower median latency in our checks — BVG transport.rest responds in 930 ms versus StayingAPI at 143 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 BVG transport.rest and StayingAPI need an API key?
BVG transport.rest needs no key, while StayingAPI requires a free API key. If you want to start calling without signup, reach for BVG transport.rest first.
Can I call BVG transport.rest and StayingAPI from the browser?
Only BVG transport.rest 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 BVG transport.rest and StayingAPI free for commercial use?
BVG transport.rest has unclear commercial terms, and StayingAPI 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.