Touch Form Template
Brings a form template up to date in place: converges any legacy-style
smart-tag anchors in the template’s current version to the current hashed
identity format, addressed by the template’s stable FM-XXXX number. The
request has no body.
Idempotent. A template that is already up to date reports
changed: false and nothing is written — so re-running a touch (or a whole
migration sweep) is safe, and a fleet-wide pass that reports changed: false everywhere proves every anchor RESOLVABLE against the company’s
current field configuration is converged. Anchors naming a field the
configuration does not define are deliberately left unrenamed (readable,
repairable) and do not count as changes.
The template’s content is never altered: only the internal identity of each smart-tag anchor changes; text and tag display names are preserved, and no new version is created — unlike Replace Form Template, a touch updates the current version’s bytes without minting a checkpoint. Static (PDF) forms have no smart-tag anchors and always report a clean no-op.
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.
Response
The touch outcome. changed is true when the template's current
version had legacy anchors that were converged.
The touched template's stable FM-XXXX number.
True when the touch rewrote the template's current version; false when it was already up to date.
The legacy smart-tag identities that were converged to the hashed format, one entry per unique identity. Empty when the template was already converged.
