SAM.gov Entity Exclusions Scraper avatar

SAM.gov Entity Exclusions Scraper

Pricing

Pay per event

Go to Apify Store
SAM.gov Entity Exclusions Scraper

SAM.gov Entity Exclusions Scraper

Extract public SAM.gov exclusion records for vendor screening, debarment monitoring, and procurement compliance workflows.

Pricing

Pay per event

Rating

0.0

(0)

Developer

Stas Persiianenko

Stas Persiianenko

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

What does SAM.gov Entity Exclusions Scraper do?

SAM.gov Entity Exclusions Scraper extracts public exclusion records from SAM.gov and turns them into structured rows. Use it to screen vendors, subcontractors, grant recipients, or business partners for active and historical exclusion records. The actor reads the public SAM.gov search API and saves normalized fields such as entity name, UEI, CAGE code, program, type, excluding agency, status, dates, address, and source URLs.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Who is it for?

Procurement teams can check suppliers before award. Government contractors can screen subcontractors before bid submission. Compliance teams can monitor excluded parties. Vendor-risk teams can enrich onboarding workflows. Data providers can add SAM.gov exclusion status to business datasets.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Why use it?

The SAM.gov website is useful for manual searches, but repeatable screening requires structured output. This actor gives you API-ready JSON, CSV, Excel, or dataset exports that can be scheduled, monitored, and integrated with risk systems.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

What data can you extract?

Each dataset item represents one SAM.gov exclusion record. Fields include identifiers, exclusion status, exclusion program, exclusion type, excluding agency, activation date, termination date, address, SAM source URL, API URL, scrape timestamp, and optional raw metadata.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

How much does it cost to scrape SAM.gov exclusions?

The actor uses pay-per-event pricing. There is a small start fee and a per-record charge for each exclusion record saved. Exact live prices are shown on the Apify Store before you run the actor.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

How to scrape SAM.gov exclusions

Enter a keyword, UEI, CAGE code, or entity name, choose active, inactive, or all records, set the maximum number of records, and run the actor. Results appear in the default dataset.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Input options

Use query for entity search. Use activeStatus for active, inactive, or all records. Optional arrays let you keep only selected agencies, programs, types, countries, or US states. maxItems controls cost and output size.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Output fields

Important output fields are entityName, uei, cageCode, samNumber, isActive, exclusionProgram, exclusionType, excludingAgency, activationDate, terminationDate, address fields, samSearchUrl, sourceApiUrl, scrapedAt, and optional raw.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Example input

{
"query": "DYNAMIC MINDS",
"activeStatus": "active",
"maxItems": 100,
"pageSize": 100
}
  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Example output

{
"entityName": "DYNAMIC MINDS FAMILY SERVICES",
"uei": "MGS1EPM43F23",
"isActive": true,
"exclusionProgram": "Reciprocal",
"excludingAgency": "OPM",
"addressState": "NV"
}
  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Tips for reliable results

Start with active exclusions and a small maxItems value. Use a keyword or identifier when you need a targeted entity check. Use includeRaw only when your audit workflow needs the original SAM.gov metadata.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Integrations

Schedule the actor daily to monitor active exclusions. Export datasets to Google Sheets, S3, webhooks, or your vendor master database. Trigger it from procurement onboarding when a new supplier is created.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

API usage with Node.js

import { ApifyClient } from "apify-client";
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor("automation-lab/sam-gov-entity-exclusions-scraper").call({ query: "DYNAMIC MINDS", activeStatus: "active", maxItems: 100 });
console.log(run.defaultDatasetId);
  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

API usage with Python

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("automation-lab/sam-gov-entity-exclusions-scraper").call(run_input={"query":"DYNAMIC MINDS","activeStatus":"active","maxItems":100})
print(run["defaultDatasetId"])
  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~sam-gov-entity-exclusions-scraper/runs?token=$APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{"query":"DYNAMIC MINDS","activeStatus":"active","maxItems":100}'
  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

MCP integration

Use this actor from Claude Code or Claude Desktop through the Apify MCP server.

Add it in Claude Code:

$claude mcp add apify-sam-exclusions https://mcp.apify.com/?tools=automation-lab/sam-gov-entity-exclusions-scraper

Claude Desktop JSON config:

{
"mcpServers": {
"apify-sam-exclusions": {
"url": "https://mcp.apify.com/?tools=automation-lab/sam-gov-entity-exclusions-scraper"
}
}
}

Example prompts:

  • “Check this vendor against active SAM.gov exclusions and summarize the risk evidence.”

  • “Run a SAM.gov exclusions scraper search for this UEI and return the agency, dates, and source URL.”

  • “Create a vendor-risk watchlist export for active USA exclusions.”

  • ✅ Structured SAM.gov exclusion records

  • ✅ Active, inactive, or all-status workflows

  • ✅ Compliance-friendly identifiers and source URLs

Legality and responsible use

SAM.gov exclusion records are public government data. You are responsible for using results lawfully, respecting internal compliance policies, and verifying critical decisions against official SAM.gov records when needed.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Related Automation Lab actors include https://apify.com/automation-lab/samgov-government-contracts-scraper, https://apify.com/automation-lab/ofac-sanctions-list-export-scraper, and other procurement or sanctions data actors.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

FAQ

Can I scrape inactive exclusions? Yes, set activeStatus to inactive or all. Can I filter by agency? Yes, use agencies such as OPM; filtering is applied to returned records. Why are some fields empty? SAM.gov records vary and not every entity has a CAGE code, termination date, or full address.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Troubleshooting

If you receive fewer records than expected, remove optional filters or increase maxItems. If a targeted entity is missing, try searching by UEI, CAGE code, or a shorter name keyword.

  • ✅ Structured SAM.gov exclusion records
  • ✅ Active, inactive, or all-status workflows
  • ✅ Compliance-friendly identifiers and source URLs

Field reference

  • recordId — exported when available from SAM.gov or derived by the actor.
  • entityName — exported when available from SAM.gov or derived by the actor.
  • uei — exported when available from SAM.gov or derived by the actor.
  • cageCode — exported when available from SAM.gov or derived by the actor.
  • samNumber — exported when available from SAM.gov or derived by the actor.
  • isActive — exported when available from SAM.gov or derived by the actor.
  • exclusionProgram — exported when available from SAM.gov or derived by the actor.
  • exclusionType — exported when available from SAM.gov or derived by the actor.
  • typeCode — exported when available from SAM.gov or derived by the actor.
  • excludingAgency — exported when available from SAM.gov or derived by the actor.
  • excludingAgencyDescription — exported when available from SAM.gov or derived by the actor.
  • classification — exported when available from SAM.gov or derived by the actor.
  • activationDate — exported when available from SAM.gov or derived by the actor.
  • terminationDate — exported when available from SAM.gov or derived by the actor.
  • addressStreet — exported when available from SAM.gov or derived by the actor.
  • addressCity — exported when available from SAM.gov or derived by the actor.
  • addressState — exported when available from SAM.gov or derived by the actor.
  • addressZip — exported when available from SAM.gov or derived by the actor.
  • addressCountry — exported when available from SAM.gov or derived by the actor.
  • samSearchUrl — exported when available from SAM.gov or derived by the actor.
  • sourceApiUrl — exported when available from SAM.gov or derived by the actor.
  • scrapedAt — exported when available from SAM.gov or derived by the actor.
  • raw — exported when available from SAM.gov or derived by the actor.

Workflow ideas

  • Workflow 1: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 2: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 3: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 4: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 5: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 6: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 7: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 8: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 9: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 10: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 11: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 12: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 13: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 14: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 15: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 16: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 17: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 18: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 19: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 20: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 21: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 22: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 23: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 24: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 25: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 26: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 27: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 28: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 29: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 30: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 31: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 32: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 33: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 34: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 35: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 36: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 37: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 38: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 39: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.
  • Workflow 40: run targeted SAM.gov exclusion screening, export the dataset, and attach the source URL to your compliance record.