Behavior
- New searches begin with status
PENDINGand transition toCOMPLETEDorFAILED - Provider queries run asynchronously and populate hits when matches are found
- Search IDs are UUIDs that can be used with the Get Search endpoint
Request Body
The request requires:- reference: Unique identifier for the search (max 200 characters)
- input: Array of profile fields with
labelandvaluepairs
Accepted Labels
For INDIVIDUAL entities:first_name- First name (required if not using full_name)last_name- Last name (required if not using full_name)full_name- Full name (required if not using first_name and last_name)entity_type- Must be “INDIVIDUAL” (optional, defaults to INDIVIDUAL)date_of_birth- Date of birth in YYYY-MM-DD formatplace_of_birth- Place of birthcountry_code- Country code
name- Business name (required)entity_type- Must be “BUSINESS”country_code- Country codecompany_identifier- Company registration number
Examples
Individual with full name:Workflow
After creating a search, the system will:- Generate a unique search ID
- Initialize the search with status
PENDING - Query the configured screening provider
- Populate hits array with any matches found
- Update search status to
COMPLETED
FAILED.
Response
The response contains only the search ID:- Check search status with GET /name-screenings/searches/
- Retrieve hits from the search response
- Monitor provider query progress