Destination-first call flow

Start by finding the destination slug, then request destination access. Use route summary or conditions only when you need more detail.

1. GET /v1/destinations
2. GET /v1/destinations/:destination/access
3. Optional: GET /v1/routes/:route/summary
4. GET /v1/conditions

Destination first

Start with GET /v1/destinations to find the destination slug. Then call GET /v1/destinations/:destination/access to get the access answer, route coverage, and the current reason.

Discovery

Use the destination list when you know the place but not the slug.

GET /v1/destinations

Destination access

Ask for the access answer once the destination slug is known.

GET /v1/destinations/big-bear/access

Route drilldown

Route summary is optional. Use GET /v1/routes/:route/summary when you want to inspect one road, such as SR-18 or SR-38, in more detail.

GET /v1/routes/SR-18/summary

Conditions detail

Use conditions last when you need segment rows, filters, or source detail.

GET /v1/conditions?jurisdiction=US-CA&route=SR-18