action wmata_5476365e031f5909e4fe331d { label: "JSON - Next Buses" description: "

Description

\n \n

Returns next bus arrival times at a stop.

\n \n

Response Elements

\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
ElementDescription
Predictions \nArray containing bus predictions (NextBusPrediction). \n
StopNameFull name of the given StopID.
\n \n
DirectionNumDenotes a binary direction (0 or 1) of the bus. There is no \nspecific mapping to direction, but a different value for the same \nroute signifies that the buses are traveling in opposite \ndirections. Use the DirectionText element to show the actual \ndestination of the bus.
DirectionTextCustomer-friendly description of direction and destination for \na bus.
MinutesMinutes until bus arrival at this stop. Numeric value.
RouteIDBase route name as shown on the bus. This can be used in other \nbus-related methods. Note that all variants will be shown as their \nbase route names (i.e.: 10Av1 and 10Av2 will be shown as 10A).
TripIDTrip identifier. This can be correlated with the data in our \nbus schedule information as well as bus positions.
VehicleIDBus identifier. This can be correlated with results returned \nfrom bus positions.
" provider: wmata method: GET path: "/json/jPredictions" encoding: json input: { type: "object" properties: { StopID: { type: "string" } } required: ["StopID"] additionalProperties: false } output: { type: "object" additionalProperties: true } }