URBANKIT/STUDIO
    Sign inFREE TOOLS · NO SIGNUP
    URBANKIT/STUDIO · EST. 2026 · ONLINEFREE · BROWSER-ONLY · NO TELEMETRY · OPEN SOURCE
    ATLAS · COUNTY·AR·FIPS 05119·gis.arkansas.gov

    Pulaski County, AR
    parcel REST API.

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

    Primary ArcGIS REST endpoint
    https://gis.arkansas.gov/arcgis/rest/services/FEATURESERVICES/Planning_Cadastre/FeatureServer/6
    FeatureServer · LAYER 6 · PARCELS
    https://gis.arkansas.gov/arcgis/rest/services/FEATURESERVICES/Planning_Cadastre/FeatureServer/6

    Searchable fields

    • parcelidParcel ID
    • ownernameOwner Name
    • pstrnamStreet Name
    • adrcityCity
    • adrlabelFull Address Label

    Sample query (paste into terminal or browser)

    curl -s 'https://gis.arkansas.gov/arcgis/rest/services/FEATURESERVICES/Planning_Cadastre/FeatureServer/6/query?where=countyfips%3D'05119'+AND+UPPER(ownername)+LIKE+UPPER('%25SMITH%25')&outFields=parcelid,ownername,adrlabel,countyfips&returnGeometry=false&f=json&resultRecordCount=10'
    License
    Public records (terms)
    Listed on
    2026-06-20
    Registry listing
    Listed live
    Sample query
    https://gis.arkansas.gov/arcgis/rest/services/FEATURESERVICES/Planning_Cadastre/FeatureServer/6/query?where=countyfips='05119'+AND+UPPER(ownername)+LIKE+UPPER('%SMITH%')&outFields=parcelid,ownername,adrlabel,countyfips&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 Parcels
    Field nameLabelSearchable
    parcelidParcel ID YES
    ownernameOwner Name YES
    adrnumAddress Number NO
    pstrnamStreet Name YES
    adrcityCity YES
    adrzip5ZIP Code NO
    adrlabelFull Address Label YES
    countyfipsCounty FIPS (05119 = Pulaski) NO
    countyCounty Name NO
    assessvalueAssessed Value NO
    totalvalueTotal Value NO
    Notes

    Pulaski County AR (Little Rock, pop. 400,000; state capital; county seat Little Rock; FIPS 05119) is served by the Arkansas statewide parcel layer hosted by the Arkansas GIS Office (AGISO). The Planning_Cadastre/FeatureServer/6 layer aggregates parcels from all 75 AR counties, filter by countyfips='05119' to query Pulaski County specifically. Key fields: parcelid (parcel identifier), ownername (owner name), adrnum+pstrnam+adrcity+adrzip5 (address components), adrlabel (full address string), countyfips (5-digit FIPS, '05119' for Pulaski), countyid, county (county name text), parceltype, assessvalue, impvalue, landvalue, totalvalue, subdivision, section/township/range, camakey, dataprov, pubdate. Owner-name search via UPPER(ownername) LIKE works across all AR counties. Verified 2026-06-20: countyfips='05119' AND SMITH returns Little Rock addresses. The statewide layer is compiled from county assessor data and may lag 6–12 months from deed recording.

    Source

    Arkansas GIS Office (AGISO), https://gis.arkansas.gov/

    Using this endpoint

    What Pulaski County publishes

    Pulaski County's Parcels layer exposes a parcel identifier (Parcel ID), owner names (Owner Name), and address fields (Street Name, Full Address Label). Use it for owner-name lookups and address-based parcel searches. 5 of 11 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-06-20.

    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 Pulaski 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 Pulaski County's parcel layer from my own web app?

    gis.arkansas.gov serves Pulaski County, Arkansas 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 Pulaski County endpoint still current?

    We last verified Pulaski County's FeatureServer layer on 2026-06-20. 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 Pulaski County parcel queries?

    Pulaski County's layer is hosted by the county on gis.arkansas.gov. Public ArcGIS endpoints rarely rate-limit individual reads, but gis.arkansas.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.

    View all FAQs →

    Continue