Search request

Review search fields, source scope and pagination behavior.

GET /public/search accepts query parameters and POST /public/search accepts a JSON body. Both normalize to the same search contract.

Required field

name is a 2–160 character person, organization, vessel, aircraft or known alias name.

Optional context

type: person, company, vessel, aircraft, other
gender, birthDate, nationality, country
source or sources
identifier for GET or up to 20 identifiers for POST
One-based page and policy-capped pageSize

Canonical sources

Use OFAC, MASAK, EU_RESTRICTED, UK_HMT and UN_CONSOLIDATED. Aliases such as EU, UK and UN are normalized to canonical values.

Identifier example

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

Do not send unnecessary personal data. Include only fields that materially improve candidate separation.

Decision boundary

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