ArcGIS Layer Requires Authentication: A Planner's Workaround
You found a county's ArcGIS REST URL, dropped it into your tool or browser, and got back HTTP 499 Token Required or 401 Authorization Required. The layer exists. The data is probably public record. But the endpoint is locked. The answer is almost never "get a token." It is almost always: find the public version of the same data somewhere else. This guide covers where to look and what each error code tells you about your options.
The Short Answer First
Three paths forward, in order of likelihood:
- Find the county's open-data hub. The locked layer and the public layer are often the same underlying dataset, published through two different access points. The GIS department's internal URL requires auth; the open data portal version does not.
- Check for an ArcGIS Online-hosted version. Public services hosted on ArcGIS Online at
services1.arcgis.com,services2.arcgis.com, orservices3.arcgis.comtypically do not require authentication unless the organization has explicitly restricted them. - Accept that the data was never intended to be public and pivot. Some county layers are legitimately staff-only: draft zoning changes, assessment appeals, internal work-in-progress. When that is the case, the open-data hub will not have a substitute. Use the Assessor's public web portal or a federal/state alternate source instead.
Why Counties Lock Layers
County GIS departments do not lock layers to be obstructionist. They lock them because their infrastructure is built around products that default to authenticated access, and getting a public-facing layer published takes deliberate extra steps that often don't happen.
The most common causes:
- Vendor-managed portals. Counties running VertiGIS (formerly Geocortex) or similar enterprise GIS platforms sit behind a gateway that requires county credentials by default. The REST service directory is technically public, but authenticated access is assumed for anything beyond basic map tile viewing.
- Subscription-model GIS. Some counties run WinGIS, Tyler Technologies EnerGov, or similar county-wide platforms where the GIS layer is considered a module of the county's internal software, not a public data product. The staff see it as an internal tool; they may not realize it is reachable externally at all.
- Assessment and appeals layers. Assessor GIS layers that include pending appeals, under-review valuations, or draft reassessment data are restricted by policy in most states. Even where the final roll is public, mid-cycle data is not.
- Draft planning layers. Proposed rezoning boundaries, pending annexation areas, and draft general plan land use maps routinely live on locked internal services until they are formally adopted. The locked layer may be exactly what you want, and the answer is to wait for the public hearing cycle.
Workaround 1: Find the County's Open-Data Hub
This works more often than people expect. Esri's ArcGIS Hub product lets counties publish curated, public-facing datasets with no authentication required. If a county subscribes to ArcGIS Online and has stood up a Hub site, the parcel layer almost certainly exists there.
Try these search patterns in order:
- Direct URL guess:
data-[countyname].opendata.arcgis.com. Example:data-mchenrycountyil.opendata.arcgis.com. About half of Illinois counties that have ArcGIS Hub sites follow this pattern. - Google search:
[county name] county open data arcgis site:opendata.arcgis.com - County GIS department page: look for a link labeled "Open Data," "GIS Data Downloads," or "Data Portal." The GIS page is usually under a department header like IT, Public Works, or Community Development.
McHenry County, Illinois is a clean example of this split. The county's on-premises GIS server returns 403 errors on its legacy parcel endpoints. But the county publishes the same parcel data through ArcGIS Online at services1.arcgis.com/6iYC5AXXYapRVNzl/arcgis/rest/services/, which is public with no token required. That is the endpoint the Parcel Atlas indexes for McHenry County.
Once you are on the Hub site, search for "parcel" or "assessor." The dataset you find will have a download button and an API endpoint. The API endpoint in the Hub layer detail page is the public URL you want.
Workaround 2: ArcGIS Online Public Services
ArcGIS Online hosts services on a set of shared infrastructure servers: services1.arcgis.com, services2.arcgis.com, services3.arcgis.com, and similar numbered subdomains. When a county publishes a layer through ArcGIS Online rather than their own on-premises server, that service URL is public by default unless the organization's administrator has explicitly toggled it to private.
The pattern for a public ArcGIS Online-hosted service looks like:
https://services1.arcgis.com/[orgId]/arcgis/rest/services/[ServiceName]/FeatureServer/0
To find it for your county:
- Go to ArcGIS Online search.
- Search for the county name plus "parcel" or "assessor." Filter to Content type: Feature Layer and Owner: Public.
- Open a result that looks like the county's official layer. Click "I want to use this" or "View in REST." The URL in the browser bar is the public endpoint you want.
A note on provenance: ArcGIS Online search returns third-party uploads alongside official county data. Before using an endpoint you find this way, check the owner organization and the layer's description. An official county GIS endpoint will typically show the county's organization name. A third-party scrape may be months out of date. The full guide to finding ArcGIS parcel layer URLs covers how to evaluate what you find.
Workaround 3: The Assessor's Public Web Portal
County GIS and the County Assessor are often separate offices. The GIS department manages the mapping infrastructure. The Assessor manages the tax roll. Their systems overlap on parcel data, but they are not always in sync, and their public-facing tools are different.
Even when the GIS REST endpoint is locked, the Assessor's property search portal is almost always public. Every county in the U.S. assesses property for tax purposes, and nearly all publish at least a basic property lookup by parcel number or address. Some publish the full assessor roll as an annual CSV download.
What the Assessor's portal gives you that the GIS layer might not:
- Owner name and mailing address (the GIS layer sometimes omits these or holds them behind a separate join)
- Current assessed value and exemption status
- Legal description and transfer history
The workflow: get parcel numbers (APNs or PINs) from the GIS open-data layer, then look up owner and mailing address data in the Assessor's portal using those parcel numbers as the key. Our guide on assessor parcel numbers explains how the numbering systems work across different counties. If you run into parcel data where owner names come back blank even on the public layer, see the sibling article on why parcel owner names appear blank, which covers the join-key mismatch that causes this.
Workaround 4: Federal and State Alternate Sources
For some use cases, the county GIS layer is not the only option. Federal and state agencies publish parcel-adjacent data that covers gaps when county sources are locked or incomplete.
USGS National Map / The National Parcel Dataset. The USGS publishes a national parcel dataset aggregated from state and county sources as part of the National Map. Coverage and freshness vary by state, and the layer does not always include owner data, but it gives you parcel geometry when the county source is inaccessible.
State DOR or Assessor aggregations. Several states run centralized property databases. Illinois, for example, has the Illinois Department of Revenue PTAX data. Wisconsin's Department of Revenue publishes a statewide parcel layer. These state-level sources sometimes have data the county portal does not expose publicly.
County open-records requests. When all digital paths are blocked, parcel data is public record under most state sunshine laws. A written public records request to the county Assessor or GIS department for a parcel data extract is a legitimate path. Responses take days to weeks and usually come as CSV or shapefile. For a one-time project, this is slower but reliable.
What Not To Do: The CFAA Problem
Before someone suggests it: do not attempt to bypass authentication on a county GIS endpoint. Passing a forged token, harvesting a valid token from the county's own web application, or scripting repeated requests designed to probe auth boundaries are all potential violations of the Computer Fraud and Abuse Act, 18 U.S.C. § 1030. Courts have interpreted "exceeding authorized access" broadly. The fact that the underlying data is public information does not change the analysis on the access method.
This is not a theoretical risk for planning professionals who occasionally hit a locked REST endpoint. It is, however, a real risk for anyone who treats auth boundaries as a puzzle to solve rather than a signal to look elsewhere. The open-data hub and Assessor portal paths described above give you the same data legally.
The HTTP Status Code Decision Tree
Each error code tells you something different about what is possible.
| Status | What it means | Your move |
|---|---|---|
HTTP 499 |
Esri-specific: token required. The service exists and is responding, but it requires an ArcGIS token to proceed. The county has the layer; it is not public at this URL. | Find the open-data hub or ArcGIS Online public service for the same data. |
HTTP 401 |
Standard auth header missing. Usually points to a vendor gateway (VertiGIS/Geocortex) in front of the Esri service. The county's credentials are required. | Cannot fix from your end. Try the open-data hub; contact the GIS department if the data is critical and unavailable elsewhere. |
HTTP 403 |
Forbidden. You are identified but not permitted. Can indicate an IP-based firewall rule or a service restricted to county-network clients only. | Contact the county GIS department. Some counties whitelist external IP ranges for known partners. Or use the open-data hub. |
HTTP 404 |
Service not found. The URL is wrong or the service was moved or renamed, most often after a county Esri upgrade or IT consolidation. | Browse the county's REST services directory at [server]/arcgis/rest/services to find the current name. Check the open-data hub for a fresh link. |
The Parcel Atlas Shortcut
The detective work described above takes 15 to 45 minutes per county. If you work with the same counties regularly, or if you just want to know whether a public endpoint already exists before starting the search, check the UrbanKit Parcel Atlas. It covers 31 counties with verified public REST endpoints, tested for accessibility and field coverage. Each entry notes whether the endpoint exposes owner name and mailing address, or whether you need to supplement with the Assessor portal.
For individual parcel lookups without building a full GIS workflow, the Parcel Lookup Tool queries public REST endpoints directly and returns parcel data by APN or address. It uses the same verified endpoints as the Atlas.
We have already verified the public REST endpoints for 31 counties.
Check the Parcel Atlas before assuming your county's layer is locked →
Or use the Parcel Lookup Tool to query public parcel data directly by APN or address.
Frequently Asked Questions
What does HTTP 499 "Token Required" mean on an ArcGIS REST endpoint?
HTTP 499 is an Esri-specific status code. The service exists and is responding, but it requires an ArcGIS token before it will return data. The county has the layer; it is not public at that URL. The fix for a planner is not to obtain a token. Find the public open-data version of the same layer through the county's Hub site or ArcGIS Online.
What is the difference between a 499 and a 401 error on an ArcGIS service?
HTTP 499 is Esri's own code for "token required." HTTP 401 means the server expected an Authorization header that was not present. In practice, a 401 on an ArcGIS REST endpoint usually points to a vendor-managed gateway (VertiGIS, Geocortex, or similar) sitting in front of the Esri service. You cannot fix a 401 from your end without credentials the county controls. Both errors lead to the same next step: look for the open-data hub.
Is it legal to try to bypass ArcGIS authentication on a county GIS layer?
No. Attempting to circumvent authentication on any computer system — including a county GIS server — is a potential violation of the Computer Fraud and Abuse Act (18 U.S.C. § 1030) even when the underlying data is public record. The data may be public; the access control on that specific endpoint is not optional. Use the open-data hub instead.
How do I find a county's ArcGIS Open Data hub?
Search Google for "[county name] open data arcgis" or try data-[countyname].opendata.arcgis.com directly. Many counties also link their hub from the GIS department page on the county's main site. Once on the hub, search "parcel" or "assessor" to find the public layer. The endpoint in the layer's detail page is the URL to use.
What if the open data hub has parcel boundaries but no owner names?
Owner names live in the Assessor's database, not always in the GIS layer. Check whether the county Assessor runs a separate public property search portal — most do. Match parcel numbers (APN or PIN) between the GIS layer and the Assessor's lookup to get owner and mailing address data. Some counties also publish a flat CSV of the assessor roll annually as a public record download.
What HTTP error means the county moved the service to a new URL?
A 404 on an endpoint you previously used usually means the county GIS department migrated or reorganized their REST services — common after an Esri version upgrade or county IT consolidation. Browse the county's ArcGIS REST services directory at [server]/arcgis/rest/services to see what is currently published, or check the open-data hub for a refreshed link.
Should I pay for an ArcGIS token or vendor access to get county parcel data?
Rarely, if ever, for standard planning workflows. County parcel data is public record in nearly every state. If the REST endpoint is locked, the open-data version almost always exists at no cost. Paying for vendor token access makes sense for enterprise GIS operations building internal tooling — not for pulling a parcel list for a public notice mailing.
Related Resources
- How to Find an ArcGIS Parcel Layer URL (FeatureServer & MapServer Guide) — the search patterns for finding a county REST endpoint before you hit an auth wall
- What is an APN? — how assessor parcel numbers work and why they are the join key between GIS and Assessor data
- Why Parcel Owner Names Come Back Blank — what to do when the public layer returns geometry but no owner fields
- UrbanKit Parcel Atlas — 31 counties with verified public REST endpoints, tested for field coverage
- Parcel Lookup Tool — query public parcel endpoints directly by APN or address without building a GIS workflow