3 counties indexed. ArcGIS FeatureServer and MapServer URLs, with supported search fields per layer.
| County | Endpoints | Searchable fields | Status | Action |
|---|---|---|---|---|
| Maricopa County | 1 | Assessor Parcel Number (APN) · APN with dashes · Owner Name +3 | LIVE | OPEN |
| Pima County | 1 | Parcel Number (Pima County APN) · Owner / Addressee Name · Site Address +2 | LIVE | OPEN |
| Pinal County | 1 | Parcel ID (APN) · Lower Parcel ID · Owner Name (Primary) +2 | LIVE | OPEN |
Arizona county parcel data is administered by county assessors operating independently under the Arizona Department of Revenue. There is no statewide cadastral aggregation layer analogous to Colorado's OIT composite or New York's ITS service. Each county publishes on its own infrastructure at its own cadence. The state's 15 counties vary sharply in population: Maricopa alone holds more than 60 percent of Arizona's residents, which concentrates most programmatic parcel demand in a single county with a well-maintained GIS program.
The Arizona State Land Department (ASLD) maintains GIS data for state trust lands and some boundary layers, but it does not aggregate county assessor parcel data. The Arizona Association of Counties facilitates data-sharing discussions but has not produced a unified parcel API. In practice, county assessor offices run their own ArcGIS Server instances or publish through ArcGIS Online. Maricopa County Assessor's Office operates the most capable public REST service, backed by the MaricopaDynamicQueryService MapServer. Pima County routes its parcel layer through the City of Tucson's ArcGIS server (mapdata.tucsonaz.gov), a hosting arrangement that catches researchers off guard when they expect the layer at a pima.gov hostname. Pinal County hosts through the City of Casa Grande's ArcGIS Server (rogue.casagrandeaz.gov), another third-party arrangement; the gismaps.pinalcountyaz.gov hostname is not publicly accessible.
Maricopa County uses an 8-digit APN (e.g., '10101347') stored in the APN field, with a dash-formatted variant in APN_DASH (e.g., '101-01-347'). Pima County uses an alphanumeric PARCEL field (e.g., '101013880'). Pinal County calls the identifier PARCELID, also alphanumeric and typically 9 digits. None of these formats are interchangeable across counties. Maricopa's APN_DASH field is useful when working from documents that display the dashed format, but the core APN field is what the REST query engine indexes.
Maricopa exposes OWNER_NAME directly. Pima exposes ADDRESSEE, which holds the assessor's taxpayer/addressee name — functionally equivalent to owner name for most records. Pinal exposes OWNERNME1 and OWNERNME2 (primary and secondary). For a LIKE query on owner across all three counties you need three different field names. Maricopa also includes INCAREOF for care-of names, which can matter when querying LLC or trust-held properties.
The Pima County PAREGION layer (layer 17 on mapdata.tucsonaz.gov) reports supportsQuery as null in its metadata response, which some clients interpret as query-disabled. The actual service capabilities string reads 'Map,Query,Data' and queries work fine as confirmed by live testing. This is an ArcGIS Server 11.3 metadata serialization issue. If a client library reads the null and refuses to query, override it by appending the query endpoint directly.
Phoenix metro (~4.5M residents, FIPS 04013). Arizona's dominant county by population. Exposes OWNER_NAME, APN, APN_DASH, PHYSICAL_ADDRESS, sale dates, and appraised values (FCV_CUR/LPV_CUR) on the MaricopaDynamicQueryService layer 3. Owner queries confirmed live.
Tucson metro (FIPS 04019). Layer hosted on the City of Tucson's server, not on a pima.gov hostname. Owner field is ADDRESSEE. PARCEL is the APN-equivalent. Layer 17 covers the full county; layer 40 covers Tucson city limits only. 75 fields including FCV, zoning (CURZONE_OL), and legal description.
Phoenix south exurbs — Casa Grande, Queen Creek, Maricopa City (FIPS 04021). Layer hosted on the City of Casa Grande's ArcGIS Server. Owner fields are OWNERNME1 and OWNERNME2. PARCELID is the identifier. 74 fields confirmed; the gismaps.pinalcountyaz.gov hostname does not resolve publicly.
Maricopa owner search: ?where=UPPER(OWNER_NAME) LIKE UPPER('%25SMITH%25')&outFields=APN,APN_DASH,OWNER_NAME,PHYSICAL_ADDRESS,PHYSICAL_CITY,FCV_CUR&returnGeometry=false&f=json. Pima owner search using ADDRESSEE: ?where=UPPER(ADDRESSEE) LIKE UPPER('%25SMITH%25')&outFields=PARCEL,ADDRESSEE,SITE_ADDRESS,SITE_ZIPCITY,FCV,USE_DESC&returnGeometry=false&f=json. Pinal parcel lookup: ?where=PARCELID LIKE '%25302%25'&outFields=PARCELID,SITEADDRESS,OWNERNME1,CLASSCD,CLASSDSCRP&returnGeometry=false&f=json.
Last updated 2026-05-24.
3 Arizona counties are indexed in the UrbanKit atlas with verified public REST endpoints: Maricopa, Pima, and Pinal. Each exposes an owner-name field you can search directly on the public layer.
Maricopa, Pima, and Pinal expose an owner-name field on the public REST layer. Maricopa, for example, uses the OWNER_NAME field — a case-insensitive search is ?where=UPPER(OWNER_NAME)%20LIKE%20UPPER('%25SMITH%25')&outFields=*&f=json. Open a county's page here for its full field list and a ready-to-run sample query.
Maricopa publishes parcels at https://gis.mcassessor.maricopa.gov/arcgis/rest/services/MaricopaDynamicQueryService/MapServer/3 — a MapServer (layer 3). It indexes by Assessor Parcel Number (APN), APN with dashes, Owner Name, and Mailing Address 1. Owner-name search: UPPER(OWNER_NAME) LIKE UPPER('%25SMITH%25').
Arizona's indexed counties (Maricopa, Pima, and Pinal) publish county-hosted ArcGIS MapServer layers. MapServer supports the same /query operation for owner, parcel-ID, and address lookups as FeatureServer — for read-only parcel lookups the two are interchangeable.
Listing missing or moved? Tell us — we verify and update weekly.