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.
Go-live in as little as 30 minPublic APICustomer API key
We map your process, volume, and exception paths, then recommend a practical first scope.
Building internally? Read the docs →
Overview
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.
How Asteroid runs this workflow
A provider or entity record arrives with your organization's own API key, Asteroid queries the SAM.gov Exclusions API, resolves the identity, and returns the classified record to your roster, with possible matches and incomplete identifiers routed to a person rather than decided by the agent.
How it actually runs
A provider or entity record and an authorized SAM.gov API key are supplied
Delivered to your roster
The entity match with any active exclusion detail lands in the roster with its timestamp, covering the firms you contract with as well as the providers you employ, on the same monthly cadence as the rest of screening.
Possible match or incomplete identifier: Every candidate returns with UEI, classification, and dates attached; a person confirms identity once, or re-runs with the UEI for an exact answer.
Closing the loop
Nobody on your team reads this JSON. Your system does. Each run delivers its record wherever the work already lives, and the loop closes on its own: requests in, records back, no one in the middle.
▸ run triggered · request received from your system▸ agent working the source…{ "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?…"}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
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
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
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.
We use cookies for analytics and advertising. You can opt out or manage your choices anytime.