Unarchive contract template
Restores an archived template to DRAFT status so it can be edited and
published again.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
Restore an archived contract template version back to DRAFT status so it can be edited and published again. Unarchiving also clears the template's published_at timestamp. Returns the updated template version.
Authentication & access
- Requires a client API token:
Authorization: Bearer <token>. - The caller must hold the
contracts.templates.archivepermission and have the OWNER or OPERATIONS role. - Contract signing must be enabled for the client. If it is disabled the request returns
403.
Path parameters
template_version_id(string, required) — the template version to unarchive. It must belong to your client.
Preconditions
- The template version must currently be in
ARCHIVEDstatus. Unarchiving a template that is in any other status (for exampleDRAFTorPUBLISHED) returns400.
State transition
On success the template version is moved from ARCHIVED to DRAFT and its published_at timestamp is reset to null. The template can then be edited and published again.
Response
200 — returns the updated ContractTemplateVersionResponse with status now DRAFT, published_at set to null, and the template's roles, fields, and detected variables.
Error responses
| Status | When |
|---|---|
400 | The template version is not in ARCHIVED status |
403 | Contract signing is disabled for the client |
404 | No template version with this id exists under your client |
422 | Path parameter failed validation |
Standard 401 (authentication), 403 (insufficient permission or role), and 429 (rate limit) responses apply to every endpoint and are documented in the Error reference.