PASAR API
Free but requires a BODS account for an API key; separate endpoints for timetables (TransXChange), fares (NeTEx) and live vehicle positions (GTFS-RT / SIRI-VM); England only.
View docs ↗ More Travel & mobility APIs# DfT ~ Bus Open Data Service (timetables & live GPS) needs an API key ~ get yours at: # https://data.bus-data.dft.gov.uk/guidance/requirements/ curl 'https://data.bus-data.dft.gov.uk/api/v1/' \ -H 'Authorization: Bearer YOUR_TOKEN'
I'm integrating a United Kingdom API into my app. API: DfT ~ Bus Open Data Service (timetables & live GPS) Provider: Department for Transport Auth: requires an API key (sign up: https://data.bus-data.dft.gov.uk/guidance/requirements/) Pricing: free Base URL: https://data.bus-data.dft.gov.uk/api/v1/ Important note: Free but requires a BODS account for an API key; separate endpoints for timetables (TransXChange), fares (NeTEx) and live vehicle positions (GTFS-RT / SIRI-VM); England only. Source: Department for Transport (https://data.bus-data.dft.gov.uk/guidance/requirements/) Source type: Official public feed Endpoint type: Public feed, non-JSON Integration difficulty: Needs API key Last checked: 2026-07-05 Production caveat: Keep credentials server-side and confirm current limits, pricing, and webhook/error behaviour in the provider docs. Help me set up the correct onboarding/authentication path and make the first valid request ~ explain exactly where credentials go and what must happen before production.