Public ArcGIS MapServer endpoint for Wake County parcel data. URL, supported fields, and a working sample query — copy it, or open it directly in the UrbanKit parcel lookup tool.
https://maps.wake.gov/arcgis/rest/services/Property/Parcels/MapServer/0/query?where=UPPER(OWNER)+LIKE+UPPER('%SMITH%')&outFields=PIN_NUM,REID,OWNER,SITE_ADDRESS&returnGeometry=false&f=json&resultRecordCount=10Open this URL in a browser tab to see the raw ArcGIS JSON response.
| Field name | Label | Searchable |
|---|---|---|
| PIN_NUM | Parcel Identification Number | YES |
| REID | Real Estate ID | YES |
| OWNER | Owner Name | YES |
| SITE_ADDRESS | Site Address | YES |
| ADDR1 | Owner Mailing Address 1 | NO |
| ADDR2 | Owner Mailing Address 2 | NO |
| ADDR3 | Owner Mailing Address 3 | NO |
| TOWNSHIP | Township Code | NO |
| TOWNSHIP_DECODE | Township Name | NO |
| OLD_PARCEL_NUMBER | Legacy Parcel Number | YES |
435,382 polygon parcels covering Raleigh, Cary, Apex, Wake Forest, and the rest of Wake County. Verified 2026-05-11: UPPER(OWNER) LIKE '%SMITH%' returns real owners with full Raleigh-area site addresses (e.g., '600 HILLFARM DR'). Wake uses a 10-digit PIN_NUM keyed to the State Plane grid and a separate REID for Real Estate ID lookups against the assessor system. The MapServer endpoint also exposes a non-spatial OLD_PARCEL_NUMBER for legacy reconciliation.
Wake County GIS Services (Department of Information Services) — https://maps.wake.gov/
/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.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?
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.
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.
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.