SteveM's account

Thanks Duo, I did just upload the zipped package for you. Before I was sending the Sender and it's role when I created the package after accumulating all of the forms in a PDF. Now I must send each form separately, so when I get to one that has signers, the package already contains the welcome or cover page form and maybe some others. I create the package as a draft and send the documents before finally changing it to SEND when the stage is completed. Our customers each have an API key and will create several senders for different purposes. I don't expect them to want the account owner as a sender for any of their packages. I use REST calls to add the senders and keep their ID's in a database so I can use them on the documents. I have logic which accepts the sender and other needed data for each signature. I guess it boils down to needing a way to upload documents for a new package without letting the account owner get defaulted so I can set the sender when it is available. Is there a way to do that?

OK, I finally got back to this. I wound up writing a pre-process subroutine to go through the stage and find the first status and sender information. If the status is blank I POST with the sender I found. If I have a status I PUT using the package ID I found. I will keep the template idea just in case I get cornered again. Sounds like a way to improve performance in the future if uploading all the documents is too slow. Thanks for your help. BTW, and error response on the POST when the sender is changed would have saved a lot of time here.

Hi Duo,

Thanks for responding.

I am aware that lowercase is needed. I am using the token to create a package in:

https://sandbox.esignlive.com/api/packages/ POST

I use the unchanged address for the json Sender:email and Signers on that request with no problem. This is confusing and costs time to debug because the case mismatch issue is not mentioned in the API documentation for either call.

I am suggesting this be treated as a bug to save others this pain.

Steve

 

Duo,

 

I ran a test with debug code to dump the json payload to check my assertion. I am attaching it as an example of creating a package with a mixed-case signer email.

Steve