Azdeq APIazsdwis.azdeq.gov ↗
Access Arizona Safe Drinking Water Information System data: water systems, analytes, sample results, and CCR reports via 7 structured endpoints.
What is the Azdeq API?
The Arizona SDWIS API exposes public drinking water data from azsdwis.azdeq.gov across 7 endpoints, covering everything from statewide water system search to per-analyte historical sample results. The search_water_systems endpoint lets you query by name, county, system type, or source water type and returns system IDs needed to chain into detail, analyte, and sample-result calls.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/075111a7-0e3d-4140-82e1-efebeab264a1/list_filters' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace azsdwis-azdeq-gov-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Arizona Safe Drinking Water Information System — search, drill-down, sample results."""
from parse_apis.arizona_safe_drinking_water_information_system_api import (
ArizonaDrinkingWater,
County,
SystemType,
WaterSystemNotFound,
)
client = ArizonaDrinkingWater()
# Fetch available filters (counties, system types, source types)
filters = client.filters.get()
print(filters.counties, filters.water_system_types)
# Search for community water systems in Maricopa County
for ws in client.watersystems.search(county=County.MARICOPA, system_type=SystemType.COMMUNITY, limit=3):
print(ws.name, ws.pws_id, ws.tinwsys_is_number)
# Take one system and get its full detail (contacts, sources)
system = client.watersystems.search(county=County.PIMA, limit=1).first()
if system:
detail = system.detail()
print(detail.name, detail.primary_source, detail.status)
# List monitored analytes for this system
for analyte in system.analytes.list(limit=3):
print(analyte.name, analyte.code)
# Get historical sample results for this analyte
for sample in analyte.samples.list(tinwsys_is_number=system.tinwsys_is_number, limit=2):
print(sample.date, sample.detection_limit, sample.mcl)
# Check available Consumer Confidence Report years
for year in system.ccr_years.list(limit=5):
print(year.year)
# Typed error handling
try:
bad_system = client.watersystems.search(number="AZ9999999", limit=1).first()
if bad_system:
bad_system.detail()
except WaterSystemNotFound as exc:
print(f"System not found: {exc.tinwsys_is_number}")
print("exercised: filters.get / watersystems.search / detail / analytes.list / samples.list / ccr_years.list")
List available search filters for water systems including counties, system types, source water types, and point of contact types.
No input parameters required.
{
"type": "object",
"fields": {
"counties": "array of county name strings",
"source_water_types": "array of source water type display names",
"water_system_types": "array of water system type display names",
"point_of_contact_types": "array of contact type display names"
},
"sample": {
"data": {
"counties": [
"All",
"APACHE",
"COCHISE",
"COCONINO",
"GILA",
"GRAHAM",
"GREENLEE",
"LA PAZ",
"MARICOPA",
"MOHAVE",
"NAVAJO",
"PIMA",
"PINAL",
"SANTA CRUZ",
"YAVAPAI",
"YUMA"
],
"source_water_types": [
"All",
"GroundWater",
"GroundWater Purchased",
"GroundWater UDI SurfaceWater",
"GroundWater UDI SurfaceWater Purchased",
"SurfaceWater",
"SurfaceWater Purchased"
],
"water_system_types": [
"All",
"Community",
"Non-Community",
"Non-Transient Non-Community"
],
"point_of_contact_types": [
"None",
"Administrative Contact",
"Emergency Contact",
"Owner",
"Lead Engineer",
"Operator",
"Financial Contact",
"Legal Contact",
"Designated Op in Charge",
"Sampling"
]
},
"status": "success"
}
}About the Azdeq API
What the API Covers
This API surfaces data from Arizona's Safe Drinking Water Information System (SDWIS), maintained by the Arizona Department of Environmental Quality (ADEQ). It covers public water systems (PWS) statewide — community, non-community, and non-transient non-community systems — along with their monitored contaminants, lab sample results, and Consumer Confidence Report (CCR) availability. The list_filters endpoint returns all valid enumerated values for county, system type, source water type, and point-of-contact type, which are the accepted inputs throughout the rest of the API.
Searching and Identifying Water Systems
search_water_systems accepts up to five optional filters — name (partial match), number (e.g. AZ0407025), county, source_type, and system_type — and returns an array of matching systems with fields including pws_id, federal_type, status, county, source_type, tinwsys_is_number, and tinwsys_st_code. The tinwsys_is_number value is the internal ID required by get_water_system_detail, get_water_system_analytes, and get_water_system_sample_results, so a search call is typically the first step in any workflow.
Analytes and Sample Results
get_water_system_analytes returns every contaminant monitored for a given system, including code, name, and analyte_id. Passing an analyte_id plus tinwsys_is_number to get_water_system_sample_results returns the full sample history for that contaminant, with fields for sample_type, date, sample_point, result, uom (unit of measure), and a less_than flag for non-detect readings. get_available_ccr_years takes a pws_id and returns which Consumer Confidence Report years are on file for that system.
Known Limitation
The get_glossary endpoint is documented in the API but currently returns an error because the corresponding page has been removed from the ADEQ site. All other endpoints return structured data. Coverage is limited to Arizona public water systems; no data from other states is included.
The Azdeq API is a managed, monitored endpoint for azsdwis.azdeq.gov — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when azsdwis.azdeq.gov changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official azsdwis.azdeq.gov API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a lookup tool that maps Arizona county names to their public water systems and current operational status.
- Track historical contaminant levels for a specific water system by chaining analyte and sample-result endpoints.
- Generate alerts when sample results for a regulated analyte exceed a threshold value across multiple systems.
- Compile a list of available Consumer Confidence Report years for all Community water systems in a given county.
- Identify all water systems using a specific source water type (e.g. GroundWater) across Arizona counties.
- Audit contact records for water systems by pulling operator and emergency contact data from the detail endpoint.
- Cross-reference federal_type and status fields to identify inactive or non-community water systems statewide.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.