Search sanctions with JSON

Contract for POST /public/search.

Request API access Sign in

POST/public/search

Recommended for multiple identifiers, multiple source filters or a structured JSON request.

Authentication

Use the x-api-key header when possible; Authorization: ApiKey is also supported.

Parameters

No path or query parameters.

Request body

SearchQuery

{
  "name": "Example Person",
  "type": "person",
  "birthDate": "1980-05-12",
  "country": "TR",
  "identifiers": [
    {
      "type": "passport",
      "value": "AA123456"
    }
  ],
  "pageSize": 10
}

Responses

HTTP	Description	Schema
`200`	Successful response	SearchResponse
`400`	Invalid or missing request data	ErrorResponse
`401`	Authentication is missing or invalid	ErrorResponse
`403`	Account, permission, source scope, domain or IP restriction failed	ErrorResponse
`429`	Usage, rate or page size limit exceeded	ErrorResponse
`500`	Server error	ErrorResponse
`503`	Temporary service dependency failure	ErrorResponse

Code examples

curl -X POST "https://api.sanctions.tr/public/search" \
  -H "content-type: application/json" \
  -H "x-api-key: $SANCTIONS_API_KEY" \
  -d '{"name":"AEROCARIBBEAN AIRLINES","sources":["OFAC"],"pageSize":5}'

Decision boundary

An API result is a candidate match. A final sanctions or compliance decision requires official-source verification and human review.