airportsapi vs Transport for Belgium

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

Uptime · 30d
Uptime · 90d88.2%94.1%
Uptime · 30d85.0%90.0%
P50 · ms821567
P95 · ms49691576
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

airportsapi vs Transport for Belgium: common questions

Which is more reliable, airportsapi or Transport for Belgium?

On our scheduled checks, Transport for Belgium leads on measured uptime — airportsapi at 88.2% versus Transport for Belgium at 94.1% 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, airportsapi or Transport for Belgium?

Transport for Belgium has the lower median latency in our checks — airportsapi responds in 821 ms versus Transport for Belgium at 567 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 airportsapi and Transport for Belgium need an API key?

Neither needs a paid key — airportsapi is callable with no signup, and Transport for Belgium is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call airportsapi and Transport for Belgium from the browser?

Yes — both airportsapi and Transport for Belgium 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 airportsapi and Transport for Belgium free for commercial use?

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