Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
This user has not created any forum posts.
Replies Created
Reply to: Not apply the same signature to the next signing block
Tuesday, May 22, 2018 at 01:41pmHello
Thanks for the clarification. When I tried to update the 'enforceCaptureSignature' field of the package using the PUT API
URL : PUT https://apps.esignlive.com/api/packages/O-vXz8y_nZpx87g4Vfgnw4b4ZA4=
Request Body:
{
"settings": {
"ceremony": {
"enforceCaptureSignature": true
}
}
}
I get 403 forbidden error:
{
"messageKey": "error.forbidden.cannotEditDeletePkg",
"technical": "package: O-vXz8y_nZpx87g4Vfgnw4b4ZA4= cannot be edited.",
"message": "Cannot edit or delete package.",
"code": 403,
"name": "Access Denied"
}
I am using the same key that I use to create the package. Am I doing anything wrong?
I use .withStatus(PackageStatus.DRAFT) to set the package as a DRAFT while creation. Also tried eslClient.changePackageStatusToDraft(packageId) to set it to DRAFT state.
Reply to: Not apply the same signature to the next signing block
Friday, May 25, 2018 at 09:07amCan you please share an update on this?
Reply to: Not apply the same signature to the next signing block
Friday, May 25, 2018 at 09:55amI am getting a 403 when I do a PUT on the https://apps.esignlive.com/api/packages/O-vXz8y_nZpx87g4Vfgnw4b4ZA4=
I get 403 forbidden error:
{
“messageKeyâ€: “error.forbidden.cannotEditDeletePkgâ€,
“technicalâ€: “package: O-vXz8y_nZpx87g4Vfgnw4b4ZA4= cannot be edited.â€,
“messageâ€: “Cannot edit or delete package.â€,
“codeâ€: 403,
“nameâ€: “Access Deniedâ€
}
I am using the same key used for creation of the package.
Can you give me a sample of the API requests which succeeded for you so that I can compare and check if I did anything incorrect?
Reply to: Not apply the same signature to the next signing block
Monday, May 28, 2018 at 06:52amThanks for the information. It worked for me! I had been trying to use the PUT API after SENDing the document. I changed my code and did the PUT before sending the doc. It works for me now. Can you please give me an idea on when this feature might be part of SDK?
Reply to: Not apply the same signature to the next signing block
Friday, June 1, 2018 at 11:10amWe are experiencing unresponsiveness in the SDK method calls and API calls as well. Are the eSignLive services down?
Subscriptions
This user is not subscribed to any release notes.
Subscriptions Release Notes
This user is not subscribed to any release notes.