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

OneBusAway default API

The default API from OneBusAway — 13 operation(s) for default.

OneBusAway default API is one of 2 APIs that OneBusAway publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and a GitHub repository.

This API exposes 13 operations across 13 paths, and defines 33 schemas. It is described by OpenAPI 3.0.0, at version 0.0.2.

Requests are made against a single base URL, https://api.pugetsound.onebusaway.org.

13 operations 13 paths 33 schemas 13 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.0.2
Base URL
https://api.pugetsound.onebusaway.org
Authentication
API Key
Resource Areas
1

Authentication & Security 1

OneBusAway default API declares 1 security scheme for authenticating requests. An API key is passed in the query as key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 13

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

default 13
GET
/api/where/agencies-with-coverage.json
Returns a list of all transit agencies currently supported by OneBusAway along with the center of their coverage area.
→ 200
GET
/api/where/schedule-for-route/{routeID}.json
Retrieve the full schedule for a route on a particular day
2 params → 200404
GET
/api/where/routes-for-location.json
routes-for-location
6 params → 200
GET
/api/where/routes-for-agency/{agencyID}.json
Retrieve the list of all routes for a particular agency by id
1 param → 200
GET
/api/where/config.json
config
→ 200
GET
/api/where/current-time.json
current-time
→ 200
GET
/api/where/stops-for-location.json
stops-for-location
6 params → 200
GET
/api/where/arrival-and-departure-for-stop/{stopID}.json
arrival-and-departure-for-stop
6 params → 200
GET
/api/where/arrivals-and-departures-for-stop/{stopID}.json
arrivals-and-departures-for-stop
4 params → 200
GET
/api/where/arrivals-and-departures-for-location.json
arrivals-and-departures-for-location
getArrivalsAndDeparturesForLocation 11 params → 200
GET
/api/where/trips-for-route/{routeID}.json
Search for active trips for a specific route.
4 params → 200
GET
/api/where/trip-details/{tripID}.json
Retrieve Trip Details
6 params → 200
GET
/api/where/trip-for-vehicle/{vehicleID}.json
Retrieve trip for a specific vehicle
5 params → 200

Schemas 33

The contract defines 33 schemas that model the data the API accepts and returns. The most detailed are ArrivalDepartureForStop (34 properties), TripStatus (27 properties), Situation (12 properties), Trip (11 properties). Each schema is shown below with its type and property counts.

TripEntry
object
6 properties 1 required
ArrivalDepartureForStopResponse
object
2 properties 2 required
TripVehicleResponse
object
2 properties 2 required
TimeWindow
object
2 properties 2 required
StopTime
object
6 properties
ResponseWrapper
object
4 properties 4 required
Reference
object
6 properties 6 required
ConfigResponse
object
2 properties 2 required
CurrentTime
object
2 properties
DetailedScheduleStopTime
object
8 properties 6 required
Coverage
object
5 properties 5 required
Situation
object
12 properties 2 required
ScheduleForRouteResponse
object
1 property 1 required
RoutesForLocationResponse
object
4 properties 3 required
Agency
object
10 properties 4 required
ArrivalsDeparturesForStopResponse
object
2 properties 2 required
StopsForLocationResponse
object
4 properties 2 required
TripWithStopTimes
object
2 properties 2 required
ArrivalsDeparturesForLocationResponse
object
2 properties 2 required
Trip
object
11 properties 3 required
CurrentTimeResponse
object
2 properties 2 required
TripDetailsResponse
object
2 properties 2 required
CoverageResponse
object
3 properties 2 required
RoutesForAgencyResponse
object
3 properties 2 required
Stop
object
11 properties 8 required
ArrivalDepartureForStop
object
34 properties 16 required
TripSchedule
object
5 properties 4 required
Config
object
5 properties
ScheduleEntry
object
4 properties 4 required
StopTripGrouping
object
5 properties 4 required
Route
object
10 properties 3 required
TripStatus
object
Trip-specific status for the arriving transit vehicle.
27 properties 16 required
TripDetails
object
6 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onebusaway-default-api-openapi.yml Raw ↑

Other APIs OneBusAway publishes across the network.

OneBusAway Where API
Where this information came from

This is an independent, third-party profile of OneBusAway default 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.