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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
OneBusAway

OneBusAway Where API

The Where API from OneBusAway — 17 operation(s) for where.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

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

This API exposes 17 operations across 17 paths, and defines 40 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.

17 operations 17 paths 40 schemas 17 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 Where 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 17

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

Where 17
GET
/api/where/agency/{agencyID}.json
Retrieve info for a specific transit agency identified by ID
1 param → 200
GET
/api/where/route/{routeID}.json
Retrieve info for a specific route identified by ID
1 param → 200
GET
/api/where/route-ids-for-agency/{agencyID}.json
Get route IDs for a specific agency
1 param → 200
GET
/api/where/vehicles-for-agency/{agencyID}.json
Get vehicles for a specific agency
2 params → 200
GET
/api/where/trip/{tripID}.json
Get details of a specific trip
1 param → 200
GET
/api/where/trips-for-location.json
Retrieve trips for a given location
7 params → 200
GET
/api/where/stops-for-route/{routeID}.json
Get stops for a specific route
3 params → 200
GET
/api/where/stops-for-agency/{agencyID}.json
Get stops for a specific agency
1 param → 200
GET
/api/where/stop/{stopID}.json
Get details of a specific stop
1 param → 200
GET
/api/where/schedule-for-stop/{stopID}.json
Get schedule for a specific stop
2 params → 200
GET
/api/where/stop-ids-for-agency/{agencyID}.json
Get stop IDs for a specific agency
1 param → 200
GET
/api/where/report-problem-with-stop/{stopID}.json
Submit a user-generated problem report for a stop
reportProblemWithStop 6 params → 200
GET
/api/where/report-problem-with-trip/{tripID}.json
Submit a user-generated problem report for a particular trip.
reportProblemWithTrip 11 params → 200
GET
/api/where/search/stop.json
Search for a stop based on its name.
searchStop 2 params → 200404
GET
/api/where/search/route.json
Search for a route based on its name.
searchRoute 2 params → 200404
GET
/api/where/block/{blockID}.json
Get details of a specific block by ID
1 param → 200
GET
/api/where/shape/{shapeID}.json
Retrieve a shape by ID
1 param → 200

Schemas 40

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

BlockResponse
object
2 properties 2 required
ScheduleForStopEntry
object
3 properties 3 required
StopGrouping
object
4 properties
StopsForRouteResponse
object
2 properties 2 required
TripsForLocationResponse
object
4 properties 2 required
BlockEntry
object
2 properties 2 required
TimeWindow
object
2 properties 2 required
StopTime
object
6 properties
SearchStopResponse
object
4 properties 3 required
ResponseWrapper
object
4 properties 4 required
VehicleStatus
object
11 properties 3 required
StopsForAgencyResponse
object
4 properties 2 required
BlockConfiguration
object
3 properties 2 required
Reference
object
6 properties 6 required
StopRouteSchedule
object
2 properties 2 required
Location
object
2 properties
StopIDsForAgencyResponse
object
3 properties 2 required
RouteResponse
object
2 properties 2 required
ScheduleFrequency
object
6 properties 6 required
Situation
object
12 properties 2 required
StopRouteDirectionSchedule
object
3 properties 2 required
Agency
object
10 properties 4 required
SearchRouteResponse
object
4 properties 3 required
StopResponse
object
2 properties 2 required
VehiclesForAgencyResponse
object
3 properties 2 required
TripDetails
object
6 properties 3 required
ScheduleForStopResponse
object
2 properties 2 required
BlockStopTime
object
4 properties 4 required
ScheduleStopTime
object
7 properties 6 required
Trip
object
11 properties 3 required
BlockTrip
object
4 properties 4 required
Polylines
object
3 properties
RouteIDsForAgencyResponse
object
3 properties 2 required
Stop
object
11 properties 8 required
TripSchedule
object
5 properties 4 required
TripResponse
object
2 properties 2 required
AgencyResponse
object
2 properties 2 required
Route
object
10 properties 3 required
TripStatus
object
Trip-specific status for the arriving transit vehicle.
27 properties 16 required
ShapeResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

onebusaway-where-api-openapi.yml Raw ↑

Other APIs OneBusAway publishes across the network.

OneBusAway default API
AE Profile APIs.io
#Where
← Back to O APIs
API Details
ID
onebusaway:onebusaway-where-api
Base URL
https://api.pugetsound.onebusaway.org
Docs
https://developer.onebusaway.org/api/where
Provider
OneBusAway
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=onebusaway-where-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/onebusaway-where-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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