Exclia API
Screen people and organizations against healthcare exclusion lists from your own product.
The Exclia API screens people and organizations against federal and state healthcare exclusion lists — the OIG LEIE, SAM.gov and the state Medicaid lists on the coverage page — and keeps watching them after the first check.
Every endpoint lives under one base URL:
https://api.exclia.com/v1What you can do
| Endpoint | What it does |
|---|---|
POST /screen | Screen one person or organization and get the answer in the response. |
POST /batch | Submit many entities at once and poll for the results. |
PUT /monitor | Enroll an entity in continuous monitoring. It is re-screened whenever a covered list publishes a new version. |
DELETE /monitor/{id} | Stop monitoring an entity. |
GET /lists | Every source we screen against, with its current list version and retrieval date. |
GET /usage | This billing period's metered usage, priced. |
How results are worded
A result is clear or potential_match. The API never returns an automated "excluded" verdict about a person: a potential match carries the evidence (which fields matched, and how) and the provenance (which list version, retrieved when), and a person at your organization verifies it. Every match carries the same label at every score.
Start here
- Quickstart — your first successful call in under five minutes.
- Authentication — API keys and permissible use.
- Errors — every status code and what to do about it.
- Webhooks — signed deliveries when a status changes.
For coding agents
The whole contract is machine-readable. Point your agent at one of these:
/docs/openapi.json— the OpenAPI 3.0 document, generated from the same schemas the API validates with./llms.txt— an index of these docs./llms-full.txt— every guide in one Markdown file.