Public ArcGIS MapServer endpoint for Maricopa County parcel data. URL, supported fields, and a working sample query — copy it, or open it directly in the UrbanKit parcel lookup tool.
https://gis.mcassessor.maricopa.gov/arcgis/rest/services/MaricopaDynamicQueryService/MapServer/3APNAssessor Parcel Number (APN)APN_DASHAPN with dashesOWNER_NAMEOwner NameMAIL_ADDR1Mailing Address 1MAIL_ADDR2Mailing Address 2PHYSICAL_ADDRESSPhysical Address (combined)curl -s 'https://gis.mcassessor.maricopa.gov/arcgis/rest/services/MaricopaDynamicQueryService/MapServer/3/query?where=UPPER(OWNER_NAME)%20LIKE%20UPPER('%25SMITH%25')&outFields=APN,OWNER_NAME,PHYSICAL_ADDRESS,PHYSICAL_CITY&returnGeometry=false&f=json&resultRecordCount=10'https://gis.mcassessor.maricopa.gov/arcgis/rest/services/MaricopaDynamicQueryService/MapServer/3/query?where=UPPER(OWNER_NAME) LIKE UPPER('%SMITH%')&outFields=APN,OWNER_NAME,PHYSICAL_ADDRESS,PHYSICAL_CITY&returnGeometry=false&f=json&resultRecordCount=10Open this URL in a browser tab to see the raw ArcGIS JSON response.
| Field name | Label | Searchable |
|---|---|---|
| APN | Assessor Parcel Number (APN) | YES |
| APN_DASH | APN with dashes | YES |
| OWNER_NAME | Owner Name | YES |
| MAIL_ADDR1 | Mailing Address 1 | YES |
| MAIL_ADDR2 | Mailing Address 2 | YES |
| MAIL_CITY | Mailing City | NO |
| MAIL_STATE | Mailing State | NO |
| PHYSICAL_ADDRESS | Physical Address (combined) | YES |
| PHYSICAL_CITY | Physical City | NO |
| SALE_DATE | Sale Date | NO |
| SALE_PRICE | Sale Price | NO |
| FCV_CUR | Full Cash Value (current year) | NO |
| LPV_CUR | Limited Property Value (current) | NO |
57 fields confirmed including APN, APN_DASH, BOOK, MAP, ITEM, FLOOR, OWNER_NAME, MAIL_ADDR1/2, MAIL_CITY, MAIL_STATE, MAIL_ZIP, MAIL_CNTRY, PHYSICAL_ADDRESS, PHYSICAL_CITY, PHYSICAL_ZIP, PHYSICAL_STREET_NUM/DIR/NAME/TYPE, DEED_NUMBER, DEED_DATE, SALE_DATE, SALE_PRICE, MCRNUM, SUBNAME, LAND_SIZE, LOT_NUM, CONST_YEAR, LIVING_SPACE, INCAREOF, FCV_CUR/PREV, LPV_CUR/PREV, TAX_YR_CUR/PREV, CITY_ZONING, JURISDICTION, BLOCK, TRACT. Owner query tested and confirmed. The MaricopaDynamicQueryService layer 3 (Parcels) is the full-attribute layer backing the Parcel Viewer at maps.mcassessor.maricopa.gov. A separate 'Parcels' MapServer at gis.mcassessor.maricopa.gov/arcgis/rest/services/Parcels/MapServer also exists but has fewer fields. APN format: 8-digit with no dashes (e.g. '10101347'); APN_DASH adds dashes (e.g. '101-01-347').
Maricopa County Assessor's Office — GIS Division — https://maps.mcassessor.maricopa.gov/
Maricopa County's Parcels layer exposes parcel identifiers (Assessor Parcel Number (APN), APN with dashes), owner names (Owner Name), and address fields (Mailing Address 1, Mailing Address 2, Physical Address (combined)). Use it for owner-name lookups and address-based parcel searches. 6 of 13 listed fields accept queries; the rest are returned on read but not indexed for search. Served as an ArcGIS MapServer layer, which supports query operations but not write operations; last verified 2026-05-11.
/query?where=…&outFields=*&f=jsonto the URL. The sample query above is a working example you can paste into a browser tab to see the raw JSON response.Counties publish parcel data through their own ArcGIS Server installations, each with its own schema. One county uses APN, another uses PIN, a third uses PARCEL_ID. Some expose owner names; others keep them on a separate assessor's portal. The searchable fields list above reflects what Maricopa County actually publishes — not what you might expect from a national standard (there isn't one).
For background, see What is an APN?
Many county servers allow public reads but block browser cross-origin requests. The UrbanKit parcel lookup tool fetches directly from your browser; if it works there, the layer is technically public. For your own integration, you may need a same-origin proxy or server-side fetch.
Possibly — counties move services without warning. We re-verify entries weekly and flag stale ones. If you're seeing a fresh 404, please let us know and we'll update the listing.
Most are. Public ArcGIS layers don't typically rate-limit individual reads, but heavy programmatic use can trigger throttling at the host level. Be respectful — query what you need.