JSON Response
Key | Value | Description |
---|---|---|
| The Exit object defined by the supplied | |
| [Optional] The Exit object for essentially the same exit, only that it's accessed from the other side of the highway. For example, if the supplied With | |
| [Optional] The Exit object that comes immediately before this Exit for the given direction of travel. If this is the first exit on the highway, | |
| [Optional] The Exit object that comes immediately after this Exit for the given direction of travel. If this is the last exit on the highway, | |
| Array of Categorys | Array of Category objects. If a Category is present for a given exit, that means there is at least one Business / POI at that exit that fits into that Category. The Category's Business / POIs can be retrieved with the |
The Exit Details allows the user to retrieve all information we have on a particular exit.
They can optionally choose to have related exits returned with the result, including the previous_exit
, the next exit
, and the reverse_exit
as seen from the reverse direction of the Highway. This allows for features such as quickly scrolling to the previous/next Exit, or changing direction of travel.
The user can also retrieve all businesses
found at this Exit, ordered by Category (Gas, Food, etc). Since an exit_id
implies the direction of travel (Exit 13 Northbound has a different exit_id
than Exit 13 Southbound), we can include relational directions like Right/Left and mileage from the off ramp.

The 'Exit Details' API in use inside the iExit Android app
Common Next API(s)
- POI Details (by using
categories[]
.businesses[]
.id
) - Exit Details (by using
reverse_exit
.id
,previous_exit
.id
, ornext_exit
.id
)