Account
I am a
Developer
Product(s)
Earned badges
Achievement: Latest Unlocked
Preferences
Replies
Topics Started
Topic Started
| Topics |
|---|
Hi!
It would appear that the success response message sent by esign sandbox to a request for
signingStatuswas somehow changed, over this last weekend, from 'COMPLETED' to 'SIGNING_COMPLET |
While attempting to upload a document to a package via the following call:
https://sandbox.esignlive.ca/api/packages/9uPhYzkvKRJXmdxv4Bje_7gz9Ls=/documentsI am presented with the follow |
Replies Created
Reply to: name cannot be null or empty
Thursday, March 22, 2018 at 09:18amYes, all of the calls do have the hyphen. This is the exact call that failed with what appears to be a generic default error message from esign servers:
https://sandbox.e-signlive.ca/api/packages/-6OQViWG43OxbVfJ4UB0I9WkNcg=/documentsI can't send you a pdf because they are dynamically created and destroyed by the system.
Reply to: name cannot be null or empty
Thursday, March 22, 2018 at 09:23amThanks for helping. I am loathe to start making changes to the structure of the JSON because this exact same code is working perfectly in production to esignlive. As others have also been having this issue would it not be prudent to update that error message with something a little bit more informative?
Reply to: name cannot be null or empty
Monday, March 26, 2018 at 03:56am@Haris Hi, has there been any movement on this? Any further advice? Our CTO is now opening talking about switching from esign to an alternative platform because of this issue. I'd rather not have to implement a whole new platform but we need to be able to run tests against the sandbox. Any updates would be appreciated.
Reply to: name cannot be null or empty
Monday, March 26, 2018 at 08:22amFor anyone coming looking with the same problem, it appears that file upload to the sandbox requires filename set in
Content-Disposition. I was missing the filename set like so:
Content-Disposition: form-data; name="file"; filename="my_file.pdf"
Subscriptions
| Topics | Replies | Freshness | Views | Users |
|---|---|---|---|---|
Hi!
It would appear that the success response message sent by esign sandbox to a request for
signingStatuswas somehow changed, over this last weekend, from 'COMPLETED' to 'SIGNING_COMPLET |
2 | 6 years ago | 25 |  |
While attempting to upload a document to a package via the following call:
https://sandbox.esignlive.ca/api/packages/9uPhYzkvKRJXmdxv4Bje_7gz9Ls=/documentsI am presented with the follow |
13 | 6 years 1 month ago | 475 | |
Subscriptions Release Notes
This user is not subscribed to any release notes.