API reference
A template keeps the recipient slots and the fields bound to them, so a document made from one can be sent for signature straight away — no signature blocks to place, no fields to map.
Base URL https://xdocs.io/api/v1, with Authorization: Bearer xdk_… on every request. Pagination, rate limits, scopes and error codes are the same for every endpoint and are described once, in how the API behaves.
A document saved for reuse. Recipient slots and the fields bound to them are kept; the addresses and access codes are stripped, so a template can never quietly send to whoever signed last time.
/api/v1/templatesdocuments:readSaved templates, most recently changed first.
Query parameters
limitintegercursorstringnextCursor. Opaque — pass it back unchanged.Returns
{ data: Template[], nextCursor } — id, name, description, kind, pageCount, recipients: [{ id, name, role, routingOrder }], useCount, createdAt, updatedAt
/api/v1/templates/:iddocuments:readOne template.
Query parameters
includestringcontent adds the body.Returns
{ data: Template }
/api/v1/templatesdocuments:writeSave one of your documents as a template.
Body (JSON)
documentIdstringrequirednamestringdescriptionstringReturns
201 { data: Template }
422 A spreadsheet, which a template cannot hold: a template keeps a body, and a sheet's body is only its grid worked out./api/v1/templates/:iddocuments:writeRename or re-describe a template. Its body is fixed at save time.
Body (JSON)
namestringdescriptionstringReturns
{ data: Template }
/api/v1/templates/:iddocuments:writeDelete a template. Documents made from it are untouched.
Returns
204