canonical: https://jentic.com/apis/az511.com/az511

# AZ511 Traffic Data API

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.

## For AI 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.

## Scope

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.

## Capabilities

- 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

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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 your Jentic One instance, so the agent never sees the raw key. Suited to commuter copilots and corporate travel briefings.

Example prompt: 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

| 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 |

## Key resources

- **Cameras** — Live traffic camera feeds across Arizona highways
- **Weather Stations** — Road-weather sensor readings used by ADOT
- **Message Signs** — Current text on dynamic message signs along highways
- **Events** — Active traffic incidents and events reported by ADOT
- **Alerts** — Statewide alerts including closures, construction, and advisories
- **Rest Areas** — Public rest areas with location and amenity metadata

## Why Jentic

- **Setup:** Wiring AZ511 by hand means adding the key to the key query parameter on every call to az511.com/api/v2 and building a polling loop with back-off for the modest ADOT call cadence. Through Jentic you install once, import the AZ511 Traffic Data API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Every AZ511 endpoint is a read-only GET (cameras, weather stations, message signs, events, alerts, rest areas) with no resource id in the path, so scoping is by operation. You limit the agent to the operations it needs, such as GET /get/alerts or GET /get/cameras, and the feed carries no write operations that could change ADOT data.
- **Credential handling:** Your AZ511 API key is stored once, encrypted, by your own Jentic One instance and injected into the key query parameter at call time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'arizona traffic alerts' or 'list arizona rest areas', and Jentic returns the matching AZ511 operation with its input schema so the agent calls the right endpoint without reading the ADOT docs.

## Related APIs

- **Arizona 511 API** — Same Arizona DOT 511 feed published under the .gov domain with a slightly different path layout.
- **New York 511 API** — Equivalent state 511 traffic feed for New York instead of Arizona.
- **HERE Maps API** — HERE Maps provides routing and base maps that overlay well with state 511 traffic feeds.

## FAQ

### 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 with Jentic One, the self-hosted execution layer.

### 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.

### Can I limit what my agent is allowed to do with the AZ511 Traffic Data API?

Yes. Because you run Jentic One yourself, your own rules decide which AZ511 operations and credentials the agent may use. Every AZ511 endpoint is a read-only GET with no resource id in the path, so you scope access by operation, allowing only the calls the agent needs, such as GET /get/alerts or GET /get/cameras while withholding GET /get/weatherstations, GET /get/messagesigns, GET /get/event, and GET /get/restareas. The feed carries no write operations, so a scoped agent can read Arizona traffic data without any way to change ADOT records.