Sending for signing
Get the API key from here
Get the documentId
Prepare the JSON Body
Send a template for signing
BoloForms BASE_URL to use https://sapi.boloforms.com/signature
POST
/pdf-template-lambda
Headers
Name | Value |
---|---|
|
|
|
|
Body
Key | Required | Value | Description | Reference Image |
---|---|---|---|---|
YES | Select PDF_TEMPLATE if you want to send PDF template for signing else select FORM_TEMPLATE | N/A | ||
YES | ||||
NO | ||||
NO | This is not required to be added in required but is recommended to customize the email body and title according to your customers data, making the email more authentic | N/A | ||
YES | ||||
YES | The same PDF which you uploaded in the UI it needs to be sent via API as base64 because you can send a different PDF as well if you want other then the PDF you uploaded as a template with all your mapping and variables kept intact page by page For example - Suppose you've uploaded a 50-page PDF where each page contains a signature field. Later, you need to send a PDF that is only 30 pages but follows the same format. Instead of creating a new template or manually setting up the fields again, you can simply send the new 30-page PDF as a base64 string via the API. The system will automatically recognize the structure and map the fields to the correct locations, page by page, based on the original template. This ensures that the new PDF aligns with the existing template, saving time and avoiding redundancy. |
Response
Example Request
Last updated