Henderson, Nevada homeowners' associations

At a glance

Publisher

City of Henderson, Nevada

Jurisdiction

US-NV / Henderson, Nevada

Publisher updates

Maintained by the City of Henderson GIS as associations change

SourceFinch checks

Daily by default

Records per run

366 in the latest run

Record key

name

Acquired from

Publisher's public API: https://maps.cityofhenderson.com/arcgis/rest/services/public/HOAs/MapServer/1/query?where=1%3D1&outFields=OBJECTID,NAME,MASTER_ASSOCIATION,HOA,MASTER,INACTIVE,GATED,AGE_RESTRICTED,NUM_UNITS,WARD,MANAGEMENT_COMPANY&returnGeometry=false&orderByFields=OBJECTID&resultRecordCount=100&f=json

Recipe

v1.0.0, approved October 3, 2026

Verified since

October 3, 2026

Last green run

October 3, 2026

What the data contains

The City of Henderson, Nevada maintains a GIS layer of the homeowners' associations within the city, used by its HOA web map. Each run reads the whole layer through the City's public ArcGIS REST query service (up to 500 associations, in pages of 100) and returns one record per association: name, master association, whether it is itself a master association, whether it is marked inactive, gated (Y, N or GUARD) and age-restricted flags, number of units, City Council ward and the management company. A monitor reports associations added to or removed from the layer and changes such as a new management company or unit count. Only these columns are requested; the layer's manager and board-president name, address, phone and email columns are never read, and map geometry is not downloaded. Values are as maintained by the City; blank flags are published as a single space.

Fields and types

Every record has these fields. The key field name identifies a record across runs, so changes are reported field by field.

Sample output

The first 5 of 366 records from SourceFinch's own run on October 3, 2026, exactly as delivered.

[
  {
    "hoa": "Y",
    "name": "ACACIAS CONDOMINIUM ASSN",
    "ward": 4,
    "gated": "Y",
    "units": 1,
    "inactive": "N",
    "is_master": "N",
    "object_id": 851248,
    "age_restricted": " ",
    "management_company": "TAYLOR ASSOCIATION MANAGEMENT",
    "master_association": " "
  },
  {
    "hoa": "Y",
    "name": "ALLEGRO HOMEOWNERS ASSOCIATION",
    "ward": 4,
    "gated": " ",
    "units": 2,
    "inactive": "N",
    "is_master": "N",
    "object_id": 851249,
    "age_restricted": " ",
    "management_company": "TAYLOR ASSOCIATION MANAGEMENT",
    "master_association": " "
  },
  {
    "hoa": "Y",
    "name": "ALTEZZA HOMEOWNERS ASSOCIATION INC",
    "ward": 4,
    "gated": "Y",
    "units": 3,
    "inactive": "N",
    "is_master": "N",
    "object_id": 851250,
    "age_restricted": " ",
    "management_company": "TERRA WEST MANAGEMENT SERVICES",
    "master_association": "GVR COMMUNITY ASSOC"
  },
  {
    "hoa": "Y",
    "name": "AMBER RIDGE COMMUNITY ASSOCIATION",
    "ward": 1,
    "gated": " ",
    "units": 4,
    "inactive": "N",
    "is_master": "N",
    "object_id": 851251,
    "age_restricted": " ",
    "management_company": "NEVADA COMMUNITY MANAGEMENT",
    "master_association": " "
  },
  {
    "hoa": "Y",
    "name": "ANASAZI ESTATES HOMEOWNERS ASSOCIATION",
    "ward": 4,
    "gated": " ",
    "units": 5,
    "inactive": "N",
    "is_master": "N",
    "object_id": 851252,
    "age_restricted": " ",
    "management_company": "PRIME COMMUNITY MANAGEMENT",
    "master_association": " "
  }
]

Evidence behind every value

• Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash cad82fed7e88754c8f888d4eb5364400f8a84c7ed03587f956f67e18d06dd59f.
• Every value records where it came from in that response: a JSON Pointer into the retained capture.
• Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is fcf57e90252127ce52f85d481c27bb26117bc465f6401df148a70abbcb06c036, timestamped October 3, 2026.
• The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
• Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch: sourcefinch verify-bundle run.wacz.

Terms posture and usage rights

The City of Henderson publishes its GIS layers through an ArcGIS REST service and its open data hub under the City's Open Data Policy (2019). The HOA layer's licence information is a disclaimer: the City makes no warranty of merchantability or fitness, assumes no liability for accuracy or completeness, and provides the data as is. No registration or key is needed; the GIS host serves no robots.txt (HTTP 404), which RFC 9309 treats as allowing access.

Source: City of Henderson, Nevada GIS, HOA layer. The City makes no warranty as to the accuracy or completeness of this data.

Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.

Reliability

Runs, last 30 days

0

Green

—

Failed

0

Median run time

—

Latest run

success, October 3, 2026

Measured on runs of this recipe version across SourceFinch, anonymized. This recipe is newly Verified; the numbers fill in as it runs daily.

Use it

Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).

{
  "name": "Henderson, Nevada homeowners' associations",
  "url": "https://maps.cityofhenderson.com/arcgis/rest/services/public/HOAs/MapServer/1/query?where=1%3D1&outFields=OBJECTID,NAME,MASTER_ASSOCIATION,HOA,MASTER,INACTIVE,GATED,AGE_RESTRICTED,NUM_UNITS,WARD,MANAGEMENT_COMPANY&returnGeometry=false&orderByFields=OBJECTID&resultRecordCount=100&f=json",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "features[*]",
    "fields": {
      "hoa": "attributes.HOA",
      "name": "attributes.NAME",
      "ward": "attributes.WARD",
      "gated": "attributes.GATED",
      "units": "attributes.NUM_UNITS",
      "inactive": "attributes.INACTIVE",
      "is_master": "attributes.MASTER",
      "object_id": "attributes.OBJECTID",
      "age_restricted": "attributes.AGE_RESTRICTED",
      "management_company": "attributes.MANAGEMENT_COMPANY",
      "master_association": "attributes.MASTER_ASSOCIATION"
    },
    "pagination": {
      "kind": "param",
      "param": "resultOffset",
      "start": 0,
      "step": 100,
      "maxPages": 5
    },
    "required": [
      "name"
    ]
  },
  "key_field": "name",
  "schedule": "daily",
  "rights": true
}

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/henderson-nv-hoa-registry -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

sourcefinch login
sourcefinch catalog get henderson-nv-hoa-registry --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

import { SourceFinch } from "@tsg/sourcefinch";

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("henderson-nv-hoa-registry");
const source = await sf.sources.create({
  name: entry.name.slice(0, 100),
  url: entry.acquisition_path.endpoint,
  recipe: entry.recipe.definition,
  key_field: entry.recipe.key_field,
  schedule: entry.recipe.schedule,
  rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Henderson, Nevada homeowners' associations: get_catalog_source henderson-nv-hoa-registry,
then create_source with its create_source_args (dry run first), then run_source."

Pricing

Each check is one run, whatever the number of records, and failed runs are free. On its default daily schedule this source uses about 30 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.

Related sources

• Baltimore County, Maryland community associations · Baltimore County, Maryland
• Colorado HOA and condominium association registrations · Colorado Department of State
• Connecticut HOA and condominium association registrations · Connecticut Secretary of the State
• Florida Statutes chapter 720 (homeowners' associations) sections · The Florida Legislature (Online Sunshine)