khartness's account

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?

{"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 } }

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"}

curl -H "Authorization: Basic $1" -H "Accept: application/json; esl-api-version=11.12" -X POST $2 -k -F payload=@$3 -F file=@$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" }

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.