Skip to main content
POST
Screen a subject

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Body

application/json

Screen one subject on demand. Each successful call is billed once.

entityType
enum<string>
required

Whether the subject is a person or a business.

Available options:
person,
business
name
string
required

Full name / legal name.

Required string length: 1 - 500
dateOfBirth
string | null

Date of birth (any common format; normalised to YYYY-MM-DD). Supplying it dramatically reduces false positives for people.

gender
string | null
incorporationDate
string | null
website
string | null
altNames
string[]
address
ScreeningAddressInput · object | null

A structured address; flattened to one line before screening.

email
string | null
phone
string | null
governmentIds
string[]
externalRef
string | null
Maximum string length: 255

Response

The screening result. This example shows a review — a real match that a human must confirm, and the shape most genuine hits arrive in. The topScore shown is illustrative: do not assert on it, and do not infer a threshold from it (see the endpoint description).

status_code
integer
required

HTTP status code for the response.

data
ScreeningCheckRead · object
required

Payload or error details.

query_generated_time
integer
required

UTC timestamp (milliseconds since epoch) when response was generated.