Connecticut HOA and condominium association registrations

At a glance

Publisher

Connecticut Secretary of the State

Jurisdiction

US-CT / Connecticut

Publisher updates

Updated daily by the Secretary of the State

SourceFinch checks

Daily by default

Records per run

100 in the latest run

Record key

account_number

Acquired from

Open data portal: 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

v1.0.0, approved October 3, 2026

Verified since

October 3, 2026

Last green run

October 3, 2026

What the data contains

Connecticut common interest communities (Common Interest Ownership Act, Conn. Gen. Stat. chapter 828) are governed by associations that typically register with the Secretary of the State as non-stock corporations. The Secretary publishes the Connecticut Business Registry master table on data.ct.gov. Each run asks the dataset's SODA API for the 100 most recently registered non-stock entities whose names containing HOMEOWNER, CONDOMINIUM, PROPERTY OWNER, TOWNHOM or OWNERS ASSOC, newest first, and returns one record per entity: Business Registry account number, name, status and sub-status (for example Active, First report due), registration date and next annual report due date. A monitor reports new associations and changes in standing. Email, mailing and billing address columns are never requested. The name filter is a heuristic and can include a few non-association entities with matching words.

Fields and types

Every record has these fields. The key field account_number 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.

[
  {
    "name": "56-58 East Main Condominium Association Inc.",
    "status": "Active",
    "registered": "2026-09-23T00:00:00.000",
    "sub_status": "First report due",
    "business_type": "Non-Stock",
    "account_number": "3519703",
    "annual_report_due": "2026-12-22T00:00:00.000"
  },
  {
    "name": "Mount Pleasant Owners Association, Inc.",
    "status": "Active",
    "registered": "2026-09-02T00:00:00.000",
    "sub_status": "First report due",
    "business_type": "Non-Stock",
    "account_number": "3509678",
    "annual_report_due": "2026-12-01T00:00:00.000"
  },
  {
    "name": "Joray Road Homeowners Association, Inc.",
    "status": "Active",
    "registered": "2026-09-02T00:00:00.000",
    "sub_status": "First report due",
    "business_type": "Non-Stock",
    "account_number": "3509736",
    "annual_report_due": "2026-12-01T00:00:00.000"
  },
  {
    "name": "The Junction Homeowners Association, Inc.",
    "status": "Active",
    "registered": "2026-08-12T00:00:00.000",
    "sub_status": "Annual report due",
    "business_type": "Non-Stock",
    "account_number": "3494067",
    "annual_report_due": "2027-08-14T00:00:00.000"
  },
  {
    "name": "Prospect Street School Condominiums Inc",
    "status": "Active",
    "registered": "2026-08-06T00:00:00.000",
    "sub_status": "First report due",
    "business_type": "Non-Stock",
    "account_number": "3493047",
    "annual_report_due": "2026-11-04T00:00:00.000"
  }
]

Evidence behind every value

• Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash cca0d1c6824d685df92f7ed9020c68e84b4de3b2c830fb9c6094aa49d76350e1.
• 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 446e3b120b432f68a9cc097aa604c4d7288b8e06d451c2c9e8a54ec1f1d093c1, 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 Connecticut Open Data Portal marks the Business Registry dataset Public Domain. Its terms of use provide the data as a public service on an as-is basis with no warranty, and the State may correct or remove datasets. Anonymous SODA API access needs no key; robots.txt asks for a 1 second crawl delay.

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

0.9 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": "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
}

# 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)"

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_ID

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

const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("connecticut-hoa-condo-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 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."

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
• Florida Statutes chapter 720 (homeowners' associations) sections · The Florida Legislature (Online Sunshine)
• Henderson, Nevada homeowners' associations · City of Henderson, Nevada