API Endpoint: List Sanctions

The list-sanctions endpoint screens a name against more than 330 global sanctions and watchlists.

POST /api/v1/validate/list-sanctions

https://www.tincomply.com/api/v1/validate/list-sanctions

Screens a person or business name against more than 330 sanctions and watchlists, including OFAC SDN, the Consolidated Screening List, SAM exclusions, FinCEN, BIS, EU and UN, with fuzzy matching and alias detection. Hits below your account's match threshold are filtered out.

Request body

FieldTypeDescription
namerequired string The person or business name to screen.

Response object: listSanctionsMatchResult

FieldTypeDescription
resultsarrayHits, omitted when there are none. Each item has name, type, confidence, list (the source list), properties, related and relationships.
anyFilteredboolTrue when the name matched an entry that appears only on lists your account does not have enabled. Those hits are left out of results.
completedboolFalse when the upstream source was unavailable. The request is retried automatically; call request-details with the request id later to get the finished result.

A hit is a lead for review, not a determination. Compare the list source and the returned identifiers (aliases, addresses, IDs) against your record before acting.

What to do with this result

When you seeDo this
No resultsClear. Keep the request id as evidence of the screening.
anyFiltered is trueThe name is on a list your account does not screen against. If that list matters to your program, enable it in the portal and screen again.
One or more resultsHold the payment or onboarding and review each hit: the list it came from, aliases, addresses and identifiers.
A hit you confirm is the same partyDo not pay. Escalate to your compliance officer; OFAC and other regimes have their own blocking and reporting rules.
completed is falseThe source was unavailable. Keep the request id and call request-details later; the result fills in once the retry succeeds.

Sample request

curl -X POST https://www.tincomply.com/api/v1/validate/list-sanctions \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"INTERNATIONAL BUSINESS MACHINES"}'

Sample response

{
  "id": "Wm3nB5vC7xZ9aS1dF2gH4jK6",
  "request": {
    "name": "INTERNATIONAL BUSINESS MACHINES",
    "requestDate": "2026-10-01T14:02:11Z",
    "requestedServices": "list-sanctions"
  },
  "listSanctionsMatchResult": {
    "completed": true,
    "anyFiltered": false,
    "results": [
      {
        "name": "INTERNATIONAL BUSINESS MACHINES",
        "type": "Organization",
        "confidence": 75,
        "list": "Business Identifier Code (BIC) Reference Data",
        "properties": {
          "names": "INTERNATIONAL BUSINESS MACHINES",
          "sWIFTBIC": "IBMXUS33",
          "country": "United States"
        },
        "related": [],
        "relationships": []
      }
    ]
  }
}

Errors

Requests that cannot be processed return HTTP 400 with an object keyed by field name, each listing what was wrong. Authentication, permission and other status codes are covered in Errors & service status.

This endpoint requires an API key with the Validate permission.

See how this check works in the portal and what it costs: Sanctions & OFAC Screening