Publish a workflow

POST/v1/workflows/{id}/publish

Makes the workflow the one new verifications with its workflow_id run. Checked like publishing in the dashboard: the definition, the documents against the environment's catalog, the FINMA profile against the plan, and, for an active production workflow, a free slot of the plan. Publishing a published workflow again is allowed. Publishing changes which checks real verifications go through: confirm with the person responsible first. Needs the workflows:write scope (a key issued through Connect with secuveri: the workflows:write setup right).

Send your API key in the x-api-key header.

Path parameters

  • idstringuuidrequired

Responses

  • 200The published workflow.
    • workflowobject
      Show 21 child properties
      • idstringuuid
      • namestring
      • descriptionstring
      • environmentstring

        One ofsandboxproduction

      • statusstring

        One ofdraftpublished

      • activeboolean
      • minimum_ageinteger | null
      • ip_countriesobject | null
      • location_countriesobject | null
      • video_hoursobject | null
      • four_eyesboolean
      • outcome_overridesobject
      • score_thresholdsobject
      • status_rulesarray of object
      • stepsarray of string
      • step_configsobject

        Every option of the workflow's steps, defaults filled in.

      • document_rulesarray of object
      • created_atstringdate-time
      • updated_atstringdate-time
      • published_atstring | nulldate-time
      • price_per_verification_chfnumber

        What one verification of this workflow costs; business verification is charged per company on top.

    • warningsarray of string
    • liveboolean

      true when the workflow is published and active: new verifications run it as it is now.

  • 401Missing, unknown or expired API key.
  • 402The plan's active production workflows are used up, or the FINMA profile is not in the plan (code plan_required, feature names it).
  • 403The key lacks workflows:write, or was issued through Connect with secuveri without the workflows:write setup right.
  • 404No workflow with this id in the key's organization and environment.
  • 409The workflow cannot be published as it is, for example a document its environment does not offer; errors lists why.
  • 429More than 30 workflow changes in a minute.
curl -X POST https://api-verify.secuveri.com/v1/workflows/6f1c2e0a-8f43-4f7e-9a51-2b7c1d9e4a10/publish \
  -H "x-api-key: $SECUVERI_API_KEY"
Response · 200
{
  "workflow": {
    "id": "0b8f4f5e-3c2a-4d1b-9e7f-6a5c4b3d2e1f",
    "name": "Jane Doe",
    "description": "<description>",
    "environment": "sandbox",
    "status": "draft",
    "active": true,
    "minimum_age": 1,
    "ip_countries": null,
    "location_countries": null,
    "video_hours": null,
    "four_eyes": true,
    "outcome_overrides": {},
    "score_thresholds": {},
    "status_rules": [
      {}
    ],
    "steps": [
      "string"
    ],
    "step_configs": {},
    "document_rules": [
      {}
    ],
    "created_at": "2026-10-23T09:12:44.120Z",
    "updated_at": "2026-10-23T09:12:44.120Z",
    "published_at": "2026-10-23T09:12:44.120Z",
    "price_per_verification_chf": 1
  },
  "warnings": [
    "string"
  ],
  "live": true
}