Build with MyBusz
MyBusz provides live bus arrivals, vehicle positions, and route data for rider apps, passenger displays, and transit feeds.
Choose an API
Section titled “Choose an API”| Frontline (recommended) | GTFS-RT | |
|---|---|---|
| Best for | Rider apps, passenger displays, and maps | Systems that already consume GTFS Realtime |
| Data | Stop search, arrivals, route details, and live bus positions | Trip updates and vehicle positions |
| Updates | Unary calls, plus streams that push full snapshots | Polling, up to 10 requests/minute per feed |
| Protocol | Native gRPC or gRPC-Web | HTTP GET, binary Protocol Buffers |
Both use an access token from Identity with the
frontline:consumer scope. No admin role is required.
Getting access
Section titled “Getting access”Self-service registration is currently unavailable. External integrators get access through a service account registered under an approved MyBusz admin. See get access.
API reference
Section titled “API reference”The API reference is generated from the service contracts on every build. A new endpoint can appear there, marked Documentation pending, before its guide is written; that does not promise it is available in production. Admin endpoints are excluded.