Trigger a workflow

Trigger a workflow run on an existing session. The session must be in `completed` or `failed` status. This is useful for retrying after investigation, running a different workflow on an existing session, or regulatory re-verification. The previous workflow run (if any) is deleted and the session is set to `processing`. The workflow executes asynchronously — poll the session or use webhooks to track completion. **Required scope:** `workflows:trigger` (or legacy `workflows:write`).

Trigger a workflow run on an existing session. The session must be in completed or failed status. This is useful for retrying after investigation, running a different workflow on an existing session, or regulatory re-verification.

The previous workflow run (if any) is deleted and the session is set to processing. The workflow executes asynchronously — poll the session or use webhooks to track completion.

Required scope: workflows:trigger (or legacy workflows:write).

Authentication

X-API-Keystring

Organization API key. Keys are prefixed with vk_live_ (production) or vk_sandbox_ (sandbox).

Path parameters

workflow_idstringRequired

Workflow ID (wfl_*).

Request

This endpoint expects an object.

session_idstringRequired

The session to run the workflow on.

Response

Workflow trigger accepted. The session is now processing.

session_idstring

workflow_idstring

statusstring

Errors

401

Unauthorized Error

404

Not Found Error

409

Conflict Error

422

Unprocessable Entity Error

The previous workflow run (if any) is deleted and the session is set to processing. The workflow executes asynchronously — poll the session or use webhooks to track completion.

Required scope: workflows:trigger (or legacy workflows:write).

Organization API key. Keys are prefixed with vk_live_ (production) or vk_sandbox_ (sandbox).

Workflow ID (wfl_*).

API version date string (e.g. 2026-02-01). If omitted, the version pinned to your API key is used.

Response key casing. Defaults to snake.

This endpoint expects an object.

The session to run the workflow on.

Workflow trigger accepted. The session is now processing.

$	curl -X POST https://devapi.withverifa.com/api/v1/workflows/workflow_id/trigger \
>	-H "X-API-Key: <apiKey>" \
>	-H "Content-Type: application/json" \
>	-d '{
>	"session_id": "ses_abc123"
>	}'

$	curl -X POST https://devapi.withverifa.com/api/v1/workflows/workflow_id/trigger \
>	-H "X-API-Key: <apiKey>" \
>	-H "Content-Type: application/json" \
>	-d '{
>	"session_id": "ses_abc123"
>	}'

Trigger a workflow

Authentication

Path parameters

Headers

Request

Response

Errors

Authentication

Path parameters

Headers

Request

Response

Errors

1	{
2	"session_id": "ses_abc123",
3	"workflow_id": "wfl_abc123",
4	"status": "processing"
5	}