The exclusions information is public, but the documented SAM.gov Exclusions API requires an API key. Those are different things: the key identifies and validates API users; it does not mean the public exclusions dataset is private. You can search exclusions in SAM.gov, query the API, or use documented public extracts, depending on how much data you need and how you plan to process it.
Why does the SAM.gov exclusions API require a key if the list is public?
“Public” describes the information and the public extract. “Key-gated” describes the documented programmatic endpoint. GSA says the Exclusions API provides public exclusion information using optional request parameters, and its v4 production endpoint requires an API key: https://api.sam.gov/entity-information/v4/exclusions?api_key=<value>. Request a personal key through a registered SAM.gov account. GSA’s Exclusions API documentation explains the endpoint and access requirements.
As an Amazon Associate I earn from qualifying purchases.
The key is for API access and user validation; it is not evidence that the API provides access to restricted data. SAM.gov also offers a browser search and public data services. Some registrant information requires federal sign-in, so public access to exclusions information does not mean every item or service on the site is available without authentication. See SAM.gov’s Entity Information page.
Which way should you retrieve exclusions information?
| Route | Best fit | Behavior and limits | Access |
|---|---|---|---|
| SAM.gov browser search | One-off lookups and manual filtering | Search filters include classification, exclusion type, program, location, and dates. | Public search is available; some registrant information requires federal sign-in. |
| Exclusions API v4 | Specific queries in an application or script | Paginated JSON; 10 records per page and a documented ceiling of 10,000 records. | Registered SAM.gov user and API key; daily request limits depend on account category. |
| Exclusions API extract mode | Larger filtered downloads for local processing | Asynchronous JSON or CSV generation; documented ceiling of 1,000,000 records. | Uses the API and requires a key; generation may take time. |
| Public exclusions bulk extract | Repeated or broad processing of the public list | Daily public extract of parties with currently active exclusions. | Use documented SAM.gov/GSA data services; the extracts API requires an account and API key for public extract requests. |
The right route depends on query specificity, result volume, how often you need refreshed data, your processing workflow, and the request limit for your account category. “Public extract” does not mean every download mechanism is credential-free.
#1 Best Overall
How to query the API or request a larger extract
Use paginated JSON for targeted queries
The production API is version 4. GSA documents ten records per page and a 10,000-record ceiling for the standard paginated response. Optional parameters and q expressions support searches involving terms such as classification, geography, exclusion type, agency, and FASCSA order. The query syntax has restrictions; for example, the documentation limits how q handles null, not-null, and NOT searches. Check the current parameter table before relying on a particular expression. The same documentation provides production and alpha endpoint forms; use production for live work and alpha for testing when appropriate. See the v4 API reference.
Use asynchronous extract mode for larger results
Adding the documented format parameter switches the API to asynchronous file generation. The available formats are JSON and CSV, with a documented ceiling of 1,000,000 records. The response provides a file URL or can trigger an email notification. File generation may still be pending when you check; the download flow uses a token, and a token can be invalid or expire. Follow the current API documentation for the request, status-check, and download steps rather than treating the initial response as an immediately available file.
Use the daily public extract for recurring broad processing
GSA describes the public exclusions extract as a list of publicly available parties with currently active exclusions in SAM.gov, and says daily exclusion extracts are produced every day. The separate extracts download API documents a daily ZIP containing a CSV, named SAM_Exclusions_Public_Extract_V2_YYDDD.ZIP, where YYDDD is the Julian date. Its documentation says to check after 7 a.m. Eastern; that is a documented schedule, not a guarantee that a specific file will be available at an exact time. Consult GSA’s extracts documentation for the current access process and SAM.gov’s Exclusions Public V2 listing for listed files.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesWhat API limits apply?
GSA’s Exclusions API documentation lists default daily request limits by account category. These are requests per day, not records per day:
| Account category | Default requests per day |
|---|---|
| Non-federal user with no SAM.gov role and a personal key | 10 |
| Several personal-key and non-federal system-account categories | 1,000 |
| Federal system accounts | 10,000 |
The 1,000-request default covers several categories, not every account. Check the current account-category table in GSA’s API documentation to identify the limit that applies to your key. These request limits are separate from the API’s record ceilings: ten records per page and 10,000 records for standard paginated results, or up to 1,000,000 records in extract mode.
What should you do about the “Exclusions API Update” notice?
SAM.gov’s notice titled “Exclusions API Update,” subtitled “Change is Coming for SAM.gov Exclusions APIs,” was last updated August 11, 2026. The notice page does not state what is changing or when it takes effect. Do not infer a new endpoint, key policy, or deadline from the title alone. Check the SAM.gov announcement and current GSA API documentation before changing an integration.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why scraping is not a workaround
SAM.gov’s terms prohibit automated scraping and gathering tools and direct users to documented APIs and downloads. Use only authorized data and documented access methods; do not share an individual API key or use a SAM.gov login for data mining or automated gathering. SAM.gov also says that only data from public API versions should be shared publicly. See the SAM.gov Terms of Use.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
