Send Signature Request from Template
Creates and sends a new signature request from a template with the submitted template data.
Required scopes (OAuth 2.0)
Required scopes (OAuth 2.0)
sign:requests and templatesAuthorizations
Provide your API key in the X-API-Key header, e.g., X-API-Key: YOUR_API_KEY.
Body
ID of the template. ID needs to include the prefix returned by the template list endpoint.
The title of the signature request.
1 - 255Signers of the signature request.
When the signature request will expire. This is a unix epoch timestamp (miliseconds). Should be later than today.
Key–value pairs for Merge Tags defined in the Sign template. Keys must match tag names. Values replace the corresponding tags and are rendered as plain text in the sent agreement.
Key–value pairs for Form Fields defined in the template. Keys must match field names. Values prefill the corresponding fields in the sent agreement.
Key–value pairs for Variables defined in the AgreementGen template. Keys must match variable names. Values prefill the corresponding variables and are rendered as plain text in the sent agreement.
Map of collection name → array of record objects used to expand table-scoped row-loop markers in the template.
- Each key must match a collection name returned by Get Template Details under
collections[].name. - Each value is an ordered array of flat record objects; each record is a key–value map where keys match the collection's variable names and values are strings.
- Records are rendered in array order.
- Maximum 100 items per collection, and up to 50 collections per request.
Applies to AgreementGen templates only. Ignored silently when the resolved template type is not lumin.
Viewers of the signature request.
Custom email content for the email sent to signers.
Response
Returns the information of the created signature request.
Contains information about a signature request.