trevorewen | Posts: 43

Document already signed

0 votes
I have a document that is generated on the fly by our web system. It's a PDF created by the back-end and then goes out for signing. I have been able to upload the document just fine. Once it goes out for signing, there are two signatures it requires. One is from the vendor and the other from the customer. I want a way to store the vendor signature so it's always just 'automatically signed' by them. This makes it so the only signature needed is that of the customer in question. What is the best way to go about this process via the REST API?

Approved Answer
mwilliams | Posts: 957

Reply to: Document already signed

0 votes
Looks like I was incorrect in my previous answer. With version 11, there is a new option to sign all documents for a signer, with the SDK/API, as you can see in the release notes. http://docs.e-signlive.com/doku.php?id=esl:e-signlive_release_notes Here is a link to the API call in the documentation: http://docs.e-signlive.com/doku.php?id=esl:api:e-signlive_documents#post_packages_packageid_documents_signed_documents Please note that this will only work in 11. https://sandbox.esignlive.com/login I will test out the new feature and get back to you. :)

mwilliams | Posts: 957

Reply to: Document already signed

0 votes
Currently there isn't a way to automatically sign a document, to my knowledge. What would prevent you from just using an image for the vendor's signature, if they are not reviewing/signing off on anything in the document?

mwilliams | Posts: 957

Reply to: Document already signed

0 votes
Okay. Sorry for the delay. I tested this out and it worked as expected. I passed the following payload in a POST request to
https://sandbox.esignlive.com/api/packages/{package_id}/documents/signed_documents
{"documents": [
    {
      "status": "",
      "data": null,
      "approvals": [
        {
          "data": null,
          "accepted": null,
          "signed": null,
          "id": "PTvo4a2EySAC",
          "role": "Sender",
          "fields": [
            {
              "data": null,
              "subtype": "FULLNAME",
              "page": 0,
              "height": 50.00000762939453,
              "width": 199.99951171875,
              "binding": null,
              "extract": false,
              "extractAnchor": null,
              "left": 550.0,
              "top": 164.9995880126953,
              "validation": null,
              "id": "hrfCq97cqeYY",
              "type": "SIGNATURE",
              "value": "",
              "name": "PTvo4a2EySAC"
            }
          ],
          "name": ""
        }
      ],
      "pages": [
        {
          "height": 1056.0,
          "width": 816.0,
          "left": 0.0,
          "id": "",
          "top": 0.0,
          "index": 0,
          "version": 0
        }
      ],
      "external": null,
      "extract": false,
      "id": "8bdb50f78222c9bf",
      "signedHash": null,
      "description": "",
      "index": 1,
      "fields": [],
      "name": "sampleAgreement",
      "size": 1267
    }
  ]}
Essentially, this is just the documents section of the package with just the approval I want signed by the API. The other signer's approvals (the entire consent document and the approval I had for them in the sampleAgreement document) were removed. There are probably more fields that can be removed from this, but this for sure worked. I'm guessing that the id for the approval you want signed is the most important part.

trevorewen | Posts: 43

Reply to: Document already signed

0 votes
Hey Michael - Thanks for all your work. I just want to clarify that this will support our process. Our application is an auto insurance quote application. We write and sell the policies. Users create PDF contracts using our online system. The actual insurance is purchased through their auto dealer, so when I say 'dealer' below, I am referring to that dealer (not us). The contract, though issued by us, is between the dealer and the customer. The dealer 'always agrees', so that is the signature we would like to have on file. Here is the flow: 1) Document is created on our server with no human intervention. 2) At the end of our 'bid' flow, the document is uploaded to E-Sign. 3) Dealer signature is already there, but we have around 100 different dealers, so we would have to choose the specific one. 4) Document is sent out only to customer for E-Signing. Sorry about the complexity of the flow, but I just figured I would cover the bases. The big issue is that a human intervenes at no part of this process. We can have all the dealer signatures loaded on the server, but we need to have those ready in advance, and then have a way of knowing which one is which.

mwilliams | Posts: 957

Reply to: Document already signed

0 votes
None of this should be a problem, I don't believe. We're experiencing some issues with the new sandbox, right now. I will look into your scenario again, when it's back up.

CarolineWebb | Posts: 1

Reply to: Document already signed

0 votes

 Very thankful to you for creating PDF on web system by the back-end and have been able to upload the document just fine. Thanks.

Caroline,

Personal statement tutor and design UCAS personal statement at Personal Statement Folks - http://www.personalstatementfolks.co.uk/ in UK.


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off