UrbanKit Studio — Free GIS & Mailing Tools for Planners

    URBANKIT/STUDIO
    FREE · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE · BROWSER-ONLY · NO TELEMETRY · OPEN SOURCE
    ATLAS · COUNTY·AZ·FIPS 04013

    Maricopa County, AZ
    parcel REST API.

    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.

    MapServer · LAYER 3 · PARCELS
    https://gis.mcassessor.maricopa.gov/arcgis/rest/services/MaricopaDynamicQueryService/MapServer/3
    License
    Public records (terms)
    Last verified
    2026-05-11
    Status
    Live
    — Sample query
    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=10

    Open this URL in a browser tab to see the raw ArcGIS JSON response.

    — Searchable fields
    Searchable fields for Parcels
    Field nameLabelSearchable
    APNAssessor Parcel Number (APN) YES
    APN_DASHAPN with dashes YES
    OWNER_NAMEOwner Name YES
    MAIL_ADDR1Mailing Address 1 YES
    MAIL_ADDR2Mailing Address 2 YES
    MAIL_CITYMailing City NO
    MAIL_STATEMailing State NO
    PHYSICAL_ADDRESSPhysical Address (combined) YES
    PHYSICAL_CITYPhysical City NO
    SALE_DATESale Date NO
    SALE_PRICESale Price NO
    FCV_CURFull Cash Value (current year) NO
    LPV_CURLimited Property Value (current) NO
    — Notes

    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').

    — Source

    Maricopa County Assessor's Office — GIS Division — https://maps.mcassessor.maricopa.gov/

    How to use this REST endpoint

    Two paths from URL to result

    1. Open in Parcel Lookup — click the button on the endpoint card. The lookup tool loads the layer, auto-detects fields, and gives you a search box. No code, no API keys, just a browser.
    2. Query directly — append /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.

    Why field names vary by county

    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 this county actually publishes — not what you might expect from a national standard (there isn't one).

    For background, see What is an APN?

    What to do with the results

    • Generate a public-notice mailing list — pipe the parcel layer URL into Radius Notice to buffer around an address and select neighboring owners.
    • Print Avery 5160 labels — export the result CSV and drop it into CSV → Labels.
    • Pull individual parcel records — use Parcel Lookup directly to grab zoning, assessed value, and ownership for one property at a time.

    Quick FAQs

    This URL gives me a CORS error in my own app — what now?

    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.

    The endpoint loaded last week and now returns 404. Did the URL change?

    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.

    Are these endpoints free to query at scale?

    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.

    View all FAQs →

    — Continue