Sound Transit · Schema
Sound Transit Arrival And Departure
Schema for a real-time arrival or departure prediction from the Sound Transit OneBusAway API
TransitTransportationGTFSReal-TimePublic TransitGovernmentSeattle
Properties
| Name | Type | Description |
|---|---|---|
| routeId | string | Route identifier |
| tripId | string | Trip identifier |
| serviceDate | integer | Service date in milliseconds since Unix epoch |
| vehicleId | string | Vehicle identifier if known |
| stopId | string | Stop identifier |
| stopSequence | integer | Sequence number of this stop within the trip |
| scheduledArrivalTime | integer | Scheduled arrival time in milliseconds since Unix epoch |
| scheduledDepartureTime | integer | Scheduled departure time in milliseconds since Unix epoch |
| predictedArrivalTime | integer | Real-time predicted arrival time in milliseconds (0 if no prediction) |
| predictedDepartureTime | integer | Real-time predicted departure time in milliseconds (0 if no prediction) |
| predicted | boolean | Whether real-time prediction data is available for this arrival |
| status | string | Status of the arrival (ON_TIME, EARLY, DELAYED, etc.) |
| routeShortName | string | Short name/number of the route |
| tripHeadsign | string | Destination headsign displayed on the vehicle |
JSON Schema
{
"$schema": "http://json-schema.org/draft-07/schema#",
"$id": "https://raw.githubusercontent.com/api-evangelist/sound-transit/main/json-schema/sound-transit-arrival-schema.json",
"title": "Sound Transit Arrival And Departure",
"description": "Schema for a real-time arrival or departure prediction from the Sound Transit OneBusAway API",
"type": "object",
"properties": {
"routeId": {
"type": "string",
"description": "Route identifier"
},
"tripId": {
"type": "string",
"description": "Trip identifier"
},
"serviceDate": {
"type": "integer",
"format": "int64",
"description": "Service date in milliseconds since Unix epoch"
},
"vehicleId": {
"type": "string",
"description": "Vehicle identifier if known"
},
"stopId": {
"type": "string",
"description": "Stop identifier"
},
"stopSequence": {
"type": "integer",
"description": "Sequence number of this stop within the trip"
},
"scheduledArrivalTime": {
"type": "integer",
"format": "int64",
"description": "Scheduled arrival time in milliseconds since Unix epoch"
},
"scheduledDepartureTime": {
"type": "integer",
"format": "int64",
"description": "Scheduled departure time in milliseconds since Unix epoch"
},
"predictedArrivalTime": {
"type": "integer",
"format": "int64",
"description": "Real-time predicted arrival time in milliseconds (0 if no prediction)"
},
"predictedDepartureTime": {
"type": "integer",
"format": "int64",
"description": "Real-time predicted departure time in milliseconds (0 if no prediction)"
},
"predicted": {
"type": "boolean",
"description": "Whether real-time prediction data is available for this arrival"
},
"status": {
"type": "string",
"description": "Status of the arrival (ON_TIME, EARLY, DELAYED, etc.)"
},
"routeShortName": {
"type": "string",
"description": "Short name/number of the route"
},
"tripHeadsign": {
"type": "string",
"description": "Destination headsign displayed on the vehicle"
}
},
"required": ["routeId", "tripId", "stopId", "scheduledArrivalTime"]
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/sound-transit-arrival"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.