---
title: "XML - Schedule at Stop"
method: GET
path: "/StopSchedule"
---

# XML - Schedule at Stop

`GET /StopSchedule`

<h4 class="text-primary">Description</h4>

<p>Returns a set of buses scheduled at a stop for a given date.</p>

<h4 class="text-primary">Response Elements</h4>

<table class="table table-condensed table-hover">
<thead>
<tr>
<th class="col-md-3">Element</th>

<th>Description</th>
</tr>
</thead>

<tbody>
<tr>
<td>ScheduleArrivals</td>

<td>
Array containing scheduled arrival information (<a href=
"#ScheduleArrival">ScheduleArrival</a>).
</td>
</tr>

<tr>
<td>Stop</td>

<td>
Structure describing <a href="#Stop">stop</a> information.
</td>
</tr>

<tr>
<td colspan="2">
<div class="text-primary" style="margin-top: 1em">
<a id="ScheduleArrival" name=
"ScheduleArrival">ScheduleArrival Elements</a>
</div>
</td>
</tr>

<tr>
<td>DirectionNum</td>

<td>Denotes a binary direction (0 or 1) of the bus. There is no
specific mapping to direction, but a different value for the same
route signifies that the buses are traveling in opposite
directions. Use the TripDirectionText element to show the actual
destination of the bus.</td>
</tr>

<tr>
<td>EndTime</td>

<td>Scheduled end date and time (Eastern Standard Time) for this
trip. Will be in YYYY-MM-DDTHH:mm:ss format (e.g.:
2014-10-27T13:17:00).</td>
</tr>

<tr>
<td>RouteID</td>

<td>Bus route variant identifier (pattern). This variant can be
used in several other bus methods which accept variants. Note that
customers will never see anything other than the base route name,
so variants 10A, 10Av1, 10Av2, etc. will be displayed as 10A on the
bus.</td>
</tr>

<tr>
<td>ScheduleTime</td>

<td>Date and time (Eastern Standard Time) when the bus is scheduled
to stop at this location. Will be in YYYY-MM-DDTHH:mm:ss format
(e.g.: 2014-10-27T13:17:00).</td>
</tr>

<tr>
<td>StartTime</td>

<td>Scheduled start date and time (Eastern Standard Time) for this
trip. Will be in YYYY-MM-DDTHH:mm:ss format (e.g.:
2014-10-27T13:17:00).</td>
</tr>

<tr>
<td>TripDirectionText</td>

<td>General direction of the trip (e.g.: NORTH, SOUTH, EAST,
WEST).</td>
</tr>

<tr>
<td>TripHeadsign</td>

<td>Destination of the bus.</td>
</tr>

<tr>
<td>TripID</td>

<td>Trip identifier. This can be correlated with the data in our
bus schedule information as well as bus positions.</td>
</tr>

<tr>
<td colspan="2">
<div class="text-primary" style="margin-top: 1em">
<a id="Stop" name="Stop">Stop Elements</a>
</div>
</td>
</tr>

<tr>
<td>Lat</td>

<td>Latitude.</td>
</tr>

<tr>
<td>Lon</td>

<td>Longitude.</td>
</tr>

<tr>
<td>Name</td>

<td>Stop name. May be slightly different from what is spoken or
displayed in the bus.</td>
</tr>

<tr>
<td>Routes</td>

<td>String array of route variants which provide service at this
stop. Note that these are not date-specific; any route variant
which stops at this stop on any day will be listed.</td>
</tr>

<tr>
<td>StopID</td>

<td>7-digit regional ID which can be used in various bus-related
methods. If unavailable, the StopID will be 0 or NULL.</td>
</tr>
</tbody>
</table>

## Query parameters

- `StopID` '1001195', required
- `Date` string

## Response `200`

Default response code.

---

[API](https://skmtc.net/wmata/apis/bus-route.md) · [All operations](https://skmtc.net/wmata/apis/bus-route/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/wmata/bus-route/versions/35c18770f085/schema)