UCC Filing Records - CT, CO, OR + NYC/NY Liens

UCC financing statements, farm-product liens and tax warrants from eleven public registers in Connecticut, Colorado, Oregon and New York. One schema across all of them: look up a debtor, a secured party or a filing number, pull one row per filing, screen a company name, or watch for new filings.

Low cost

From $0.00005 per record, down to $0.00003 at Gold.

What you get

Every record carries the same keys, whichever register it came from:

• corpus, jurisdiction, state - which register and where
• recordKind - debtor, secured_party, party, collateral, filing, document or warrant
• lienType - farm_products on the two farm registers, the register's own label elsewhere
• filingNumber, originalFilingNumber, filingType, filingDate, lapseDate
• debtorName, securedPartyName
• status - derived into active / lapsed / terminated / satisfied / unknown
• statusRaw - the register's own word, always preserved
• amount, address, city, stateCode, zip
• collateral, collateralCount, product, county, partyRole
• sourceUrl, sourceUpdatedAt

Every record also carries debtorNames[], securedPartyNames[] and debtorCount; outside mode=filings those are empty, because the record is one party row rather than a filing - except co-farm, where one row already lists the additional debtors. Colorado publishes the debtor, secured-party and collateral sides as separate tables: a mode=filings record from co or co-farm carries the debtor names, while co-secured, co-collateral and co-filing filing keys carry no party names themselves (the sides are separate registers, co and co-secured).

Registers

corpus	Register	Rows	recordKind
ct	Connecticut UCC filing index	~849,600 debtor rows / ~438,100 filings	debtor
co	Colorado UCC debtor register	~2,024,500 debtor rows / ~1,606,600 filings	debtor
co-collateral	Colorado UCC collateral	~1,711,500 rows	collateral
co-secured	Colorado UCC secured parties	~2,095,100 rows	secured_party
co-filing	Colorado UCC filing information	2,606,100 transactions	filing
co-farm	Colorado farm-products EFS	54,246 rows / 5,164 filings	debtor
or	Oregon UCC secured parties	~220,000 rows / ~214,900 filings	secured_party
or-farm	Oregon farm-products master list	124,703 rows / 8,130 filings	debtor / secured_party
or-filings	Oregon UCC entered last month	5,990 rows (rolling window)	debtor / secured_party
nyc-acris	NYC ACRIS personal property	~4,553,000 documents	document / debtor
ny	New York State tax warrants	~698,800 since 2025-07-01	warrant

Modes

mode=rows (default) returns one record per source row.

mode=filings collapses rows onto the filing number and returns one row per filing - debtorNames[], securedPartyNames[], debtorCount. Use it when the filing, not the party row, is what you are buying. Connecticut's ~849,600 debtor rows collapse to ~438,100 filings. maxResults in this mode counts filings delivered, not source rows; the arrays hold the party rows retrieved for those filings (a second pass, capped at 5,000 source rows).

mode=monitor returns only records filed after the last run for the same Apify user, and advances a per-user, per-register watermark stored in the actor's key-value store. The watermark is a row-level cursor on the oldest date delivered in the batch, so a page that spans several dates cannot skip the older ones; already-delivered rows are remembered by a row key (filing + party + status), not just by filing number, so a filing that names several debtors is not truncated to its first row. The cursor remembers up to 20,000 delivered row keys. Owner runs do not advance the watermark unless sinceLastRun=true. If a single date holds more undelivered rows than one page can traverse, the run fails with a clear message rather than returning nothing forever - use mode=rows with dateFrom/dateTo for that window.

mode=company requires name and state (CT, CO, OR or NY) and screens every register of that state for party names that start with the query. Each record says matchType: exact or prefix. This is not entity resolution - see the limits below.

Examples

{ "corpus": "ct", "debtor": "SMITH", "maxResults": 100 }

{ "corpus": "co", "filingNumber": "2609784" }

{ "corpus": "co-collateral", "filingNumber": "2610622", "maxResults": 20 }

{ "corpus": "co-secured", "securedParty": "WELLS FARGO", "maxResults": 100 }

{ "corpus": "co-filing", "filingType": "lien_irs", "maxResults": 100 }

{ "corpus": "co-farm", "debtor": "SMITH", "maxResults": 100 }

{ "corpus": "or", "securedParty": "WELLS FARGO", "maxResults": 100 }

{ "corpus": "or-farm", "securedParty": "FARM SERVICE AGENCY", "maxResults": 100 }

{ "corpus": "or-filings", "lienType": "UCC", "maxResults": 100 }

{ "corpus": "nyc-acris", "debtor": "SMITH", "maxResults": 100 }

{ "corpus": "ny", "status": "Added", "city": "BUFFALO", "maxResults": 100 }

{ "mode": "filings", "corpus": "co", "debtor": "SMITH", "maxResults": 50 }

{ "mode": "monitor", "corpus": "co-filing", "maxResults": 100 }

{ "mode": "company", "name": "SMITH", "state": "CO", "maxResults": 50 }

Colorado collateral coverage

Colorado publishes collateral on a separate table. Measured 2026-10-23:

• 1,377,087 of 1,606,615 Colorado filings (~86%) have at least one collateral row.
• 1,376,807 filings (~86%) have at least one readable description. Colorado writes the literal text UNKNOWN when a filer left the field blank (945,489 rows, 55%); that placeholder is normalised to an empty collateral and is not counted.
• collateral shows up to three distinct descriptions joined by |; collateralCount counts the distinct descriptions retrieved for that filing (the join fetches a bounded page per filing, so a filing with an unusually long collateral list can report fewer than it has).
• corpus=co joins the collateral and filing tables onto each debtor row by fileId, so a Colorado debtor record carries its filing date, lapse date and collateral without a second call.

corpus=co-filing is the transaction view: Initial Filing, Amendment, Filing Officer Correction and Correction, with fileid as the join key to the debtor, collateral and secured-party tables.

Derived status

status is computed from the register's own fields; statusRaw keeps the original word. An unrecognised combination is unknown - never guessed.

corpus	Raw -> status
ct	Active -> active (lapsed if lapseDate is past) / Released -> satisfied / Terminated -> terminated
co, co-secured, co-collateral	active -> active (lapsed if lapseDate is past) / inactive -> terminated when the action is a delete, otherwise unknown / a termination transaction on the filing -> terminated
co-filing	terminationflag=true -> terminated / lapseDate past -> lapsed / otherwise active
co-farm	effective financing statement -> active (the register carries no status word and no lapse date, so statusRaw is empty)
or	IRS-X -> satisfied / lapseDate past -> lapsed / known lien code (UCC / EFS / IRS / CW / RW / TU / PF / ASL / APL) -> active / anything else -> unknown
or-farm	lapseDate past -> lapsed / known farm code (EFS / ASL / APL) -> active / anything else -> unknown
or-filings	IRS-X -> satisfied / lapseDate past -> lapsed / known lien code -> active / anything else -> unknown
ny	satisfaction date -> satisfied / vacate date -> terminated / Added / Updated -> active / Closed with neither date -> unknown
nyc-acris	TERM -> terminated / RLSE -> satisfied / good-through date past -> lapsed / INIT / INIC / UCC1 / FL / FTL / CONT / AMND / ASGN / RFL / UCC3 / SUBO -> active

Status filters accept the source word or the derived word where the register can answer it; anything else is rejected with a clear error rather than silently ignored.

Which fields each register fills

corpus	debtorName	securedPartyName	filingDate	lapseDate	amount	collateral	derived status
ct	yes	yes	yes	yes	-	-	yes
co	yes	-	via co-filing	via co-filing	-	via co-collateral	yes
co-collateral	-	-	via co-filing	via co-filing	-	yes	yes
co-secured	-	yes	via co-filing	via co-filing	-	-	yes
co-filing	-	-	yes	yes	-	-	yes
co-farm	yes	yes	yes	-	-	product / crop	yes
or	-	yes	yes	yes	-	-	yes
or-farm	debtor rows	secured-party rows	yes	yes	-	product / crop	yes
or-filings	debtor rows	secured-party rows	yes	yes	-	-	yes
nyc-acris	name screens only	-	yes	yes	often 0	yes	yes
ny	yes	-	yes	sparse (~11%)	yes	-	yes

Honest limits

• A row is not always a filing. Connecticut and Colorado publish one row per debtor; Colorado collateral is one row per collateral entry; Oregon UCC is one row per secured party; New York publishes one row per warrant status record (a warrant can appear on several rows as its status changes); ACRIS is document-level. recordKind tells you which. Use mode=filings for one row per filing.
• Oregon UCC has no debtor name. corpus=or indexes the lender side, so debtor is rejected there rather than silently ignored. The Oregon farm and last-month registers carry both sides.
• corpus=or-filings is a rolling one-month window, not history. The publisher replaces it each month; a filing absent from it is not "no filing", only outside the snapshot. Use corpus=or for the current Oregon register.
• Colorado's debtor table has no date column. co and the two Colorado detail tables obtain filing and lapse dates by joining fileid against the filing-information table, so a date filter resolves through that table first. The window is resolved against the newest 6,000 filings in it, then the detail rows are read with every other filter applied server-side; a window holding more than 6,000 filings is therefore sampled (raise maxResults for more of the same window, but not beyond that ceiling).
• NYC ACRIS debtor screens are prefix-match only. The parties table is 11 million rows and a leading-wildcard search times out at the source.
• mode=company is a name screen, not entity resolution. It matches the start of a party name in one state's registers and deliberately does not merge records, assert that two same-named parties are one legal entity, or carry identifiers across registers. A common name such as SMITH will return unrelated people and businesses; treat matchType and the filing number as the facts. Each register contributes at most 500 prefix matches, so a very broad name is sampled per register rather than exhaustively paged.
• New York's warrant feed is windowed from 2025-07-01 (~699,000 rows), and one warrant can appear on several rows as its status changes.
• lienType is not a national taxonomy. The farm registers use farm_products; every other register keeps its own label.
• Filters a register cannot honour are rejected with a clear error - none are dropped.
• Each register has its own integrity guard; a register that structurally changes or collapses fails the run instead of returning empty rows.

Related

Also available in this account: NYC ACRIS (document lookups with parties) and NYC Tax Lien Sale Lists.