Colorado HOA and condominium association registrations

At a glance

Publisher

Colorado Department of State

Jurisdiction

US-CO / Colorado

Publisher updates

Refreshed daily by the Colorado Department of State

SourceFinch checks

Daily by default

Records per run

100 in the latest run

Record key

entity_id

Acquired from

Open data portal: https://data.colorado.gov/resource/4ykn-tg5h.json?$select=entityid,entityname,entitystatus,entitytype,entityformdate,principalcity,principalstate,principalzipcode&$where=entitytype%20in('DNC','UNA')%20AND%20(upper(entityname)%20like%20'%25HOMEOWNER%25'%20OR%20upper(entityname)%20like%20'%25CONDOMINIUM%25'%20OR%20upper(entityname)%20like%20'%25PROPERTY%20OWNER%25'%20OR%20upper(entityname)%20like%20'%25TOWNHOM%25'%20OR%20upper(entityname)%20like%20'%25OWNERS%20ASSOC%25')&$order=entityformdate%20DESC,%20entityid&$limit=100

Recipe

v1.0.0, approved October 3, 2026

Verified since

October 3, 2026

Last green run

October 3, 2026

What the data contains

Colorado community associations (homeowners', property owners', townhome and condominium associations governed by the Colorado Common Interest Ownership Act, C.R.S. 38-33.3) are registered with the Colorado Department of State as nonprofit corporations or unincorporated nonprofit associations. The Department publishes every registered entity as the Business Entities in Colorado dataset on the Colorado Information Marketplace. Each run asks the dataset's SODA API for the 100 most recently formed domestic nonprofit corporations (DNC) and unincorporated nonprofit associations (UNA) whose names containing HOMEOWNER, CONDOMINIUM, PROPERTY OWNER, TOWNHOM or OWNERS ASSOC, newest first, and returns one record per entity: Secretary of State entity ID, legal name, standing, entity type, formation date and the principal office's city, state and ZIP. A monitor reports new associations and status changes such as delinquency. Registered agent names and street addresses are never requested. The name filter is a heuristic: a few non-association entities with matching words can appear, and associations named only "Association" are not included.

Fields and types

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

Sample output

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

[
  {
    "zip": "81501",
    "city": "Grand Junction",
    "name": "Monument Vistas Homeowners Association, Inc.",
    "state": "CO",
    "formed": "2026-09-25T00:00:00.000",
    "status": "Good Standing",
    "entity_id": "20268201086",
    "entity_type": "DNC"
  },
  {
    "zip": "80111",
    "city": "Greenwood Village",
    "name": "Turnberry Filing 7 Homeowners Association, Inc",
    "state": "CO",
    "formed": "2026-09-24T00:00:00.000",
    "status": "Good Standing",
    "entity_id": "20268193507",
    "entity_type": "DNC"
  },
  {
    "zip": "80112",
    "city": "Centennial",
    "name": "Parker Homestead Owners Association",
    "state": "CO",
    "formed": "2026-09-23T00:00:00.000",
    "status": "Good Standing",
    "entity_id": "20268175466",
    "entity_type": "DNC"
  },
  {
    "zip": "80521",
    "city": "Fort Collins",
    "name": "OLD ELK HANGAR CONDOMINIUM ASSOCIATION",
    "state": "CO",
    "formed": "2026-09-23T00:00:00.000",
    "status": "Good Standing",
    "entity_id": "20268183683",
    "entity_type": "DNC"
  },
  {
    "zip": "81505",
    "city": "Grand Junction",
    "name": "Aspen Breeze Estates Homeowners Association, Inc.",
    "state": "CO",
    "formed": "2026-09-17T00:00:00.000",
    "status": "Good Standing",
    "entity_id": "20268154448",
    "entity_type": "DNC"
  }
]

Evidence behind every value

• Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash 9777ba4a44eb0ef6c9d8ed97c31cc1ed1d1adc985e67edd3c6817dffd3032db0.
• 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 e9e519fd99b8b9ac3eb8c2ef1bfccbcb23b7bd8d2924afd2e74c237c0fd8faca, 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 Colorado Information Marketplace marks the Business Entities dataset Public Domain. Its terms of service disclaim any warranty, let the State modify or discontinue feeds, and ask applications using the data to state that it was modified for use from its original source, the State of Colorado, with the State's no-warranty disclaimer. Anonymous SODA API access needs no key; robots.txt asks for a 1 second crawl delay.

The data made available here has been modified for use from its original source, which is the State of Colorado. THE STATE OF COLORADO MAKES NO REPRESENTATIONS OR WARRANTY AS TO THE COMPLETENESS, ACCURACY, TIMELINESS, OR CONTENT OF ANY DATA MADE AVAILABLE THROUGH THIS SITE. THE STATE OF COLORADO EXPRESSLY DISCLAIMS ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. The data is subject to change as modifications and updates are complete. It is understood that the information contained in the Web feed is being used at one's own risk.

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

1

Green

100%

Failed

0

Median run time

1.1 s

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": "Colorado HOA and condominium association registrations",
  "url": "https://data.colorado.gov/resource/4ykn-tg5h.json?$select=entityid,entityname,entitystatus,entitytype,entityformdate,principalcity,principalstate,principalzipcode&$where=entitytype%20in('DNC','UNA')%20AND%20(upper(entityname)%20like%20'%25HOMEOWNER%25'%20OR%20upper(entityname)%20like%20'%25CONDOMINIUM%25'%20OR%20upper(entityname)%20like%20'%25PROPERTY%20OWNER%25'%20OR%20upper(entityname)%20like%20'%25TOWNHOM%25'%20OR%20upper(entityname)%20like%20'%25OWNERS%20ASSOC%25')&$order=entityformdate%20DESC,%20entityid&$limit=100",
  "recipe": {
    "mode": "http",
    "format": "json",
    "items": "[*]",
    "fields": {
      "zip": "principalzipcode",
      "city": "principalcity",
      "name": "entityname",
      "state": "principalstate",
      "formed": "entityformdate",
      "status": "entitystatus",
      "entity_id": "entityid",
      "entity_type": "entitytype"
    },
    "required": [
      "entity_id",
      "name"
    ]
  },
  "key_field": "entity_id",
  "schedule": "daily",
  "rights": true
}

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/colorado-hoa-condo-entity-registrations -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 colorado-hoa-condo-entity-registrations --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("colorado-hoa-condo-entity-registrations");
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 Colorado HOA and condominium association registrations: get_catalog_source colorado-hoa-condo-entity-registrations,
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
• Connecticut HOA and condominium association registrations · Connecticut Secretary of the State
• Florida Statutes chapter 720 (homeowners' associations) sections · The Florida Legislature (Online Sunshine)
• Henderson, Nevada homeowners' associations · City of Henderson, Nevada