Guide · 3 Verified sources
Monitor new HOA and condominium association registrations
Follow newly registered homeowners', property owners' and condominium associations in Colorado, Connecticut and New York state registries, with alerts for new associations and changes in standing.
Start with Colorado HOA and condominium association registrationsREST API, CLI and MCP
The problem
Homeowners', property owners' and condominium associations register with their state's business registry when they form. Management companies, insurers, lenders and service providers who work with associations want to know when new ones appear and when an existing one's standing changes.
This guide monitors three state registries that publish open data: Colorado, Connecticut and New York. Each source asks the state's public dataset for the 100 most recently formed or registered entities whose names look like an association, and returns one record per entity.
What the source contains
Colorado HOA and condominium association registrations · Colorado Department of State
Newly formed Colorado homeowners', property owners' and condominium associations from the Colorado Department of State's Business Entities dataset: entity ID, name, status, nonprofit type, formation date and principal city.
8 typed fields · 100 records in SourceFinch's latest run on October 12, 2026 · publisher updates: refreshed daily by the Colorado Department of State · full source page
| Field | Type | Description | Sample value |
|---|---|---|---|
entity_idkey | string | Colorado Secretary of State entity ID. The record key. | 20268253873 |
name | string | Legal name of the association. | Golden Garages of McIntyre Condominiums |
status | string, nullable | Standing, for example Good Standing, Delinquent or Voluntarily Dissolved. | Good Standing |
entity_type | enum | DNC = domestic nonprofit corporation, UNA = unincorporated nonprofit association. | DNC |
formed | datetime, nullable | Formation date (midnight, no time zone, as published). | 2026-10-08T00:00:00.000 |
city | string, nullable | City of the principal office. | Golden |
state | string, nullable | State of the principal office. | CO |
zip | string, nullable | ZIP code of the principal office. | 80401 |
Connecticut HOA and condominium association registrations · Connecticut Secretary of the State
Newly registered Connecticut condominium, homeowners' and property owners' associations from the Secretary of the State's Business Registry: account number, name, status, registration date and annual report due date.
7 typed fields · 100 records in SourceFinch's latest run on October 12, 2026 · publisher updates: updated daily by the Secretary of the State · full source page
Fields and a sample record
| Field | Type | Description | Sample value |
|---|---|---|---|
account_numberkey | string | Connecticut Business Registry account number. The record key. | 3519703 |
name | string | Registered name of the entity. | 56-58 East Main Condominium Association Inc. |
business_type | string | Business type; always Non-Stock in this source. | Non-Stock |
status | string, nullable | Registry status, for example Active. | Active |
sub_status | string, nullable | Sub-status, for example First report due. | Annual report due |
registered | datetime, nullable | Registration date (midnight, no time zone, as published). | 2026-09-23T00:00:00.000 |
annual_report_due | datetime, nullable | Next annual report due date (midnight, no time zone, as published). | 2027-10-03T00:00:00.000 |
New York HOA and condominium association corporations · New York Department of State
Newly incorporated New York homeowners', property owners' and condominium associations from the Department of State's Active Corporations dataset: DOS ID, name, filing date and county.
6 typed fields · 100 records in SourceFinch's latest run on October 12, 2026 · publisher updates: refreshed by the Department of State (monthly snapshot, updated on data.ny.gov) · full source page
Fields and a sample record
| Field | Type | Description | Sample value |
|---|---|---|---|
dos_idkey | string | New York Department of State corporation ID. The record key. | 8037905 |
name | string | Current name of the corporation. | 655 BALTIC STREET CONDOMINIUM ASSOCIATION, INCORPORATED |
filed | datetime, nullable | Initial Department of State filing date (midnight, no time zone, as published). | 2026-10-05T00:00:00.000 |
county | string, nullable | County named in the filing. | Kings |
jurisdiction | string, nullable | Jurisdiction of incorporation (New York for domestic corporations). | New York |
entity_type | string | Entity type; always DOMESTIC NOT-FOR-PROFIT CORPORATION in this source. | DOMESTIC NOT-FOR-PROFIT CORPORATION |
What a change means
- A new record: an entity newly formed or registered in that state.
- Colorado and Connecticut: a change to
status(andsub_statusin Connecticut), such as delinquency or a first annual report coming due. - New York: the dataset lists active corporations only, so one that dissolves or becomes inactive drops out and shows as a removed record.
Set it up in the console
- Open the Verified recipe. Open the Colorado HOA and condominium association registrations recipe in the console. It keeps the reviewed URL, fields and record key (entity_id), and shows the latest captured sample. Open in the console
- Create the monitor. Name the monitor, keep the daily schedule or pick another (the console shows the monthly run cost), confirm that you have the right to monitor the source, and choose Create monitor.
- Run the baseline. The first run is the baseline: every record is new. From the second run on, the monitor reports what was added, changed or removed, field by field, with the evidence behind each value.
- Choose how you hear about changes. In Alerts, choose immediate change emails or a daily or weekly digest; each monitor can override that on its own page. For your own systems, add a signed webhook in Destinations. Alerts and team
- Repeat for each state you need. Open the Connecticut and New York recipes the same way. Each state is a separate monitor, so you can keep only the states you work in.
The other recipes: Connecticut HOA and condominium association registrations, New York HOA and condominium association corporations.
The same through the REST API, CLI or MCP
Every surface creates the same monitor from the same Verified recipe. You confirm you have the right to collect the source (rights: true).
Colorado HOA and condominium association registrations
REST API
Create an API key under Console → API & access. Reference: /docs/api.
# 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)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
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_IDMCP
Remote MCP server with OAuth; see /docs/mcp.
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."source.json
The request body the API and CLI examples send.
{
"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,
"catalog": {
"slug": "colorado-hoa-condo-entity-registrations",
"version_id": "c3b903de-5e25-4123-b112-3b33db42e2e2"
}
}Connecticut HOA and condominium association registrations
REST API
Create an API key under Console → API & access. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/connecticut-hoa-condo-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)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
sourcefinch login
sourcefinch catalog get connecticut-hoa-condo-registrations --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDMCP
Remote MCP server with OAuth; see /docs/mcp.
claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp
# then ask your agent:
"Use SourceFinch to monitor Connecticut HOA and condominium association registrations: get_catalog_source connecticut-hoa-condo-registrations,
then create_source with its create_source_args (dry run first), then run_source."source.json
The request body the API and CLI examples send.
{
"name": "Connecticut HOA and condominium association registrations",
"url": "https://data.ct.gov/resource/n7gp-d28j.json?$select=accountnumber,name,business_type,status,sub_status,date_registration,annual_report_due_date&$where=business_type%20%3D%20'Non-Stock'%20AND%20(upper(name)%20like%20'%25HOMEOWNER%25'%20OR%20upper(name)%20like%20'%25CONDOMINIUM%25'%20OR%20upper(name)%20like%20'%25PROPERTY%20OWNER%25'%20OR%20upper(name)%20like%20'%25TOWNHOM%25'%20OR%20upper(name)%20like%20'%25OWNERS%20ASSOC%25')&$order=date_registration%20DESC,%20accountnumber&$limit=100",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"name": "name",
"status": "status",
"registered": "date_registration",
"sub_status": "sub_status",
"business_type": "business_type",
"account_number": "accountnumber",
"annual_report_due": "annual_report_due_date"
},
"required": [
"account_number",
"name"
]
},
"key_field": "account_number",
"schedule": "daily",
"rights": true,
"catalog": {
"slug": "connecticut-hoa-condo-registrations",
"version_id": "5159fa61-f1dc-4bf8-b4d8-f05e3562dd96"
}
}New York HOA and condominium association corporations
REST API
Create an API key under Console → API & access. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/new-york-hoa-condo-corporations -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)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
sourcefinch login
sourcefinch catalog get new-york-hoa-condo-corporations --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDMCP
Remote MCP server with OAuth; see /docs/mcp.
claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp
# then ask your agent:
"Use SourceFinch to monitor New York HOA and condominium association corporations: get_catalog_source new-york-hoa-condo-corporations,
then create_source with its create_source_args (dry run first), then run_source."source.json
The request body the API and CLI examples send.
{
"name": "New York HOA and condominium association corporations",
"url": "https://data.ny.gov/resource/n9v6-gdp6.json?$select=dos_id,current_entity_name,initial_dos_filing_date,county,jurisdiction,entity_type&$where=entity_type%20%3D%20'DOMESTIC%20NOT-FOR-PROFIT%20CORPORATION'%20AND%20(upper(current_entity_name)%20like%20'%25HOMEOWNER%25'%20OR%20upper(current_entity_name)%20like%20'%25CONDOMINIUM%25'%20OR%20upper(current_entity_name)%20like%20'%25PROPERTY%20OWNER%25'%20OR%20upper(current_entity_name)%20like%20'%25TOWNHOM%25'%20OR%20upper(current_entity_name)%20like%20'%25OWNERS%20ASSOC%25')&$order=initial_dos_filing_date%20DESC,%20dos_id&$limit=100",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"name": "current_entity_name",
"filed": "initial_dos_filing_date",
"county": "county",
"dos_id": "dos_id",
"entity_type": "entity_type",
"jurisdiction": "jurisdiction"
},
"required": [
"dos_id",
"name"
]
},
"key_field": "dos_id",
"schedule": "daily",
"rights": true,
"catalog": {
"slug": "new-york-hoa-condo-corporations",
"version_id": "54d1c89d-edbb-4449-8e1c-64be15228cf9"
}
}Alerts and evidence
Registrations arrive a few at a time, so a weekly digest is usually enough. Use a webhook if new associations should land in a CRM.
Every run keeps the publisher's exact response with its SHA-256 hash and a signed manifest, and every value points back to where it was read. How that works is in the docs:
Limitations
- The name filter is a heuristic: a few non-association entities with matching words can appear, and associations without the matched words in their names are missed (in Colorado, associations named only “Association” are not included).
- Each run reads the 100 most recently formed or registered matching entities. An older entity leaving that window has not dissolved.
- Many New York condominiums are unincorporated and do not appear in the New York dataset.
- Registered agent names, process addresses and email, mailing or billing addresses are never requested.
Usage rights, terms posture and reliability for each source are on its source page. They are our documented understanding of each publisher's stated terms, not legal advice.
Related
SourceFinch is independent and is not affiliated with or endorsed by Colorado Department of State, Connecticut Secretary of the State, New York Department of State. This guide describes their public data as SourceFinch acquires it. It is not legal, medical or financial advice.