How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

TransportAPI Bus Information API

Real-time and scheduled bus departure and arrival data

TransportAPI Bus Information API is one of 4 APIs that TransportAPI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Bus Information. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 1 JSON Schema.

This API exposes 3 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version v3.0.0.

Requests are made against a single base URL, https://transportapi.com/v3/uk.

3 operations 3 paths 5 schemas 3 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v3.0.0
Base URL
https://transportapi.com/v3/uk
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

TransportAPI Bus Information API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-App-Id (AppIdAuth). An API key is passed in the header as X-App-Key (AppKeyAuth). By default, every request must be authenticated.

  • AppIdAuth — Application ID header
  • AppKeyAuth — Application key header

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 GET. Each is listed below with its method, path, parameters, and response codes.

Bus Information 3

Real-time and scheduled bus departure and arrival data

GET
/bus/stop/{atcocode}/live.json
Get Bus Stop Live Departures
getBusStopLiveDepartures 6 params → 200401404
GET
/bus/stop/{atcocode}/timetable.json
Get Bus Stop Timetable
getBusStopTimetable 4 params → 200401
GET
/bus/route/{operator}/{line}/{direction}/{atcocode}/{date}/timetable.json
Get Bus Route Timetable
getBusRouteTimetable 7 params → 200

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are BusDeparture (11 properties), BusLiveDeparturesResponse (5 properties), BusTimetableResponse (4 properties), BusRouteTimetableResponse (4 properties). Each schema is shown below with its type and property counts.

BusDeparture
object
11 properties
TimetableStop
object
3 properties
BusRouteTimetableResponse
object
4 properties
BusLiveDeparturesResponse
object
5 properties
BusTimetableResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

transportapi-bus-information-api-openapi.yml Raw ↑

Other APIs TransportAPI publishes across the network.

TransportAPI Journey Planner API
TransportAPI Places API
TransportAPI Rail Information API
Where this information came from

This is an independent, third-party profile of TransportAPI Bus Information API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.