UCC Lien Search avatar

UCC Lien Search

Under maintenance

Pricing

Pay per usage

Go to Apify Store
UCC Lien Search

UCC Lien Search

Under maintenance

Search official state UCC lien sources and write normalized debtor filing rows to the default dataset. The Actor wraps the UCC Lien Search API for lending, KYC, collateral, and M&A diligence workflows.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

jts

jts

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

5 days ago

Last modified

Share

What this Actor does

Search official state UCC lien sources and write normalized debtor filing rows to the default dataset. The Actor wraps the UCC Lien Search API for lending, KYC, collateral, and M&A diligence workflows.

Input example

{
"state": "FL"
}

Input fields

Provide debtor names or lookup objects to search with the UCC Lien Search API.

  • liens (array, user input): Array of strings or objects with { debtor, state, entityType?, exact?, filedAfter?, expiringBefore?, securedParty? }.
  • state (string, user input): Default state code applied to string lien searches. Use FL for the live v1 adapter.
  • apiBaseUrl (string, optional override): Override of the upstream API base URL. Defaults to runtime.baseUrl from service.json.

Output dataset

Each dataset item is one normalized UCC filing row or lookup summary.

  • input: Original UCC lien lookup input.
  • normalized: Normalized query summary.
  • filingId: Official UCC filing identifier.
  • jurisdiction: State code searched.
  • debtorName: Debtor name returned by the source.
  • collateralType: Normalized collateral category.
  • status: Normalized filing status.
  • totalMatches: Number of rows in the lookup response.
  • confidence: Confidence in the normalized response.

Developer notes

Set UCC_LIEN_SEARCH_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API. Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json. For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.

Run locally

$apify run

Deploy

$apify push