Duplicate template into signing request
Creates a new signing request by duplicating an existing template, including all fields, users, reminders, and settings.
Seals. The new signing request carries the template’s seal participants and the template fields that belong to them. This operation takes no seal_participants key. While multi-document editing is suspended, templates on the multi-document read-only path answer 409 MULTI_DOCUMENT_READ_ONLY. For templates on the single-document path during that suspension, a template seal follows the current version of its lineage: if that current version is revoked or deleted, or the lineage has no current version, the call answers 409 SEAL_UNAVAILABLE and creates nothing; a seal that the API key’s company cannot see, or that is limited to a workspace other than the target workspace, is not copied and neither are its fields, and the 201 lists it in seal_participants as a dropped entry; if a seal would be kept while organization seals are not enabled, the call answers 503 SEALS_DISABLED; the 201 always carries seal_participants (an empty array when the template has no seal participants). For every company during normal operation, the copy attaches the template’s stored seal version as it is, the 201 does not carry seal_participants, and a seal that was replaced, revoked or deleted since the template was saved fails when the request is sent.
Authorizations
API key for authentication. Use your API key directly without any prefix (e.g., 'your-api-key'). Bearer prefix is optional but not required.
Path Parameters
Template ID to duplicate
Body
Custom name for the new signing request (defaults to template name)
255Response
Template duplicated successfully into a new signing request
Duplicated template details
ID of the newly created signing request
Name of the new signing request
Status of the new signing request
"draft"
Workspace the signing request belongs to
Description of the new signing request
Creation timestamp
Seal participants of the new signing request, persisted entries (the shape of the create operations, except that order can be null) with dropped: false, then dropped entries. Not answered during normal operation for any company. While multi-document editing is suspended, duplication of a template on the multi-document read-only path answers 409 MULTI_DOCUMENT_READ_ONLY; on the single-document path, this key is always present, an empty array when the template has no seal participants.
A persisted seal participant of the duplicated signing request: every key of SealParticipantApi, plus dropped: false. order is normally an integer and is null only if the position was not reported when the participant was saved.
- Option 1
- Option 2