API

Business verification and UCC search API

One REST API for both checks. Send a business name and state, get back JSON with a verdict, the state's record and every lien filing, each with its official source and the date of the data.

curl -H "Authorization: Bearer $CLERKFIELD_KEY" \
  "https://clerkfield.com/v1/business-check?name=Pizza%20and%20Company&state=KY"

{
  "verdict": "pass",
  "matchQuality": "exact",
  "match": {
    "legalName": "PIZZA AND COMPANY",
    "status": "active",
    "formedOn": "1980-07-30",
    "monthsInBusiness": 556
  },
  "flags": []
}

Start in three steps

  1. 01

    Create a free account

    Sign up at clerkfield.com/app. No sales call and no card.

  2. 02

    Create an API key

    Open your profile in the app and create a key. It's shown once, so store it in your secrets manager.

  3. 03

    Call an endpoint

    Send the key as a bearer token in the Authorization header. Every response is JSON.

Endpoints

Base URL ${rec(SITE_URL)}. All endpoints use GET and return JSON. Full parameters, responses and errors are in the API documentation; the machine-readable spec is at /openapi.json.

GET /v1/business-check

Verify a business: Pass, Review or Fail with the reasons, plus the state's record.

GET /v1/liens

UCC filings against a business or filed by a lender, with a summary and full history.

GET /v1/coverage

Every state and what each check covers there. No key needed.

GET /v1/account/me

Check an API key and see the account it belongs to.

Frequently asked questions.

Straight answers. Still have a question?

Talk to us
  • Not yet. The API is plain REST over HTTPS and returns JSON, so any HTTP client works, from curl to your CRM's webhook step.

  • Create a free account, open your profile in the app and create a key. Send it in the Authorization header as a bearer token. The key is shown once, so store it in your secrets manager.

  • Open-data states usually answer in a second or two. States read through their own online search take longer, because Clerkfield makes one request at a time to the state and waits for its answer.

  • The API returns a 502 error that names the state, instead of an empty or stale result. Retry once the state is back online.