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/0PIN_NUMParcel Identification NumberREIDReal Estate IDOWNEROwner NameSITE_ADDRESSSite AddressOLD_PARCEL_NUMBERLegacy Parcel Numbercurl -s 'https://maps.wake.gov/arcgis/rest/services/Property/Parcels/MapServer/0/query?where=UPPER(OWNER)+LIKE+UPPER(%27%25SMITH%25%27)&outFields=PIN_NUM,REID,OWNER,SITE_ADDRESS&returnGeometry=false&f=json&resultRecordCount=10'
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 |
Wake County (Raleigh metro, pop. 1.17 million) hosts 435,382 parcel polygons in its county-direct ArcGIS FeatureServer. Owner-name queries use UPPER(OWNER) LIKE '%SMITH%' and return real site addresses (verified 2026-05-11). Two identifiers matter: PIN_NUM is a 10-digit code derived from State Plane grid coordinates and uniquely locates the parcel geographically; REID (Real Estate ID) is the assessor's account key, used by the Wake County Register of Deeds and the iMAPS application for cross-reference. The layer also carries OLD_PARCEL_NUMBER for reconciling legacy records that predate current PIN_NUM assignment. Wake County GIS and Raleigh GIS jointly maintain iMAPS (maps.raleighnc.gov/iMAPS) as a parallel lookup tool supporting owner, address, PIN, and REID searches. NC OneMap aggregates Wake data quarterly as well; the county's own FeatureServer is more current for recent splits and consolidations.
Wake County GIS Services (Department of Information Services), https://maps.wake.gov/
Wake County's Property layer exposes parcel identifiers (Parcel Identification Number, Legacy Parcel Number), owner names (Owner Name), and address fields (Site Address). Use it for owner-name lookups and address-based parcel searches. 5 of 10 listed fields accept queries; the rest are returned on read but not indexed for search. Served as an ArcGIS MapServer layer, which supports query operations but not write operations; last verified 2026-05-11.
/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 Wake County actually publishes, not what you might expect from a national standard (there isn't one).
For background, see What is an APN?
maps.wake.gov serves Wake County, North Carolina 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.
We last verified Wake County's MapServer layer on 2026-05-11. 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.
Wake County's layer is hosted by the county on maps.wake.gov. Public ArcGIS endpoints rarely rate-limit individual reads, but maps.wake.gov 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.