01
Start broad
GET /v1/destinations Search the complete consumer-place catalog, then inspect endpoint markers before choosing a follow-up call.
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
Find Big Bear in the complete place catalog, verify its access marker, 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 the complete consumer-place catalog and inspect its endpoint markers. Answer the access question only for access-capable places, use route summary for one road, and open conditions when you need segment detail or 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 | GET endpoint | Why |
|---|---|---|
| Can I get to a destination right now? | /v1/destinations/:destination/access | Use destination access when you already know the destination. |
| I already know the destination slug. | /v1/destinations/:destination/access | Use the same endpoint when you already have the slug. |
| I need detail for one known route. | /v1/routes/:route/summary | Use route summary for one specific road. |
| I need segment-level detail or debugging filters. | /v1/conditions | Use conditions for segment detail and filters. |
Keep going
Go from the overview to Try it, the OpenAPI spec, or llms.txt.