Colorado UCC Filings - Secured Lien & Debtor Search

When a lender takes a security interest in a business - equipment financing, inventory, receivables - it files a UCC financing statement with the Colorado Secretary of State. Those filings are public, and they are published as open data. This actor turns that register into a charged-per-record search, filter and aggregate tool: find a debtor by name, pull the filings on a single statement, filter by action or status, or aggregate the register.

Built for: lenders and credit analysts checking who else has a claim on a debtor, M&A and asset-based diligence, and anyone who wants the public lien record on a business without paging a state portal one name at a time.

What it covers

~2.02M debtor records - the state's full UCC register, across 1,599,600 financing statements (a statement can name several debtors, so one filing can return more than one row).

Depth beyond a bare name list:

• the filing's action - add (~1.99M), change only (26,522), delete only (6,855), change and delete (82) - the amendment history of a statement
• the record status - active (~1.98M) / inactive (37,919)
• the debtor identity, either an organization (name, jurisdiction, type, organization id) or a natural person (last / first / middle name, suffix) - the two are mutually exclusive
• the debtor's full address - street, city, state (CO ~1.89M, CA, TX, ...), country and zip

The fine print that matters

This register carries no date column at all. The recency axis is the monotonic file id (newest filing first), and the freshness guard reads the dataset's own update stamp rather than a row field - so a newest-first pull still tracks the live edge without a date to sort on.

Also worth knowing: a file id is not a debtor. The id names the statement; the register lists every debtor on it, so fileId can legitimately return more than one record. And a debtor is either an organization or a natural person, never both - the actor keeps both key sets on every record (empty-filled) so the output shape never shifts.

Typical questions

• "Every UCC filing naming a given business."
• "The debtors on one financing statement (file id)."
• "Active filings against debtors in Denver."
• "Amendments and terminations (change / delete) on a statement."
• "Aggregate the register by state, organization type or action."

Inputs

Input	What it does
mode	rows (default) / aggregate
debtor	organization or person name substring
fileId / debtorId / efsUniqueId	exact identifiers
debtorType	organization / individual
actionType / recordStatus	add / change / delete; active / inactive
city / state / country	debtor location
organizationJurisdiction / organizationType	entity jurisdiction and type
groupBy	aggregate over state / country / action / status / org type / jurisdiction
maxResults	cap records (default 50)

Default run = the 50 most recent debtor records - fast for the daily auto-test. For a targeted query add a filter; for a broad view use aggregate.

Example inputs

Everything filed against a business - debtor is a substring match on the organization name or any part of a natural person's name.

{ "debtor": "CHEVROLET", "maxResults": 5 }

One financing statement - fileId names the statement, and a statement can name several debtors, so more than one row can come back.

{ "fileId": "2559898", "maxResults": 5 }

Active liens against Denver debtors

{ "city": "Denver", "state": "CO", "recordStatus": "active", "maxResults": 5 }

How the register splits by action - one row per actionType.

{ "mode": "aggregate", "groupBy": "actionType" }

Low cost

From $0.00005 per record, down to $0.00003 at Gold - billed only for the rows you use, at the low end of the store. Cost scales with what you pull, not with the size of the register, and each record is metered individually.

What a thin scraper misses is the filing structure: a UCC record is not a name in a list, it is a debtor on a statement that can be amended and terminated over time - the register carries the action (add / change / delete) and the status, and the id you search on names the statement, not the debtor. The register also has no date column to sort by, so a naive newest-first pull either fails or drifts, and a debtor is either an organization or a natural person, two different shapes behind one record. Normalizing the statement-vs-debtor grain, the amendment action and the two debtor shapes into a schema where a debtor / state / recordStatus query returns exactly the filings you mean is the actual product. Every pull is integrity-checked against the register's known shape, so a degraded source fails loudly instead of returning bad rows.

Example output

One debtor - fileId=2559898 returns this debtor row (the statement can name more than one):

{
  "platform": "co-ucc-filings",
  "source": "colorado-ucc-debtors",
  "mode": "rows",
  "groupKey": "",
  "groupCount": "",
  "groupBy": "",
  "recordId": "1994308",
  "fileId": "2559898",
  "efsUniqueId": "",
  "actionTypeCode": "A",
  "actionType": "add",
  "actionReferenceId": "",
  "recordStatusCode": "A",
  "recordStatus": "active",
  "debtorDescription": "",
  "debtorType": "organization",
  "lastName": "",
  "firstName": "",
  "middleName": "",
  "suffix": "",
  "organizationName": "COOK CHEVROLET, INC.",
  "organizationJurisdiction": "",
  "organizationType": "",
  "organizationId": "",
  "address1": "1955 CURVE CT",
  "address2": "",
  "city": "STEAMBOAT SPRINGS",
  "state": "CO",
  "country": "United States",
  "zipCode": "80487",
  "zipCode4": "",
  "sourceUpdatedAt": "2026-09-23"
}

mode=aggregate, groupBy=actionType - one row per group:

add                  ~1.99M
change only             26,522
delete only              6,855
change and delete           82

Source

• Colorado: Uniform Commercial Code (UCC) Debtor Information - the Secretary of State's UCC debtor register. Public open data. Records are the state's own published fields; not legal advice, and a filing is not a determination of any obligation.