Unarchive contract flow
Restores an archived contract flow so it can be used again. Returns 404
if the flow does not exist and 400 if it is not archived.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Restore an archived contract flow so contracts can be sent from it again. Its template must not be archived either; otherwise sending still returns 400. Saving the flow with PUT /api/v1/contracts/workflows/{workflow_id} also restores it.
This endpoint is for contract flows (
/contracts/workflows). Automation workflows (/workflows) have their own unarchive endpoint.
Authentication & access
- Requires a client API token:
Authorization: Bearer <token>. - API credentials need the
contracts.workflows.archivepermission. Dashboard users need the OWNER or OPERATIONS role, or a custom role that includes this permission. - Contract signing must be enabled for the client. If it is disabled the request returns
403.
Path parameters
| Parameter | Description |
|---|---|
workflow_id | ID of the archived contract flow to restore. Must belong to your client. |
Response
200 - The updated contract flow, with status set back to published.
Error responses
| Status | When |
|---|---|
400 | The contract flow is not archived |
403 | Contract signing is disabled for the client |
404 | No contract flow with this workflow_id exists under your client |
Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.