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.
POST
TypeScript
Headers
Body
application/json
Response
Screening accepted
Acknowledgement that a screening was accepted and is now running.
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
Available options:
PENDING, RUNNING, COMPLETED, FAILED Example:
"COMPLETED"