Creating package using REST API Text Tag not working

Hi there, Ids care case sensitive in eSignLive. In your payload, you defined "signer1" as the id of your signer but in your document you have "Signer1". Simply make the correction in either your payload or document and it should be working.

Thanks Haris for quick response it is working! now. Also I noticed that in the package my name teh.p.liu get added as "Myself" is there any way to remove it using API or not create it at all. I just need Recipient Name I have attached screen shot

Yes, you will need to add the "senderVisible" field in your payload.

{
  "documents": [
    {
      "id": "Demo",
      "name": "Test Document",
      "extract": true,
      "data": {
        "esl_doc_extract_type": 1
      }
    }
  ],
  "status": "DRAFT",
  "type": "PACKAGE",
  "roles": [
    {
      "id": "signer1",
      "type": "SIGNER",
      "signers": [
        {
          "email": "[email protected]",
          "firstName": "John",
          "lastName": "Smith",
          "id": "signer1"
        }
      ],
      "name": "signer1"
    }
  ],
  "name": "Text Tags Example Package",
  "data": {
    "senderVisible": false
  }
}

THANK YOU HARIS you have been a great help. Your solution resolved my issue.

My pleasure :)

I'm attempting to do something similar with the REST API, but the service reports that I must define approvals. Do I need to specify a particular version?

It looks like you're attempting to send a package without any signatures defined. Can you share your json payload (copy-paste it using the

 tags) along with your documents so I can have a look?

{"status":"SENT", "documents":[{ "id":"Application", "description":"Application.pdf", "name":"Application.pdf", "extract":true, "data":{ "esl_doc_extract_type":1 } }], "roles":[{ "signers":[{ "name":"OWNER1", "auth":{ "scheme":"NONE", "challenges": [] }, "id":"OWNER1", "language":"en", "title":"OWNER", "firstName":"Ken", "lastName":"Hartness", "email":"[email protected]", "company":"Hartness Inc.", "phone":"2815834432" }], "name":"OWNER1", "index":1, "id":"OWNER1", "type":"SIGNER" }], "visibility":"ACCOUNT", "notaryRoleId":null, "settings":{ "ceremony":{ "optOutReasons":["Signing application with agent", "Mailing application"], "maxAuthFailsAllowed":3, "handOver":{ "title":"Signed Merchant Application", "text":"Welcome!", "href":"https://www.merchantfoundry.com" }, "documentToolbarOptions":{ "downloadButton":true }, "hideLanguageDropdown":true, "hideCaptureText":true, "declineButton":true, "optOutButton":true, "hideWatermark":false } }, "type":"PACKAGE", "autocomplete":true, "trashed":false, "description":"MCPS Application", "name":"MCPS Application Package", "due":"2018-04-30T00:00:00Z", "language":"en", "completed":null, "data": { "senderVisible": false } }

Looking at your pdf, you need to make sure that the text tags are not broken apart on different lines. See attachment.

I reduced the date to 1-point font so it is entirely on one line. Still receiving this response: {"messageKey":"error.validation.sendPackage.noApprovals","entity":null,"technical":null,"packageId":null,"message":"Cannot send package without approvals.","code":400,"name":"Validation Error"}

I've updated your document to make it work using text tags. Please make sure that there aren't any typos in the text tags. Otherwise, it will not work.

document

curl -H "Authorization: Basic $1" -H "Accept: application/json; esl-api-version=11.12" -X POST $2 -k -F [email protected]$3 -F [email protected]$4 > $5 Your PDF (or mine) with the JSON I included, earlier, produces the following response: { "messageKey":"error.validation.sendPackage.noApprovals", "entity":null, "technical":null, "packageId":null, "message":"Cannot send package without approvals.", "code":400, "name":"Validation Error" }

Can you share a package id so I can have a look at your account with our support team?

7cc86556-171e-4ed4-b498-b9487a353423 We've never used anything other than position-specific signatures, but as the forms are updated, this is becoming impractical. If text tags must be enabled in the account, then that could be the problem. We could simply interpret the text as anchors, but text tags sounded so much easier.

Ah I see what's going on. Your account is still on the classic environment. The text tag extraction feature is only available on the new environments (https://sandbox.esignlive.com). Please create a new account there and then send an email to [email protected] to have the text tag extraction feature enabled.