URBANKIT/STUDIO
    Sign inFREE TOOLS · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE · BROWSER-ONLY · NO TELEMETRY
    ATLAS · COUNTY·CO·FIPS 08031·services1.arcgis.com

    Denver County, CO
    parcel GIS REST API.

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

    Look up a parcel

    This page is the endpoint reference. If you came here to find a specific property, the Denver County parcel search runs this same layer in your browser, no account and no API key.

    Search Denver County parcels →
    Primary ArcGIS REST endpoint
    https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_PROP_PARCELS_A/FeatureServer/245

    What these endpoints answer

    Field by field, whether any endpoint we index for Denver County answers it, and the evidence for each. We only call a field restricted when there is a stated reason we can cite. Everything else here is a fact about the services we index, not a claim about the law.

    Which parcel fields Denver County’s endpoint answers, and the evidence for each
    FieldStatusBasis
    APN AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Owner name AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Owner mailing address AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Site address AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Geometry AnsweredDocumented in a field list on an endpoint we index. Not every row is populated.
    Land use Not publishedNo endpoint we index for this county documents this field, so a query cannot ask for it. That is a fact about the services we index, not a legal restriction, and not a statement that the county holds no such record. Where to request it.
    Zoning Not publishedNo endpoint we index for this county documents this field, so a query cannot ask for it. That is a fact about the services we index, not a legal restriction, and not a statement that the county holds no such record. Where to request it.
    FeatureServer · LAYER 245 · PROP_PARCELS_A
    https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_PROP_PARCELS_A/FeatureServer/245

    Searchable fields

    • SCHEDNUMSchedule Number (13-digit parcel ID)
    • SITUS_ADDRESS_LINE1Situs Address
    • OWNER_NAMEOwner Name
    • OWNER_ADDRESS_LINE1Owner Mailing Address
    • SITUS_CITYSitus City
    • SITUS_ZIPSitus ZIP

    Sample query (paste into terminal or browser)

    curl -s 'https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_PROP_PARCELS_A/FeatureServer/245/query?where=UPPER(OWNER_NAME)+LIKE+UPPER('%25SMITH%25')&outFields=SCHEDNUM,OWNER_NAME,SITUS_ADDRESS_LINE1,SITUS_CITY,SITUS_ZIP&returnGeometry=false&f=json&resultRecordCount=10'
    License
    Public records (terms)
    Listed on
    2026-08-24
    Registry listing
    Listed live
    Sample query
    https://services1.arcgis.com/zdB7qR0BtYrg0Xpl/arcgis/rest/services/ODC_PROP_PARCELS_A/FeatureServer/245/query?where=UPPER(OWNER_NAME)+LIKE+UPPER('%SMITH%')&outFields=SCHEDNUM,OWNER_NAME,SITUS_ADDRESS_LINE1,SITUS_CITY,SITUS_ZIP&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 PROP_PARCELS_A
    Field nameLabelSearchable
    SCHEDNUMSchedule Number (13-digit parcel ID) YES
    SITUS_ADDRESS_LINE1Situs Address YES
    OWNER_NAMEOwner Name YES
    OWNER_ADDRESS_LINE1Owner Mailing Address YES
    SITUS_CITYSitus City YES
    SITUS_ZIPSitus ZIP YES
    Notes

    34 fields confirmed including parcel_id, countyName, countyFips, situsAdd, sitAddCty, sitAddZip, owner, owner2, ownerAdd, ownAddCty, ownAddStt, ownAddZip, legalDesc, landSqft, landAcres, block, lot, subCode, subName, zoningCode, zoningDesc, landUseCde, landUseDsc, saleDate, salePrice, apprValTot, asedValTot, URL, dateReceived. This is a statewide composite. Query by countyName='Denver' OR countyFips='031' (note: FIPS here is the 3-digit county portion, not the full 5-digit). Owner query tested and confirmed with real Denver addresses. This same endpoint covers all 64 Colorado counties; filter by countyName or countyFips for any of them. Denver is a consolidated city-county (countyName='Denver' and cityName='Denver' are the same entity).

    Source

    Colorado Governor's Office of Information Technology (OIT), Colorado Geographic Information Systems Program, https://gis.colorado.gov/

    Using this endpoint

    What Denver County publishes

    Denver County's PROP_PARCELS_A layer exposes a parcel identifier (Schedule Number (13-digit parcel ID)), owner names (Owner Name, Owner Mailing Address), and address fields (Situs Address, Situs City, Situs ZIP). Use it for owner-name lookups and address-based parcel searches. All 6 listed fields accept queries. Served as an ArcGIS FeatureServer layer, so edits and applyEdits operations are technically exposed (read access only is published here); last verified 2026-08-24.

    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 Denver 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

    Can I query Denver County's parcel layer from my own web app?

    services1.arcgis.com serves Denver County, Colorado parcels over public ArcGIS REST, but, like most county servers, it may not send the CORS headers a browser needs for a cross-origin fetch. If a direct browser call fails, the layer still works from curl, Postman, or a server-side script; the UrbanKit parcel lookup tool proxies the request, so a search that succeeds there confirms the layer is genuinely public.

    Is the Denver County endpoint still current?

    We last verified Denver County's FeatureServer layer on 2026-08-24. County GIS teams move services without notice, so if you hit a fresh 404, tell us and we'll re-check. Atlas entries are re-verified on a rolling basis.

    Is there a rate limit on Denver County parcel queries?

    Denver County's layer is hosted on Esri ArcGIS Online. Public ArcGIS endpoints rarely rate-limit individual reads, but services1.arcgis.com can throttle heavy automated traffic at the host level. Page through results with resultOffset / resultRecordCount and request only the fields you need. There's no API key and no charge from the county.

    View all FAQs →

    Continue