SourceFinch Verified · Community associations & real estate
Oregon HOA and condominium association nonprofit corporations
Newly registered Oregon homeowners' and condominium unit owners' associations from the Secretary of State's Active Nonprofit Corporations dataset: registry number, name, registry date, nonprofit type and principal-place city.
- Healthy
- US-OR / Oregon
- Open data portal
- 7 typed fields
Monitor this sourceAPI, CLI, SDK and MCP SourceFinch is invite-only right now; request access.
At a glance
- Jurisdiction
- US-OR / Oregon
- Publisher updates
- Monthly snapshot, first working day of each month
- SourceFinch checks
- Daily by default
- Records per run
- 100 in the latest run
- Record key
registry_number- Acquired from
- Open data portal:
https://data.oregon.gov/resource/8kyv-b2kw.json?$select=registry_number,business_name,registry_date,nonprofit_type,city,state,zip_code&$where=entity_type%20%3D%20'DOMESTIC%20NONPROFIT%20CORPORATION'%20AND%20associated_name_type%20%3D%20'PRINCIPAL%20PLACE%20OF%20BUSINESS'%20AND%20(upper(business_name)%20like%20'%25HOMEOWNER%25'%20OR%20upper(business_name)%20like%20'%25CONDOMINIUM%25'%20OR%20upper(business_name)%20like%20'%25PROPERTY%20OWNER%25'%20OR%20upper(business_name)%20like%20'%25TOWNHOM%25'%20OR%20upper(business_name)%20like%20'%25OWNERS%20ASSOC%25')&$order=registry_date%20DESC,%20registry_number&$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
Oregon planned communities (ORS chapter 94) and condominiums (ORS chapter 100) are run by homeowners' and unit owners' associations that usually incorporate as domestic nonprofit corporations with the Oregon Secretary of State, Corporation Division. The Division publishes the active nonprofit corporations on data.oregon.gov, one row per entity per associated name (principal place of business, mailing address, registered agent, president, secretary). Each run asks the dataset's SODA API for the principal-place-of-business rows of the 100 most recently registered domestic nonprofit corporations whose names containing HOMEOWNER, CONDOMINIUM, PROPERTY OWNER, TOWNHOM or OWNERS ASSOC, newest first, and returns one record per corporation: registry number, business name, registry date, nonprofit type (mutual benefit, public benefit, religious) and the principal place's city, state and ZIP. Officer and registered-agent rows, and street addresses, are never requested. A monitor reports new associations; the dataset is a monthly snapshot of active corporations.
Fields and types
Every record has these fields. The key field registry_number identifies a record across runs, so changes are reported field by field.
| Field | Type | Description |
|---|---|---|
registry_numberkey | string | Oregon Corporation Division registry number. The record key. |
name | string | Business name of the corporation (truncated by the publisher at 50 characters). |
registered | string, nullable | Registry date as published (YYYY-MM-DD HH:MM:SS, no time zone). |
nonprofit_type | string, nullable | Nonprofit type, for example MUTUAL BENEFIT WITH MEMBERS. |
city | string, nullable | City of the principal place of business. |
state | string, nullable | State of the principal place of business. |
zip | string, nullable | ZIP code of the principal place of business. |
Sample output
The first 5 of 100 records from SourceFinch's own run on October 3, 2026, exactly as delivered.
| Field | Record 1 | Record 2 | Record 3 | Record 4 | Record 5 |
|---|---|---|---|---|---|
registry_number | 262637391 | 260644795 | 259466192 | 259306893 | 259320191 |
name | ELSA MEADOWS TOWNHOME CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC. | HELENSVIEW TOWNHOME CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC. | SOUTHEAST 89 GRANT CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC. | PARKLANE CONDOMINIUM OWNERS ASSOCIATION | NEW YORK CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC. |
registered | 2026-09-09 00:00:00 | 2026-07-23 00:00:00 | 2026-06-26 00:00:00 | 2026-06-23 00:00:00 | 2026-06-23 00:00:00 |
nonprofit_type | MUTUAL BENEFIT WITH MEMBERS | MUTUAL BENEFIT | MUTUAL BENEFIT WITH MEMBERS | MUTUAL BENEFIT WITH MEMBERS | MUTUAL BENEFIT WITH MEMBERS |
city | CLACKAMAS | GRESHAM | CLACKAMAS | WEST LINN | VANCOUVER |
state | OR | OR | OR | OR | WA |
zip | 97015 | 97080 | 97015 | 97068 | 98663 |
Sample as JSON
[
{
"zip": "97015",
"city": "CLACKAMAS",
"name": "ELSA MEADOWS TOWNHOME CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC.",
"state": "OR",
"registered": "2026-09-09 00:00:00",
"nonprofit_type": "MUTUAL BENEFIT WITH MEMBERS",
"registry_number": "262637391"
},
{
"zip": "97080",
"city": "GRESHAM",
"name": "HELENSVIEW TOWNHOME CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC.",
"state": "OR",
"registered": "2026-07-23 00:00:00",
"nonprofit_type": "MUTUAL BENEFIT",
"registry_number": "260644795"
},
{
"zip": "97015",
"city": "CLACKAMAS",
"name": "SOUTHEAST 89 GRANT CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC.",
"state": "OR",
"registered": "2026-06-26 00:00:00",
"nonprofit_type": "MUTUAL BENEFIT WITH MEMBERS",
"registry_number": "259466192"
},
{
"zip": "97068",
"city": "WEST LINN",
"name": "PARKLANE CONDOMINIUM OWNERS ASSOCIATION",
"state": "OR",
"registered": "2026-06-23 00:00:00",
"nonprofit_type": "MUTUAL BENEFIT WITH MEMBERS",
"registry_number": "259306893"
},
{
"zip": "98663",
"city": "VANCOUVER",
"name": "NEW YORK CONDOMINIUMS UNIT OWNERS ASSOCIATION, INC.",
"state": "WA",
"registered": "2026-06-23 00:00:00",
"nonprofit_type": "MUTUAL BENEFIT WITH MEMBERS",
"registry_number": "259320191"
}
]Evidence behind every value
- Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash
e25918dbf287e32f2a46d6347f72decb70ca19afa3e49c84a7bbd2b4bf6aec59. - 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
7b72cd546160f11109fa9354fa57216543ce30645f848a043ba41b157fb26541, 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
- Terms
- Terms are silent on automated access · publisher's terms
- robots.txt
- Allows this path · SHA-256
6db365e53458d373… - AI-preference signals
- None observed at review
- Public record
- Yes. Oregon business registry filings are public records (ORS 65 nonprofit corporations; ORS 192.311 et seq., Oregon Public Records Law).
- Reviewed
- October 3, 2026; next review April 3, 2027
- Licence basis
- Publisher's terms of use
- Commercial use
- Unknown
- Redistribution
- Unknown
- Attribution
- Required (text below)
data.oregon.gov publishes the Corporation Division's dataset for public use through Socrata's anonymous SODA API; no key is needed for moderate use and robots.txt asks for a 1 second crawl delay. The dataset carries no separate licence and the portal links only Tyler Technologies' general terms, which do not restrict reuse of agency data. Business registry records are public records of the Secretary of State.
Source: Oregon Secretary of State, Corporation Division, Active Nonprofit Corporations (data.oregon.gov).
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).
Console
Open this recipe in the console: it loads the URL, fields and key, samples the source live, and saves a monitor on the daily schedule.
source.json
The request body used by the API, CLI and SDK examples.
{
"name": "Oregon HOA and condominium association nonprofit corporations",
"url": "https://data.oregon.gov/resource/8kyv-b2kw.json?$select=registry_number,business_name,registry_date,nonprofit_type,city,state,zip_code&$where=entity_type%20%3D%20'DOMESTIC%20NONPROFIT%20CORPORATION'%20AND%20associated_name_type%20%3D%20'PRINCIPAL%20PLACE%20OF%20BUSINESS'%20AND%20(upper(business_name)%20like%20'%25HOMEOWNER%25'%20OR%20upper(business_name)%20like%20'%25CONDOMINIUM%25'%20OR%20upper(business_name)%20like%20'%25PROPERTY%20OWNER%25'%20OR%20upper(business_name)%20like%20'%25TOWNHOM%25'%20OR%20upper(business_name)%20like%20'%25OWNERS%20ASSOC%25')&$order=registry_date%20DESC,%20registry_number&$limit=100",
"recipe": {
"mode": "http",
"format": "json",
"items": "[*]",
"fields": {
"zip": "zip_code",
"city": "city",
"name": "business_name",
"state": "state",
"registered": "registry_date",
"nonprofit_type": "nonprofit_type",
"registry_number": "registry_number"
},
"required": [
"registry_number",
"name"
]
},
"key_field": "registry_number",
"schedule": "daily",
"rights": true
}REST API
Create an API key under Console → API keys. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/oregon-hoa-condo-nonprofit-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 oregon-hoa-condo-nonprofit-corporations --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDTypeScript SDK
The SDK is not on npm yet; see /docs/sdk.
import { SourceFinch } from "@tsg/sourcefinch";
const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("oregon-hoa-condo-nonprofit-corporations");
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);MCP
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 Oregon HOA and condominium association nonprofit corporations: get_catalog_source oregon-hoa-condo-nonprofit-corporations,
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
SourceFinch is independent and is not affiliated with or endorsed by Oregon Secretary of State, Corporation Division. This page describes oregon hoa and condominium association nonprofit corporations as SourceFinch acquires it.