Enforcement Ledger Subscribe

Enforcement Ledger: Contractor License Enforcement Records API

Structured disciplinary and enforcement records for licensed contractors, collected from state licensing boards and archived permanently.

Board orders, revocations, suspensions, citations and penalties for licensed contractors across 11 US states, in one structured API. 136,553 enforcement records and growing daily. We archive what state boards publish before it ages off their sites.

Subscribe on RapidAPI Subscribe on api.market
136,553Enforcement records
11States covered
Archived permanently

What this is

State licensing boards publish disciplinary actions and then quietly remove them: several states keep only the last two or three years online. We collect these public records on a schedule, structure them, and keep every record permanently, so an enforcement history is still there when you need it.

An append-only archive of public contractor licensing and enforcement records, collected from state licensing authorities and served read only. The states it covers, and how much of each, are published in the coverage block on /v1/meta. Every endpoint is keyed on a license or registration number together with a state, or on business identifiers, and there is no search by the name of an individual. This archive reports the enforcement actions it has collected and never reports that a licensee is clear: an empty result is not a clearance and not a verification, so read discipline_status and discipline_disclaimer on every license response, and the per state scope strings on /v1/meta, before acting on an absence. Sold for commercial business purposes only; the permitted and prohibited uses, the correction address and the plan quotas are served in full on /v1/meta.

What you get

  • Board orders, license revocations and suspensions, citations, monetary penalties and statute references, keyed by license number and state. 136,553 enforcement records across 11 states today, with license roster records in 7 states behind them so an enforcement action can be looked up.
  • A derived severity reading beside every record, so actions are comparable across states, with the state's own words served unchanged beside it.
  • Coverage stated per state, in the API itself. /v1/meta publishes what each state's collection covers and what it does not, before you pay: two absolute counts and a date per state, never a ratio, plus a plain sentence describing what is monitored there.
  • A published plan block on the same endpoint, so a client learns its quotas from the API rather than from a refusal in production.

What this is not

  • Not license verification and not clearance. An empty result means this archive holds no enforcement action for that license, not that the license was checked and found clean. Every response says so.
  • Not a way to look up people. Every endpoint is keyed on a license or registration number with a state, or on business identifiers. There is no search by a person's name, and none will be added.
  • Not a consumer product. The service is sold to businesses for commercial purposes only.

Coverage

Coverage varies by state and is published per state in /v1/meta and on this page. We state what each state's collection covers rather than implying completeness anywhere.

DepthStatesWhat that means
Deep historyVA, WA, FL, CA, LA, MDMulti-year enforcement history, in Virginia's case a disposition register running from 2000, with statutes, penalties and dates
Current publishing windowTX, MN, AZ, UT, RIThe state publishes a rolling window of roughly two to three years and we keep permanently everything we collect inside it
Roster onlyORLicense roster records and no enforcement: the state's discipline host forbids collection, which is recorded rather than worked around

Counts per state, and the sentence describing what is monitored in each, are served live on /v1/meta.

Use cases

  • Commercial underwriting: read a contracting business's enforcement history before pricing, binding or renewing a commercial policy, bond line or trade credit line.
  • Counterparty due diligence: review a contracting business before awarding work to it, contracting with it or onboarding it.
  • Portfolio risk analytics: measure enforcement exposure across a book, portfolio or network of contracting businesses.
  • Research: academic, journalistic, policy or market research into public enforcement and licensing records.

Plans

Calendar month, UTC. Every counter below resets at 00:00 UTC on the first day of the month.

A disciplinary event counts once per subscriber per calendar month, however many times it is returned. Paging back over records already counted this month does not count them again. Requests that return no disciplinary events count against the call quota only. The marketplace you subscribe through bills on its own monthly period from the day you subscribe; our counters reset on the first of each month, so a subscription started late in a month gets a fresh allotment on the first.

For developers

The interactive reference is at api.enforcementledger.com/docs, built from the OpenAPI schema the API itself publishes. The health endpoint needs no credential; every other endpoint takes the key issued with your plan, in the X-Api-Key header.

curl -H "X-Api-Key: YOUR_KEY" \
  https://api.enforcementledger.com/v1/meta

Corrections and disputes

If you believe a record here misstates what a state published, write to hhonlineventures@proton.me with the license or case identifier. We re-verify the record against the source, correct it where we got it wrong, annotate it where the source itself is unclear or has changed, and reply within 10 business days. This is a voluntary correction process and not a Fair Credit Reporting Act dispute procedure: we are not a consumer reporting agency and these records are not consumer reports.