.NET SDK

we have our application as front end to eSignLive system.

Team, Trying to form iframe url for sender in the package. When i open the url, seeing an error unauthorized access.

Hello, We recently upgraded our internal ESL system to 6.2. After the upgrade, packages created with .WithDialogOnComplete() no longer present the dialog at the end of the signing process. Is there a separate setting that has to be enabled on the account level for this dialog to work?

I have a Dynamics CRM which matches the Statuses of the ESign Packages and I need to reconcile them. Right now there are 28 Transaction in my Inbox, 16 Documents in Draft, 0 Archived and 29 in Trash. That's 73 Transactions total.

Hi, I came across an issue today, we are receiving the in-correct document status when we try to check that from .NET SDK. For Document 1: Package Id : DawPINFPRX_fGrvTnRi0DA6UV0I= Document Id : consent-Buyer API URL : https://sandbox.esignlive.com/api/packages/DawPINFPRX_fGrvTnRi0DA6UV0I=/signingStatus?signer=Buyer&document=consent-Buyer SDK _client.GetSigningStatus(new PackageId(packageId), signerId, documentId); For Document 2: Package Id : DawPINFPRX_fGrvTnRi0DA6UV0I= Document Id : b9c00c8d-647a-463f-9b1b-bb30d7470457 API URL

Here is the scenario. I need to change the Expiration Date of several packages that are about to expire out 30 Days.

Hi all, We are currently using SDK version 10.13 and accessing through the portal at https://sandbox.e-signlive.com. We would like to move to using the new portal at https://sandbox.esignlive.com. After looking around some, I couldn't seem to find in the existing portal that we log into which version of eSignLive we are using to find an upgrade path. The credentials we have for the current portal don't work for the updated portal (https://sandbox.esignlive.com).

We are trying to upload the attached PDF (eF2 - Sign.pdf) to eSignLive as a document to sign. It contains a signature block embedded in it. The error we get while ww upload it from eSignLive portal (image attached herewith) is the same which we get while we try the same using SDK. Following is the error we get from SDK: Could not upload document to package. Exception: HTTP POST on URI https://apps.esignlive.com/api/packages/8I3D8RMX4Ye7XKa0Rl9caUIfu2s=/documents resulted in response with status code: [500, Internal Server Error].

I am implementing eSignLive integration with one of my services. I need a detailed documentation of all 'Optional details message' for 400 Bad requests that can be thrown on createPackage SDK method. Is there such a documentation available?

Hi, On december 1st 2017, I have submitted a Pull Request on GitHub as I wanted to have my enhancement merged into the official SDK.