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

    Dallas County, TX
    parcel REST API.

    Public ArcGIS FeatureServer endpoint for Dallas 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 · TAXPARCELS
    https://services2.arcgis.com/rwnOSbfKSwyTBcwN/arcgis/rest/services/DallasTaxParcels/FeatureServer/0
    License
    Public records (terms)
    Last verified
    2026-05-14
    Status
    Live
    — Sample query
    https://services2.arcgis.com/rwnOSbfKSwyTBcwN/arcgis/rest/services/DallasTaxParcels/FeatureServer/0/query?where=UPPER(TAXPANAME1) LIKE UPPER('%SMITH%')&outFields=ACCT,TAXPANAME1,ST_NUM,ST_NAME,CITY,COUNTY,APPRAISALYEAR&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 TaxParcels
    Field nameLabelSearchable
    ACCTDCAD Account Number (17-digit) YES
    GIS_ACCTGIS Account Number YES
    TAXPANAME1Taxpayer / Owner Name (Primary) YES
    TAXPANAME2Taxpayer / Owner Name 2 YES
    ST_NUMStreet Number YES
    ST_NAMEStreet Name YES
    ST_TYPEStreet Type NO
    CITYCity NO
    COUNTYCounty Label NO
    TAXPAADD1Taxpayer Mailing Address 1 YES
    TAXPACITYTaxpayer Mailing City NO
    PROP_CLProperty Class NO
    APPRAISALYEARAppraisal Year NO
    BUSNAMEBusiness Name YES
    — Notes

    41 fields confirmed including ACCT (17-digit DCAD account number), TAXPANAME1/2 (taxpayer names), TAXPAADD1-4, TAXPACITY, TAXPASTA, TAXPAZIP, ST_NUM, ST_NAME, ST_TYPE, ST_DIR, CITY, COUNTY, SCHOOL, SPTBCODE (special purpose district), PROP_CL, BLDG_CL, LEGAL_1-5, MAPSCO_GR, TOTEXEMPT, BUSNAME, PROPNAM, ResCom, APPRAISALYEAR. Owner search uses TAXPANAME1 (the taxpayer of record). APPRAISALYEAR in live records reads 2019 — this is the snapshot vintage of the City of Dallas GIS's DallasTaxParcels layer, which sources from DCAD annual export. The authoritative real-time DCAD parcel lookup is at dcad.org; the gis.dallascounty.org REST server does NOT expose a public parcel service (only SampleWorldCities and CommissionerDistricts). This layer covers all of Dallas County, not just the City of Dallas city limits — CITY field contains the incorporated municipality (Dallas, Rowlett, Garland, Irving, etc.). The COUNTY field confirms 'DALLAS COUNTY' for all records. The Texas SB247 privacy flag may suppress some owner names in a future data refresh; query TAXPANAME2 as fallback. maxRecordCount=1000.

    — Source

    City of Dallas GIS / Dallas Central Appraisal District (DCAD) — https://www.dallascad.org/

    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