Using Form Fields Per Document with Pre-filled Data
Overview
Using pre-filled data with form_fields_per_document allows you to add data on your documents without the need for a template. Fields are programmatically placed on a document with form_fields_per_document using a x/y coordinate system. It’s well-suited for working with dynamically generated documents, transferring field mappings from old documents to new ones, and more.
Form Fields per Document Structure with Pre-filled Data
To add pre-filled data into Merge Fields, use the form_fields_per_document parameter and specify the field type as either text-merge or checkbox-merge. This creates the data fields, which can then be populated with data in the custom_fields property in the request.
The custom_fields value for the above form_fields_per_document:
Using Form Fields per Document with non-embedded and embedded signing
Send Signature Request Endpoint with Form Fields Per Document:
Create Embedded Signature Request Endpoint with Form Fields Per Document:
Using Form Fields per Document with non-embedded requesting and embedded requesting.
Create Unclaimed Draft Endpoint with Form Fields Per Document
Create Embedded Unclaimed Draft Endpoint with editable merge fields:
Things to consider
- You’ll need to use both the
form_fields_per_documentandcustom_fieldsparameters in the same API request to pre-fill data on the fields of the document. - The ability to make pre-filled fields editable or non-editable for your signers is set in the
form_fields_per_documentsigner fields. - When implementing pre-filled fields with non-embedded or embedded requesting, the requester/sender can adjust these fields prior to sending a signature request.
- Placing your pre-filled fields outside the document’s x/y coordinates will cause an error and the signature request will not be sent.