Credentialing & Verification

SAM.gov Exclusion Check Automation

Check a provider or an entity for federal exclusion and debarment on SAM.gov: a clear found or not-found status with exclusion type, classification, and dates back as one structured record. Pure API, no browser session, no screenshot needed, because the API’s own response is the evidence.

This workflowFederal award / exclusion source (SAM.gov)
StatusAvailable today
AccessPublic API
AuthCustomer API key

Overview

What this workflow does

This is the government-wide half of exclusion screening. Where the OIG’s list covers exclusions from federal healthcare programs, SAM.gov records exclusions and debarments across the federal government, and it lists organizations as well as individuals. One run checks one provider or entity and returns the shared screening envelope: a found, not-found, or multiple-matches status, with the match detail attached.

You identify the subject three ways, in order of precision: a SAM UEI for an exact entity match, an NPI, or a first and last name. A not-found run is a successful clean check, on record with a timestamp.

Step by step

How the check actually runs

  1. 01The agent queries the official SAM.gov Exclusions API directly, no browser session involved. Authentication uses the free API key from your organization’s own SAM.gov account, stored in an agent profile and sent with the request; the key is never echoed into the output, the logs, or the reported source URL.
  2. 02It matches by UEI when you have one, by NPI, or by name with the individual classification applied.
  3. 03It classifies the result: no records is a clean not-found; one record is found; several are multiple matches; and an API failure is an explicit error, never a silent pass.
  4. 04For every match it captures the listed name, UEI, exclusion type, the Individual or Firm classification, and the activation and termination dates, normalized to ISO format.
  5. 05It timestamps the check and returns one structured record. The API’s response is the evidence; there’s no portal screen to screenshot and no need for one.

Structured output

What comes back

Every run ends as a record like this in your system, not a portal screenshot someone transcribes. This is the part your team stops doing by hand.

structured output · json
{
"source": "SAM.gov",
"status": "found",
"checked_at": "2026-07-16T14:02:11Z",
"result": {
"excluded": true,
"match_count": 1,
"matches": [
{
"name": "SAMPLE HEALTH SERVICES LLC",
"uei": "ABC•••••••12",
"exclusion_type": "Ineligible (Proceedings Completed)",
"classification": "Firm",
"active_date": "2021-03-04",
"termination_date": "Indefinite"
}
]
},
"source_url": "https://api.sam.gov/entity-information/v4/exclusions?…"
}

Clean on one federal list isn’t clean

The OIG list answers a healthcare question; SAM.gov answers a federal one, and they are different lists with different reasons for someone to be on them. A provider, an owner, or a vendor entity that’s clean on one can appear on the other, which is why screening programs run both, plus the state Medicaid lists, as one pass. Running only the list you’ve always run is a habit with a gap in it, not a screening program.

This check composes directly with the OIG exclusion check for the federal healthcare side, and with the state Medicaid exclusion check for the state layer.

At scale

One check, or the whole roster and vendor file

A single run answers one subject. As a program, the roster runs on the same monthly cadence as the rest of exclusion screening, and because SAM.gov lists firms as well as individuals, the same primitive covers the entities you contract with, not just the providers you employ. Screening is part of the credentialing and verification workflow library.

Human in the loop

What escalates to a human

Runs execute on HIPAA-compliant, SOC 2 Type II infrastructure, and every screening leaves the timestamped trail an auditor asks for first. Full detail on the security page.

Multiple matches on a common name.

All matches are reported with detail; a person confirms identity, or you re-run with the UEI for an exact answer.

A found result.

Exclusion and debarment are contracting and employment decisions. The agent delivers the record; the call is yours.

The API rejecting the key or failing.

After a retry, the run ends as an explicit error, so a check that didn’t happen is never recorded as clean.

Questions

Frequently asked questions

Different list, different scope. The OIG’s LEIE covers exclusions from federal healthcare programs; SAM.gov covers exclusion and debarment government-wide and includes organizations, not just individuals. Someone clean on one can appear on the other, so full screening runs both.

The SAM.gov check is one workflow in the credentialing and verification workflow library. A screening program with a missing list is a gap an auditor can find, and the list you skip is always the one they check.

Disclaimer

Third-party names, including government agencies and registries, are used only to identify systems commonly involved in healthcare operations workflows. Asteroid is not affiliated with, endorsed by, sponsored by, or certified by those third parties unless expressly stated. Workflow availability depends on customer authorization, account permissions, configuration, and applicable system terms.