AZ511 Traffic Data API
★ Only Publicly Available OpenAPI DocumentMaps GeolocationPlaces SearchapiKey6 EndpointsREST
For Agents
Pull live Arizona traffic data — cameras, weather, message signs, events, alerts, and rest areas — from the ADOT 511 feed. Suited to agents that surface road conditions to travellers and logistics planners.
Use for: Get all current Arizona traffic cameras, Show me active road closures on Arizona highways, Retrieve weather station readings along I-17, List rest areas on the route from Phoenix to Flagstaff
Not supported: Does not handle routing, navigation, or incident reporting back to ADOT — use AZ511 for read-only Arizona traffic, weather-station, message-sign, event, alert, and rest-area data only.
Jentic publishes the only available OpenAPI specification for AZ511 Traffic Data API, keeping it validated and agent-ready. The AZ511 API gives developers programmatic access to Arizona Department of Transportation (ADOT) traffic feeds, including live traffic cameras, weather stations, dynamic message signs, traffic events, alerts, and rest areas across the Arizona highway network. All six endpoints are GET-only and require an API key passed as a `key` query parameter.
Install Jentic One Beta
Connect the AZ511 Traffic Data API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AZ511 Traffic Data API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with AZ511 Traffic Data API.
Retrieve all live traffic cameras across the Arizona highway network
Pull weather station readings for road-weather conditions
List active dynamic message sign messages on Arizona highways
Get current traffic events and incidents reported by ADOT
Fetch traffic alerts (closures, construction, advisories) statewide
List rest areas with metadata for trip-planning workflows
Use Cases
Patterns agents use AZ511 Traffic Data API for, with concrete tasks.
★ Live Road-Conditions Dashboard
Logistics dispatchers and travel apps can build a live Arizona road-conditions dashboard by polling /get/event for incidents, /get/alerts for closures, and /get/cameras for visual confirmation. Combined with /get/weatherstations, the dashboard can show whether weather is contributing to a slowdown. Suited to fleet operations centres and traveller-information apps.
Poll GET /get/event and GET /get/alerts every 5 minutes and surface any new incidents on highways crossing the Phoenix metro area
Trip Planning with Rest Areas and Weather
Traveller-information apps can call /get/restareas to plot rest stops along a planned route and /get/weatherstations to overlay temperature, visibility, and pavement conditions. Useful for long-haul drivers, RV travellers, and tourism apps providing pre-trip checks.
Fetch GET /get/restareas and GET /get/weatherstations and produce a list of rest stops with the latest temperature reading along the planned route
Construction and Closure Alerting
Commuters and freight operators can subscribe to construction and closure information by polling /get/alerts and the message-signs feed at /get/messagesigns. The data is sourced directly from ADOT operations centres. Suited to alerting tools that route alternates around major closures.
Call GET /get/alerts and filter for closures longer than 1 hour, then push them into the team's logistics Slack channel
Agent-Driven Travel Briefings via Jentic
A travel-assistant agent can produce a morning Arizona road briefing by chaining the cameras, alerts, weather, and events endpoints through Jentic. The API key is held in the Jentic vault, so the agent never sees the raw key. Suited to commuter copilots and corporate travel briefings.
Search Jentic for 'arizona traffic alerts', load GET /get/alerts, and execute it as part of a morning briefing summarising statewide road conditions
Key Endpoints
6 endpoints — jentic publishes the only available openapi specification for az511 traffic data api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/get/cameras
Get all traffic cameras
GET
/get/weatherstations
Get all weather stations
GET
/get/messagesigns
Get all dynamic message signs
GET
/get/event
Get all traffic events
GET
/get/alerts
Get all traffic alerts
GET
/get/restareas
Get all rest areas
GET
/get/cameras
Get all traffic cameras
GET
/get/weatherstations
Get all weather stations
GET
/get/messagesigns
Get all dynamic message signs
GET
/get/event
Get all traffic events
GET
/get/alerts
Get all traffic alerts
GET
/get/restareas
Get all rest areas
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The AZ511 API key is stored encrypted in the Jentic vault and injected into the `key` query parameter on every request. The raw key never appears in the agent's context.
Intent-based discovery
Agents search Jentic by intent (e.g. 'arizona traffic alerts' or 'list rest areas') and Jentic returns the matching AZ511 operations with their input schemas attached.
Time to first call
Direct AZ511 integration: a few hours to wire key handling and a polling loop. Through Jentic: minutes to call /get/event, /get/alerts, or /get/cameras with no key handling code.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using AZ511 Traffic Data API through Jentic.
Why is there no official OpenAPI spec for AZ511 Traffic Data API?
ADOT does not publish an OpenAPI specification for the AZ511 feed. Jentic generates and maintains this spec so that AI agents and developers can call AZ511 Traffic Data API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the AZ511 Traffic Data API use?
AZ511 v2 uses an API key passed in the `key` query parameter. Through Jentic, the key is stored encrypted in the vault and added to the query string at call time so it never reaches the agent context.
Can I get live Arizona traffic camera images with the AZ511 Traffic Data API?
Yes. GET /get/cameras returns the camera registry including image URLs hosted by ADOT. Pair with GET /get/event to correlate camera locations with current incidents.
How do I get current traffic alerts through Jentic?
Search Jentic for 'arizona traffic alerts', load GET /get/alerts, and execute it. Jentic injects the AZ511 key from the vault and returns the active alerts.
What are the rate limits for the AZ511 Traffic Data API?
The v2 spec does not declare numeric rate limits, but the related ADOT 511 feeds are typically capped at around 10 calls per minute. Treat the endpoints as polling-friendly with modest cadence and back off on 429 responses.
Is the AZ511 Traffic Data API free?
Access is provided by ADOT and is free for non-commercial public-information use; you must register for an API key on the AZ511 developer site. Confirm any commercial-use terms with ADOT directly.
GET STARTED