Read-only access
Inspect the same bounded responses used by the interface—without starting a provider request or changing stored data.
GET /traffic/latest?corridor=I25
200 OK · application/json
{
"corridor": "I25",
"polledAt": "…Z",
"avgCurrentSpeed": 67.4
}
Request path
Every example stays inside the same rules used by the dashboard.
Live explorer
Nothing runs until you ask. These presets are read-only, small and already used by the product.
{
"message": "A bounded response will appear here."
}Endpoint catalog
Thirteen useful starting points, grouped by the answer they return.
Live traffic, service health and provider capacity.
GET /traffic/latestlatest sample; use preferUsable=trueGET /traffic/summarytraffic, incidents and analytics togetherGET /system/operational-statuscomponent state, reason and next actionGET /system/provider-statusTomTom guard and account capacityBounded history, trends and comparison patterns.
GET /traffic/historycorridor samples with optional incidentsGET /traffic/analytics/trendstime-bucketed corridor historyGET /traffic/zones/trendshistory for each configured speed zoneGET /traffic/zones/baselinesweekly refreshed 13-week profilesRoad geometry, durable events and mapped flow cells.
GET /traffic/map/corridorstracked geometry and mile-marker calibrationGET /traffic/map/incidents/recentrecent events inside corridor boundsGET /traffic/map/flow-cells/currentcurrent combined-direction half-mile cellsGET /traffic/map/variable-speed-limits/currentcurrent I-70 sign limits, direction and source/read timesGET /traffic/map/flow-cells/frequencylong-range slowdown frequencyExample request
/dashboard-api/traffic/history?corridor=I70&windowMinutes=120&limit=12&includeIncidents=falsesamples[].polledAtsamples[].avgCurrentSpeedreturnedUp to 12 samples—not necessarily the full window. Incidents omitted.
Access model
Choose the prefix for the caller. The route suffix and response meaning stay the same.
Available when public dashboard data is enabled, with the configured per-minute ceiling applied.
Requires a valid key when API security is enabled for the deployment.
Both prefixes read current and archive-inclusive data. Neither one starts a provider request or changes stored state.
Response contract
Clients can distinguish an empty answer, a bad request and a busy public route.
JSON response or a successful empty collection.
Some single-resource reads have nothing to return yet.
Unsupported corridor, timestamp, window or limit.
Per-minute public limit exceeded; honor Retry-After.
Built-in guardrails