curl --request POST \
--url https://api.artemis.cynopsis.co/api/customer/{customerId}/screen \
--header 'Authorization: Bearer <token>' \
--header 'X-Domain-ID: <x-domain-id>'curl --request POST \
--url https://api.artemis.cynopsis.co/api/customer/{customerId}/screen \
--header 'Authorization: Bearer <token>' \
--header 'X-Domain-ID: <x-domain-id>'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).You must always include both query parameters (includeCrpandonlyUpdated) in the request URL.
Even if the value isfalse, it still needs to be explicitly set.
curl -X POST "{{backend_url}}/api/customer/{{customerId}}/screen?includeCrp=false&onlyUpdated=false" \
-H "Authorization: Bearer <token>" \
-H "X-Domain-ID: {{domain_id}}"
curl -X POST "{{backend_url}}/api/customer/{{customerId}}/screen?includeCrp=true&onlyUpdated=false" \
-H "Authorization: Bearer <token>" \
-H "X-Domain-ID: {{domain_id}}"
curl -X POST "{{backend_url}}/api/customer/{{customerId}}/screen?includeCrp=false&onlyUpdated=true" \
-H "Authorization: Bearer <token>" \
-H "X-Domain-ID: {{domain_id}}"
curl -X POST "{{backend_url}}/api/customer/{{customerId}}/screen?includeCrp=true&onlyUpdated=true" \
-H "Authorization: Bearer <token>" \
-H "X-Domain-ID: {{domain_id}}"
The access token received from the authorization server in the OAuth 2.0 flow.
X-Domain-ID
customerId
chosenEngines
ARTEMISCAN, DJ, FACE_COMPARE, INTERNET_SEARCH, OCR, OWN_RESTRICTED_LIST, TR includeCrp
onlyUpdated
OK