Public ArcGIS FeatureServer endpoint for Fayette County parcel data. URL, supported fields, and a working sample query, copy it, or open it directly in the UrbanKit parcel lookup tool.
https://services.arcgis.com/f4rR7WnIfGBdVYFd/arcgis/rest/services/Tax_Parcels/FeatureServer/0PANParcel Account Number (Parcel ID)Owner1Owner Name 1curl -s 'https://services.arcgis.com/f4rR7WnIfGBdVYFd/arcgis/rest/services/Tax_Parcels/FeatureServer/0/query?where=UPPER(Owner1)+LIKE+UPPER('%25SMITH%25')&outFields=PAN,Owner1,Mailing_Address,PARCEL_TYPE&returnGeometry=false&f=json&resultRecordCount=10'https://services.arcgis.com/f4rR7WnIfGBdVYFd/arcgis/rest/services/Tax_Parcels/FeatureServer/0/query?where=UPPER(Owner1)+LIKE+UPPER('%SMITH%')&outFields=PAN,Owner1,Mailing_Address,PARCEL_TYPE&returnGeometry=false&f=json&resultRecordCount=10Open this URL in a browser tab to see the raw ArcGIS JSON response.
| Field name | Label | Searchable |
|---|---|---|
| PAN | Parcel Account Number (Parcel ID) | YES |
| Owner1 | Owner Name 1 | YES |
| Owner2 | Owner Name 2 | NO |
| Owner3 | Owner Name 3 | NO |
| Mailing_Address | Mailing Address | NO |
| PARCEL_SUB | Parcel Sub-Identifier | NO |
| PARCEL_BLOCK | Block | NO |
| PARCEL_LOT | Lot | NO |
| PARCEL_TYPE | Parcel Type | NO |
| RecordDate | Record Date | NO |
Fayette County (Lexington, pop. 322,000; consolidated city-county) Tax Parcels FeatureServer hosted on ArcGIS Online (LFUCG org). Fayette County is a merged urban county government, the Lexington-Fayette Urban County Government (LFUCG). Fields confirmed: PAN (numeric parcel account number), PARCEL_SUB, PARCEL_BLOCK, PARCEL_LOT, LRM_GEOM_DOC, RecordDate, LRM_GEOM_DOC_AREA/UNITS, PARCEL_TYPE, PARCEL_POLY_NAME, Owner1/2/3, Mailing_Address. Note: PARCEL_POLY_NAME may be null; PAN is the numeric parcel identifier. Mailing_Address is a single concatenated field. Verified 2026-05-15: Owner1 SMITH returns Lexington-area addresses (e.g., '3875 GEIST RD STE E469', '4951 E JOHN JOHN CT'). A separate Parcels FeatureServer exists at the same org but has no owner fields, Tax_Parcels is the correct service. Note: distinct from Jefferson County KY (Louisville, FIPS 21111) already in atlas.
Lexington-Fayette Urban County Government (LFUCG) GIS, https://data-lfucg.hub.arcgis.com/
Fayette County's Tax_Parcels layer exposes a parcel identifier (Parcel Account Number (Parcel ID)) and owner names (Owner Name 1). Use it for owner-name lookups and PIN-keyed record pulls. 2 of 10 listed fields accept queries; the rest are returned on read but not indexed for search. Served as an ArcGIS FeatureServer layer, so edits and applyEdits operations are technically exposed (read access only is published here); last verified 2026-05-15.
/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 Fayette County actually publishes, not what you might expect from a national standard (there isn't one).
For background, see What is an APN?
services.arcgis.com serves Fayette County, Kentucky 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 Fayette County's FeatureServer layer on 2026-05-15. 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.
Fayette County's layer is hosted on Esri ArcGIS Online. Public ArcGIS endpoints rarely rate-limit individual reads, but services.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.