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 All United Kingdom APIs# Confirm the provider's authentication format and endpoint in its documentation before making a request. # https://www.gov.uk/government/publications/bus-open-data-implementation-guide/bus-open-data-implementation-guide
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://www.gov.uk/government/publications/bus-open-data-implementation-guide/bus-open-data-implementation-guide) 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://www.gov.uk/government/publications/bus-open-data-implementation-guide/bus-open-data-implementation-guide) Source type: Official public feed Endpoint type: Public feed, non-JSON Integration difficulty: Needs API key Last checked: 2026-07-05 Production caveat: The official implementation guide is reachable and explains registration and formats. The technical BODS guidance URL still returned HTTP 403 from the audit host; account access remains untested. 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.