MountainSwitch Know before you go.

Search and menu

Search for a destination, or browse routes, system status, documentation, and legal links.

Area
Area All areas
Activity
Activity Any activity

Developers

Call flow

START HERE

Destination-first call flow

Start by finding the place in the complete consumer catalog and inspecting its endpoint markers. Request destination access only when endpoints.access is true; 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 the consumer-place catalog to find the slug and inspect capability markers. Then call destination access only when endpoints.access is true.

Discovery

Use the catalog when you know the place but not the slug or supported follow-up endpoints.

GET /v1/destinations

Destination access

Ask for the access answer once the slug is known and its access marker is true.

GET /v1/destinations/big-bear/access

Route drilldown

Route summary is optional. Use it 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