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

    Salt Lake County, UT
    parcel REST API.

    Public ArcGIS FeatureServer endpoint for Salt Lake County parcel data. URL, supported fields, and a working sample query — copy it, or open it directly in the UrbanKit parcel lookup tool.

    FeatureServer · LAYER 0 · PARCELS_SALTLAKE_LIR
    https://services1.arcgis.com/99lidPhWCzftIe9K/ArcGIS/rest/services/Parcels_SaltLake_LIR/FeatureServer/0
    License
    Public records (terms)
    Last verified
    2026-05-15
    Status
    Live
    — Sample query
    https://services1.arcgis.com/99lidPhWCzftIe9K/ArcGIS/rest/services/Parcels_SaltLake_LIR/FeatureServer/0/query?where=PARCEL_CITY='SALT+LAKE+CITY'&outFields=PARCEL_ID,PARCEL_ADD,PARCEL_CITY,TOTAL_MKT_VALUE,PROP_CLASS,BLDG_SQFT,BUILT_YR&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_SaltLake_LIR
    Field nameLabelSearchable
    PARCEL_IDParcel ID (Serial Number) YES
    SERIAL_NUMSerial Number YES
    PARCEL_ADDParcel Address YES
    PARCEL_CITYParcel City YES
    TOTAL_MKT_VALUETotal Market Value NO
    LAND_MKT_VALUELand Market Value NO
    PARCEL_ACRESParcel Acreage NO
    PROP_CLASSProperty Class NO
    SUBDIV_NAMESubdivision Name NO
    BLDG_SQFTBuilding Square Footage NO
    BUILT_YRYear Built NO
    TAX_DISTRICTTax District NO
    — Notes

    30 fields confirmed including PARCEL_ID, COUNTY_NAME, COUNTY_ID, ASSESSOR_SRC, BOUNDARY_SRC, CURRENT_ASOF, PARCEL_ADD, PARCEL_CITY, TAXEXEMPT_TYPE, TAX_DISTRICT, TOTAL_MKT_VALUE, LAND_MKT_VALUE, PARCEL_ACRES, PROP_CLASS, PRIMARY_RES, HOUSE_CNT, SUBDIV_NAME, BLDG_SQFT, FLOORS_CNT, BUILT_YR, EFFBUILT_YR, CONST_MATERIAL, PROP_TYPE. Query confirmed: returns real Salt Lake City addresses with market values. NOTE: Owner name is NOT included in this public LIR (Land Information Record) layer — owner data is available through the Salt Lake County Assessor's Parcel Viewer at apps.saltlakecounty.gov/assessor/new/ParcelViewer/. PARCEL_ID is the 14-digit serial number. This dataset is maintained by UGRC (Utah Geospatial Resource Center) in coordination with the Salt Lake County Assessor; data is updated monthly. A basic geometry-only version (Parcels_SaltLake) also exists on the same service with 17 fields and no value data.

    — Source

    Utah Geospatial Resource Center (UGRC) / Salt Lake County Assessor — https://gis.utah.gov/data/cadastre/parcels/

    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