01
Start broad
GET /v1/destinations List destinations first if you do not know the slug yet.
Developers
Introduction
Start with a question
DEVELOPER REFERENCE
One call answers "Can I get to Big Bear?"
Get the access state, route coverage, and the current reason in one response.
01 · WORKED EXAMPLE
Walk through Big Bear
Start with Big Bear access, then check route summary or conditions if you need more detail.
Open walkthrough
Call sequence
- 1
GET /v1/destinations - 2
GET /v1/destinations/big-bear/access - 3
GET /v1/routes/SR-18/summary - 4
GET /v1/conditions
The flow in three calls
Start with
GET /v1/destinations, answer the access question
with
GET /v1/destinations/:destination/access, use
GET /v1/routes/:route/summary
for one road, and use
GET /v1/conditions
for segment detail and filters.
02
Answer the destination question
GET /v1/destinations/:destination/access Get the access answer, route coverage, and current reason.
03
Check one road
GET /v1/routes/:route/summary Use route summary for one specific road.
04
See segment detail
GET /v1/conditions Use conditions for segment detail and filters.
When to use which call
Use destination endpoints for access answers, route summary for one road, and conditions for segment detail.
| Question | Call | Why |
|---|---|---|
| Can I get to a destination right now? | GET /v1/destinations/:destination/access | Use destination access when you already know the destination. |
| I already know the destination slug. | GET /v1/destinations/:destination/access | Use the same endpoint when you already have the slug. |
| I need detail for one known route. | GET /v1/routes/:route/summary | Use route summary for one specific road. |
| I need segment-level detail or debugging filters. | GET /v1/conditions | Use conditions for segment detail and filters. |
Keep going
Go from the overview to Try it, the OpenAPI spec, or llms.txt.