Trigger a Compliance Orchestrator screening
Starts a compliance screening against an active workflow and returns a screeningId. The screening runs asynchronously — poll GET /v1/compliance/orchestrator/screenings/{screeningId} for the result.
Unlike the screening that applies automatically to submitted transactions under /v1/screening, this is called on demand, before anything exists on-chain.
Headers
A unique identifier for the request. If the request is sent multiple times with the same idempotency key, the server will return the same response as the first request. The idempotency key is valid for 24 hours.
Body
Response
Screening accepted
Acknowledgement that a screening was accepted and is now running.
Identifier of the screening that was created. Poll GET /v1/compliance/orchestrator/screenings/{screeningId} with it for the verdict.
"a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d"
A screening's lifecycle status.
PENDING— accepted, not startedRUNNING— one or more steps in flightCOMPLETED— every step finished and the workflow outcome is setFAILED— the screening could not be completed
PENDING, RUNNING, COMPLETED, FAILED "COMPLETED"