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

    Pima County, AZ
    parcel REST API.

    Public ArcGIS MapServer endpoint for Pima 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 17 · PAREGION
    https://mapdata.tucsonaz.gov/public/rest/services/PublicMaps/PropertyHousing/MapServer/17
    License
    Public records (terms)
    Last verified
    2026-05-14
    Status
    Live
    — Sample query
    https://mapdata.tucsonaz.gov/public/rest/services/PublicMaps/PropertyHousing/MapServer/17/query?where=UPPER(ADDRESSEE) LIKE UPPER('%SMITH%')&outFields=PARCEL,ADDRESSEE,SITE_ADDRESS,SITE_ZIPCITY,TAXYR,FCV,USE_DESC&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 PAREGION
    Field nameLabelSearchable
    PARCELParcel Number (Pima County APN) YES
    ADDRESSEEOwner / Addressee Name YES
    SITE_ADDRESSSite Address YES
    SITE_ZIPCITYSite City NO
    TAXAREATax Area Code NO
    FCVFull Cash Value NO
    USE_DESCUse Description NO
    TAXYRTax Year NO
    YearBuiltYear Built NO
    MAIL1Mailing Address Line 1 YES
    MAIL2Mailing Address Line 2 YES
    legal_descLegal Description NO
    — Notes

    75 fields confirmed. The PAREGION layer (layer 17) is the county-wide Pima County Assessor parcel layer, hosted on the City of Tucson mapdata.tucsonaz.gov ArcGIS server, which aggregates both City of Tucson and unincorporated Pima County parcels. Layer 40 (PAREGION_TUCSON) is the Tucson-only subset; use layer 17 for full county coverage. Owner-name field is ADDRESSEE (holds the assessor's addressee/taxpayer name — equivalent to owner name for most records). PARCEL format is alphanumeric (e.g. '101013880'). Also exposes FCV (Full Cash Value), TAXYR, USE_DESC, MAIL1-5 (mailing address), LEGAL1-5 (legal description), SITE_ADDRESS, SITE_ZIPCITY, SITE_ZIP, TAXAREA, GISACRES, CURZONE_OL (zoning), and YearBuilt. The supportsQuery field reads null in layer metadata (ArcGIS 11.3 quirk), but the service capabilities string is 'Map,Query,Data' — queries work as confirmed by live testing. maxRecordCount=2000. The gisweb.pima.gov hostname NXDOMAINs; mapdata.tucsonaz.gov is the correct publicly accessible host.

    — Source

    City of Tucson / Pima County GIS — PropertyHousing MapServer (Pima Assessor PAREGION data) — https://www.pima.gov/1796/Geographic-Information-Systems

    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