CO UCC Filings - Secured Lien & Debtor Search avatar

CO UCC Filings - Secured Lien & Debtor Search

Pricing

$0.10 / 1,000 co ucc debtor records

Go to Apify Store
CO UCC Filings - Secured Lien & Debtor Search

CO UCC Filings - Secured Lien & Debtor Search

Colorado UCC financing-statement register (public open data, 2.0M debtor records): the public record of secured claims on a business or person - debtor name and address, organization type and jurisdiction, the filing action (add / change / delete) and the record status.

Pricing

$0.10 / 1,000 co ucc debtor records

Rating

0.0

(0)

Developer

Wenhao Yang

Wenhao Yang

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

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,015,388 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,981,929), change only (26,522), delete only (6,855), change and delete (82) - the amendment history of a statement
  • the record status - active (1,977,469) / 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,887,677, 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

InputWhat it does
moderows (default) / aggregate
debtororganization or person name substring
fileId / debtorId / efsUniqueIdexact identifiers
debtorTypeorganization / individual
actionType / recordStatusadd / change / delete; active / inactive
city / state / countrydebtor location
organizationJurisdiction / organizationTypeentity jurisdiction and type
groupByaggregate over state / country / action / status / org type / jurisdiction
maxResultscap records (default 200)

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

Low cost

From $0.0001 per record - billed only for the rows you use, at the platform floor. Cost scales with what you pull, not with the size of the register, and because each record is metered individually there's no per-run charge cap to hit on a big pull.

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.

Source