Replace Static Form
Replaces an existing static PDF form’s content in place, addressed by its
stable FM-XXXX number. The uploaded PDF becomes a new version under the
SAME identity — same number, templateKey, display name, and category — so
forms-logic rules that reference the number keep working. PDFs carry no smart
tags, so nothing is validated; the bytes are committed as-is.
Same-type only. The target number must be a .pdf static form and the
replacement must be .pdf; a DOCX template is replaced via
PUT /forms/template/{number}. This prevents a replace from silently flipping
a form’s file type under the same number.
Required permission: forms:update
Authorizations
API key authentication. Send your raw API key as the Authorization header value with NO scheme prefix — Authorization: YOUR-API-KEY. Do NOT prefix it with Bearer or ApiKey, and do not use an X-API-Key header; those are not accepted.
Path Parameters
Company identifier
The form template's stable FM-XXXX number (as returned by the Upload Form
Template endpoint). It identifies the template across all of its versions and
is the same value forms-logic rules reference.
Body
Response
New version created. The response is the new checkpoint's summary — note
number and templateKey are unchanged from the previous version.
A single form-template checkpoint.
Stable identifier of the template across its versions.
Identifier of this specific checkpoint (version) of the template.
Display name (derived from the uploaded file name).
Human-facing form number (e.g. FM-0010).
The form category assigned to the template.
event, quote-flow, quote-bind-flow, unknown Internal storage key of the checkpoint's document.
