DevelopersAPI referenceSignTemplates
Template detail
One template — public built-ins, the caller's own, or a teammate's org-shared one.
View as MarkdownAuthorization
bearer AuthorizationBearer <token>
In: header
Path Parameters
id*string
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/templates/string"{ "template": { "id": "string", "name": "string", "description": "string", "category": "string", "created": "2019-08-24T14:15:22Z", "modified": "2019-08-24T14:15:22Z", "usageCount": 0, "isPublic": true, "hasFile": true, "pages": 0, "content": { "sections": [ { "heading": "string", "body": "string" } ], "placeholders": [ { "key": "string", "label": "string", "hint": "string" } ] }, "visibility": "string", "ownerId": "string", "recipients": [ { "name": "string", "role": "string", "orderIndex": 0 } ], "fields": [ { "type": "string", "x": 0, "y": 0, "width": 0, "height": 0, "page": 0, "required": true, "label": "string", "recipientIndex": 0 } ] }}Create a template
Creates a private template; recipients/fields are stored as opaque JSON arrays.
Update a template
Owner-scoped. Built-ins and teammates' shared templates read as not found — visible, but not editable. Besides metadata and visibility, the recipient slots and field layout are editable (the template editor saves its whole canvas), with the same validation as document fields.