# Save template (/api-reference/templates/saveTemplate)

Save a reusable template blueprint for a file. A template stores the
source `file_id` and an ordered `signers` array, where each signer
contains its own PDF elements and optional signer-level defaults.

- `signers` is ordered: the first template signer maps to the first
  runtime signer supplied later in `initialize-from-template`, and so on.
- Every signer must contain at least one `signature` element.
- A `field_id` is generated automatically for each saved element and
  returned in template reads; those values are what
  `initialize-from-template.signers[].element_values` uses later.
- `file_id` must belong to the authenticated user.


This page is generated from the OpenAPI specification — read /openapi.yaml for the full request/response schemas, examples, and error codes.