triggerQuickScan
Quick Scan APIs
Trigger Quick Scan Screening
POST
triggerQuickScan
This endpoint triggers a Quick Scan screening for an individual or a corporate entity.
The scan runs asynchronously — the response returns immediately with a
Possible values per engine:
screeningId that you can use to poll for results.
Query Parameters
Available Screening Engines
Headers
Example Requests
Screen an Individual with ArtemiScan
Screen a Corporate Entity with Multiple Engines
Response
A successful response returns aScreeningResponseDto with an HTTP 200 status code.
Key Response Fields
Status Object
Thestatus field contains a map of each screening engine to its individual status:
PENDING, DONE, FAILED.
Example Response
What to Do Next
- Poll for completion — Call
GET /api/quickscan/screen/{screeningId}using the returnediduntilfinalStatusbecomesDONE. - Retrieve hits — Call
GET /api/quickscan/screen/{screeningId}/hit?screeningType=ARTEMISCANto get potential matches for each engine.
Notes
- This is an ad-hoc scan and does not require a customer record to be created.
- Multiple screening engines can be combined by repeating the
chosenEnginesquery parameter. - The screening runs asynchronously. The initial response will have
finalStatus: "PENDING". - Use Get Quick Scan List to retrieve historical Quick Scans and review past results.
Important Notice
Authorizations
The access token received from the authorization server in the OAuth 2.0 flow.
Headers
X-Domain-ID
Query Parameters
One or more screening engines (repeat param to add more).
Available options:
ARTEMISCAN, DJ, FACE_COMPARE, INTERNET_SEARCH, OCR, OWN_RESTRICTED_LIST, TR customerType
Available options:
CORPORATE, INDIVIDUAL name
Response
OK
Available options:
DONE, FAILED, NEVER, PENDING Available options:
CLOSED, OPEN Available options:
CORPORATE, INDIVIDUAL Available options:
ARTEMISCAN, DJ, FACE_COMPARE, INTERNET_SEARCH, OCR, OWN_RESTRICTED_LIST, TR Available options:
ADVERSE_MEDIA, NO_HIT, OWN_RESTRICTED_LIST, PEP, SANCTION 