01 / SOURCE RECORD
US SAM Procurement Exclusions
- Publisher
- General Services Administration
- Source key
- os_us_sam_exclusions
- Entries at capture
- 129,564
- Coverage starts
- 2026-09-04
- Classification
- debarment
Start with the source. Keep the evidence.
Inspect original-publisher sanctions and public-record sources through GDELT Cloud. Understand list coverage, entity connections and how MIT-licensed OpenSanctions crawler code is used.
VERIFIED ENDPOINT EXAMPLEPublisher → source record → resolved entity when supported
Official restricted-party lists
02 / SOURCE RECORD
US Health and Human Services Inspector General Exclusions
- Publisher
- Department of Health and Human Services Office of Inspector General
- Source key
- os_us_hhs_exclusions
- Entries at capture
- 83,487
- Coverage starts
- 2026-09-05
- Classification
- debarment
03 / SOURCE RECORD
US Trade Consolidated Screening List (CSL)
- Publisher
- Department of the Commerce - International Trade Administration
- Source key
- os_us_trade_csl
- Entries at capture
- 26,029
- Coverage starts
- 2026-09-05
- Classification
- screening_list
Use This Data Exact request · JSON · curl · Python · TypeScript
Captured 2026-09-25. These are the exact saved dates and identifiers. Running this request again can return changed results.
GET https://gdeltcloud.com/api/v2/lists: "${GDELT_CLOUD_API_KEY:?Set GDELT_CLOUD_API_KEY}"
curl --fail-with-body --max-time 60 --get 'https://gdeltcloud.com/api/v2/lists' \
--header "Authorization: Bearer $GDELT_CLOUD_API_KEY" \
--header 'Accept: application/json'Pagination: this is one saved page. Follow the response’s pagination contract to retrieve additional pages; each request uses additional QU. Treat incomplete coverage as incomplete, including an empty result.
COLLECTION & INTEGRATION
Original publisher records; OpenSanctions crawler code
GDELT Cloud uses MIT-licensed OpenSanctions crawler code to collect records from original publishers. It does not ingest OpenSanctions’ compiled dataset. The wider public-record lane includes official lists, rosters and other public records; each publisher retains its own attribution and coverage. The restricted-party list catalog shown here is a distinct endpoint listing the sources that its matching surface supports.
How to use it in your workflow
Inspect the list catalog first: read the list identifier, publisher and category. Use supported list-entry and matching endpoints to retrieve relevant evidence, then connect a record to a canonical entity only when the API supplies that identity. A name match alone should be reviewed, not treated as proof.
Review individual publishers and source status in the data directory. The MIT license applies to crawler code; original-publisher data terms remain relevant. See the OpenSanctions code repository for the software license.
OpenSanctions crawler source code and license ↗
Coverage and limitations
This is investigative data, not an audit-grade compliance-screening guarantee. Coverage, update timing and identity resolution vary by publisher. An absent record does not establish that a party is unrestricted; a positive name match does not establish identity. The returned person fields are intentionally limited.
Inventory artifact published 2026-09-25. Aggregate inventory is unmeasured in this publication. Saved responses above retain their own capture dates and returned coverage.