# `POST /v1/workflows/{id}/publish`: Publish a workflow

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).

Parameters:
- `id` (path, string, required)

Responses:
- 200: The published workflow.
- 401: Missing, unknown or expired API key.
- 402: The plan's active production workflows are used up, or the FINMA profile is not in the plan (code plan_required, feature names it).
- 403: The key lacks workflows:write, or was issued through Connect with secuveri without the workflows:write setup right.
- 404: No workflow with this id in the key's organization and environment.
- 409: The workflow cannot be published as it is, for example a document its environment does not offer; errors lists why.
- 429: More than 30 workflow changes in a minute.
