json

Hello, I'm having a hard time structuring my JSON payload to reflect what I want to appear in my package. The documents have already been merged with *MOST* data via another source, but I do need to add some information to one of the 3 documents being sent for signing. This means I cannot build a new package with a form, but need to use the existing PDFs and structure I'm uploading to esign live. In my opinion, the easiest way would be to use a text anchor, find the location I want to add the data, and then give it a value and have esign live write it in.

You guys have been incredibly helpful, and I know you're bogged down. But I figured I would throw this up here and see what information you can provide. I am getting an Unexpected Error. Our technical staff have been notified and will look into the problem.

Hello all, Thank you for the good forum, and your help here! I'm trying to integrate our systems with you, and I'm sending a JSON object trying to clone a template with 1 pdf document inside, but by some reason all the fields are not listed. First thing I've noticed is that when you create the package via your website using the designer, I've noticed that in "approvals" the name field is identical with the signature field ID, and I thought that's it! But unfortunately it didn't worked!

We need a way to find out that a signer’s email is wrong (has bounced) by REST API

I'm trying to use SMS authentication for my signers, but I can't figure out how to format this in my JSON. Any ideas?

Hello, I am trying to use the REST API in my web application to add a document to a package. When I submit my form with a POST request, I am getting a 406 error. The accept header I'm using is application/json. What should I use instead? Thanks, Rex