triggerScreening
Step 5 - Screening
Step 5a — Screen Customer and CRPs
POST
triggerScreening
This endpoint initiates a screening process for a customer. Screening is used to check the customer’s information against the subscribed engine type. Both query parameters are required and must always be provided, set to eitherDocumentation Index
Fetch the complete documentation index at: https://docs.cynopsis.co/llms.txt
Use this file to discover all available pages before exploring further.
true or false:
customerId— This must be the Primary Customer’s ID.includeCrp— screen customer only (false) or customer + CRPs (true).onlyUpdated— always run (false) or only run if profile updated (true).
⚠️ Important Notice
You must always include both query parameters (includeCrpandonlyUpdated) in the request URL.
Even if the value isfalse, it still needs to be explicitly set.
Example Requests
1. Screen Primary Customer Only, it will create new screening
2. Screen Primary Customer + CRPs, it will create new screening
3. Screen Primary Customer Only, create new screening only if updated profile is updated
4. Screen Primary Customer + CRPs, create new screening only if updated profile is updated
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Headers
X-Domain-ID
Path Parameters
customerId
Query Parameters
chosenEngines
Available options:
ARTEMISCAN, DJ, FACE_COMPARE, INTERNET_SEARCH, OCR, OWN_RESTRICTED_LIST, TR includeCrp
onlyUpdated
Response
OK
