---
title: "JSON - Path Details"
method: GET
path: "/json/jRouteDetails"
---

# JSON - Path Details

`GET /json/jRouteDetails`

<h4 class="text-primary">Description</h4>

<p>For a given date, returns the set of ordered latitude/longitude points along
a route variant along with the list of stops served.</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>Direction0/Direction1</td>

<td>
Structures describing <a href="#Direction">path/stop</a>
information.<br>
<br>
Most routes will return content in both Direction0 and
Direction1 elements, though a few will return NULL for Direction0 or for Direction1.<br>
<br>
0 or 1 are binary properties. There is no specific mapping to
direction, but a different value for the same route signifies
that the route is in an opposite direction.
</td>
</tr>

<tr>
<td>Name</td>

<td>Descriptive name for the route.</td>
</tr>

<tr>
<td>RouteID</td>

<td>Bus route variant (e.g.: 10A, 10Av1, etc.).</td>
</tr>

<tr>
<td colspan="2">
<div class="text-primary" style="margin-top: 1em">
<a id="Direction" name="Direction">Direction0/Direction1
Elements</a>
</div>
</td>
</tr>

<tr>
<td style="text-decoration: line-through">DirectionNum</td>

<td><span class="text-danger">Deprecated.</span> Use the
DirectionText element to denote the general direction of the route
variant.</td>
</tr>

<tr>
<td>DirectionText</td>

<td>General direction of the route variant (NORTH, SOUTH, EAST,
WEST, LOOP, etc.).</td>
</tr>

<tr>
<td>Shape</td>

<td>
Array containing shape point information (<a href=
"#ShapePoint">ShapePoint</a>).
</td>
</tr>

<tr>
<td>Stops</td>

<td>
Array containing stop information (<a href="#Stop">Stop</a>).
</td>
</tr>

<tr>
<td>TripHeadsign</td>

<td>Descriptive text of where the bus is headed. This is similar,
but not necessarily identical, to what is displayed on the
bus.</td>
</tr>

<tr>
<td colspan="2">
<div class="text-primary" style="margin-top: 1em">
<a id="ShapePoint" name="ShapePoint">ShapePoint
Elements</a>
</div>
</td>
</tr>

<tr>
<td>Lat</td>

<td>Latitude.</td>
</tr>

<tr>
<td>Lon</td>

<td>Longitude.</td>
</tr>

<tr>
<td>SeqNum</td>

<td>Order of the point in the sequence of ShapePoints.</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

- `RouteID` '70', 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)
