UCC Filing Radar: Fresh CT + CO UCC Leads by Funders You Watch

UCC Filing Radar watches the secured parties (funders) you name and delivers new UCC filings that list them as the secured party. It reads each state's official Secretary of State open-data feed, keeps a per-watch memory so you never see the same filing twice, and returns flat rows you can schedule, download, or pipe through the Apify API. Two states are covered today: Connecticut and Colorado.

This is a standing funder-watch, not a bulk export. You name the funders to track and it returns the businesses they just filed against: funder-qualified UCC leads instead of an aged bulk list.

What does UCC Filing Radar do?

Every run pulls a recent date window from the state you choose, keeps only the filings whose secured party matches one of the funder names you watch, removes any filing this watch has already delivered, and returns the rest as dataset rows. An optional webhook receives the same new filings for alerting.

• Connecticut reads the public UCC Lien Filings dataset (Connecticut Secretary of the State). It is one denormalized table, so each row already carries the debtor, the secured party, the filing type, and the acceptance date. No join.
• Colorado reads the filing dataset plus the secured-party and debtor datasets (Colorado Secretary of State) and joins them on the file id for you.

There is no login and no proxy. During testing the newest Connecticut filing in the feed was about one business day old and the newest Colorado filing about two business days old, so a daily schedule surfaces recent filings in most cases. Neither feed publishes over weekends and holidays, so the default lookback window covers those gaps.

Why use UCC Filing Radar?

• Track named funders across states. Equipment lenders, powersports and marine financiers, and other secured parties file UCC-1s when they fund a business. Watching a funder's new filings is a read on where that funder is active. Run the same funder list against Connecticut and Colorado to watch that funder in both states.
• Own the timing. The filing is public once the state posts it. This actor delivers that window on your own schedule.
• No duplicates. Each watch remembers what it has already delivered, so an overlapping window costs you nothing and repeats nothing.
• Public record. UCC filings are public records published by each state's Secretary of State.

How to use UCC Filing Radar

1. In the Input tab, list the funders you want to watch under Secured parties to watch (for example Sheffield Financial, John Deere, Financial Pacific Leasing).
2. Pick a State (Connecticut or Colorado) and set Filing types for that state (see the tables below). The defaults are UCC-1 originations.
3. Run it once to preview the matches. Set Dry run to true first if you want a no-charge preview of up to five rows.
4. Create a daily Schedule for the actor. Each scheduled run delivers only filings you have not seen before, so a daily cadence with the default 3-day lookback covers weekends and holidays.
5. Optionally set a Webhook URL to receive each run's new filings as a POST.

Give each distinct funder list its own Watch name so its deduplication memory stays separate. A watch is per state: the same watch name run against Connecticut and against Colorado are two separate watches with separate memory and separate billing.

Input

Field	Required	Default	Description
securedPartyNames	Yes	none	1 to 50 funder names to watch. Case and punctuation insensitive substring match, each name at least 3 characters.
state	No	CT	CT (Connecticut) or CO (Colorado).
filingTypes	No	["ORIG FIN STMT"] (CT) / ["Initial Filing"] (CO)	Filing types to include, or the single value ALL. State-native (see the tables below).
lookbackDays	No	3	Days back from today (America/New_York) to query, 1 to 14.
debtorCities	No	none	Optional list of debtor cities to keep, up to 25.
webhookUrl	No	none	Optional https URL that receives new matches as a POST.
watchName	No	default	Names this watch so its dedupe memory persists across runs.
dryRun	No	false	Preview up to 5 rows, charge nothing, write no watch memory.

Filing types by state

Connecticut (matched against cd_flng_type), common values:

Value	Meaning
ORIG FIN STMT	UCC-1 origination (the default)
AMENDMENT	Amendment
CONTINUATION	Continuation
ASSIGNMENT	Assignment
RELEASE ORIG	Release
TERMINATION	Termination
ALL	Every filing type

Colorado (matched against transactiontype, case-insensitive), the complete list:

Value	Meaning
Initial Filing	New filing (the default)
Amendment	Amendment
Filing Officer Correction	Correction made by the filing officer
Correction	Correction
ALL	Every transaction type

A filing type from the wrong state's list is rejected before anything is charged, with a message naming the state.

Output

Each new filing is one flat dataset row. You can download the dataset in JSON, HTML, CSV, or Excel.

A Connecticut row:

{
    "filingNumber": "0005393671",
    "lienFilingNumber": "0005393671",
    "filingType": "ORIG FIN STMT",
    "filingTypeDetail": "OFS",
    "lienStatus": "Active",
    "acceptedDate": "2026-07-04",
    "lapseDate": "2031-07-04",
    "debtorName": "PEACH, COLLIN",
    "debtorStreet": "20 KELLOGG RD",
    "debtorCity": "MARLBOROUGH",
    "debtorState": "CT",
    "debtorZip": "06447",
    "securedPartyName": "Sheffield Financial, A Division of Branch Banking and Trust Company",
    "securedPartyStreet": "PO Box 1704",
    "securedPartyCity": "Clemmons",
    "securedPartyState": "NC",
    "securedPartyZip": "27012",
    "matchedNames": ["Sheffield Financial"],
    "state": "CT",
    "watchName": "default",
    "billing": "included",
    "source": "https://data.ct.gov/resource/xfev-8smz.json",
    "fileId": null
}

A Colorado row (same field names; filingNumber is the transaction id, fileId is the state file id, lienStatus and lienFilingNumber are null because Colorado does not publish them per filing):

{
    "filingNumber": "20262065620",
    "lienFilingNumber": null,
    "filingType": "Initial Filing",
    "filingTypeDetail": "UCC financing statement",
    "lienStatus": null,
    "acceptedDate": "2026-07-03",
    "lapseDate": "2031-07-03",
    "debtorName": "ENERGY 2 GO LTD",
    "debtorStreet": null,
    "debtorCity": "AURORA",
    "debtorState": "CO",
    "debtorZip": null,
    "securedPartyName": "Financial Pacific Leasing, Inc.",
    "securedPartyStreet": null,
    "securedPartyCity": "FEDERAL WAY",
    "securedPartyState": "WA",
    "securedPartyZip": null,
    "matchedNames": ["Financial Pacific Leasing"],
    "state": "CO",
    "watchName": "default",
    "billing": "included",
    "source": "https://data.colorado.gov/resource/wffy-3uut.json",
    "fileId": "2571973"
}

A Colorado input example:

{
    "securedPartyNames": ["Snap-on Credit", "Financial Pacific Leasing"],
    "state": "CO",
    "filingTypes": ["Initial Filing"],
    "lookbackDays": 3
}

When you choose Colorado, either leave filingTypes empty to get Colorado's default (Initial Filing) or set it to Colorado values from the table above. Connecticut values such as ORIG FIN STMT are rejected for Colorado, with a message naming the state.

A summary record is also written to the run's key-value store under OUTPUT with counts for the run: state, new matches, delivered rows, any rows withheld at your charge limit, the seen-set size, the feed's newest filing date, the feed lag in days, and (for Colorado) the feed's Last-Modified timestamp.

Data fields

Field	Meaning
filingNumber	The dedupe key: Connecticut's UCC filing number, or Colorado's transaction id.
lienFilingNumber	Connecticut's published lien filing number. Null for Colorado.
filingType	Connecticut cd_flng_type (for example ORIG FIN STMT) or Colorado transactiontype (for example Initial Filing).
filingTypeDetail	Connecticut's filing-type description code, or Colorado's document type.
lienStatus	Connecticut lien status (for example Active). Null for Colorado, which publishes status per party action rather than per filing.
acceptedDate	Date the state posted the filing (YYYY-MM-DD).
lapseDate	Lapse date, or null.
debtorName	Debtor business name, or the individual debtor name.
debtorStreet, debtorCity, debtorState, debtorZip	Debtor address.
securedPartyName	The secured party (funder) that matched.
securedPartyStreet, securedPartyCity, securedPartyState, securedPartyZip	Secured party address.
matchedNames	Which of your watched names matched this filing.
state	CT or CO.
watchName	The watch this row belongs to.
billing	included, overflow, or dry-run.
source	The source dataset URL, on every row.
fileId	Colorado's file id (the join key). Null on Connecticut rows.

Demo datasets

Two public datasets show real, unedited output from smoke runs of this actor (UCC filings are public records published by the state):

• Connecticut: ucc-radar-demo (13 filings matched from a three-funder watch)
• Colorado: ucc-radar-co-demo (14 filings matched from a two-funder watch, July 2026)

Pricing

The actor is billed per event.

• Monthly watch fee: 19.00 USD per watch, which includes the first 25 delivered filings that month. A watch is per state, so watching the same funders in Connecticut and in Colorado is two watches at 19.00 USD each.
• Overflow: 0.40 USD per delivered filing beyond the first 25 in a month, per watch.
• First calendar month free. The watch fee is waived during your account's first calendar month, so an initial run to try it out costs nothing while your matches stay within the 25 included filings. The free month is per account and covers your Connecticut and Colorado watches alike.

A dry run charges nothing. A run that cannot complete its query charges nothing. A run against a feed that has not updated in more than 7 days delivers what it finds but does not bill the watch fee. Filings withheld because you hit your run's max-charge limit are not billed and are redelivered on the next run.

Tips and advanced options

• Run daily on a Schedule. The default 3-day lookback covers weekends and holidays; overlap is free because filings you have already received are deduplicated.
• Use the same watchName across scheduled runs so the dedupe memory persists. Use different watchName values for different funder lists.
• To watch both states, run two schedules with the same funder list: one with state = CT, one with state = CO.
• Set a per-run max-charge limit if you want a hard ceiling. If a run hits it mid-delivery, the withheld filings are not billed and return on the next run.
• Use dryRun to check your funder spellings before scheduling. Matching is a substring test, so Sheffield Financial matches Sheffield Financial, A Division of Branch Banking and Trust Company.
• Narrow with debtorCities when you only want filings against debtors in specific towns.

FAQ, limitations, and support

• Is this data legal to use? UCC filings are public records published by each state's Secretary of State. This actor reads the states' own open-data feeds.
• Which states are covered? Connecticut and Colorado today. The output fields and events are built so additional states can be added later without changing them.
• How fresh is it? In testing Connecticut ran about one business day behind the Secretary of the State and Colorado about two business days behind. Colorado's secured-party dataset can lag its filing dataset within a day, so a very new Colorado filing may deliver on a later run once its funder resolves. That is why the default lookback re-checks recent days.
• Are source-document images or collateral descriptions included? No. The feeds do not publish a document link or a collateral text field, so those are not in the output.
• How reliable is the webhook? It is best-effort alerting with retries. The dataset is the durable record. If you need to verify the caller, put a secret token in your webhook URL.
• What happens if a feed changes shape? The actor checks the feed's structure on every run and stops without charging if a field it depends on is missing, rather than delivering broken rows.

For issues or a custom variant, use the Issues tab on the actor page.