Archiving a template affects future signing. It is not a way to delete historical waivers or hide a template from just one staff member. Before building an archive action, identify every public route and integration that uses that template.
Inventory active consumers
Check booking messages, QR signs, event workflows and any template picker in your integration. A template can be used beyond the page where the operator clicks archive. Give the operator enough context to understand that new signatures will stop.
Use templates:read for inspection and templates:manage for the lifecycle mutations. Keep the archive action distinct from ordinary draft editing because saving a draft does not have the same effect on public signing.
Apply the documented lifecycle
The archive request shape is:
POST /v1/templates/{id}/archive
Authorization: Bearer YOUR_API_KEY
Archiving stops new signatures, causes the public signing page to return 404 and removes the template from the ordinary list endpoint. Already-signed waivers remain connected to their original versions. See archive template.
Restoring uses a different action:
POST /v1/templates/{id}/unarchive
Authorization: Bearer YOUR_API_KEY
The documented result is active when a published version exists, otherwise draft. A restored draft-only template should not be presented as ready for guest signing merely because the restore request succeeded.
Refresh dependent interfaces
After the mutation, refresh your local template choices and any displayed availability. A cached template list can continue to offer an archived form until your application rechecks it. Do not assume an absent item in that list means its historical signed records were deleted.
For an uncertain response, inspect state before repeating the lifecycle action. Keep the operator’s intended change and the request identifier available for troubleshooting without storing participant content.
Test the public and historical paths
Use a controlled template with a published version and sample signed record. Confirm the public route’s behavior after archive and the retained record’s version. Then test restoration. Also test a template that has never been published so the draft-only case is visible.
Coordinate physical signs and external booking links through the link-retirement process. Technical state changes and guest communications need owners even when the endpoint itself is a single request.