mailalan | Posts: 1

How to update package status to expired

0 votes
Our application is using e-SignLive for signatures on insurance documents. Our application provides users with the ability to choose wet signatures on paper or e-signing. It is possible for a user to choose e-signing and then change to wet signing on paper after we have sent you the e-sign package but before it has been e-signed. When this occurs, we would like to be able to immediately expire the e-sign package so that they can no longer access it through the URL they received by email. Is this possible? The only method I see in the documentation that allows us to change the package status is changePackageStatusToDraft. If it is not possible to change the status to from SENT to EXPIRED, what other options do we have to make a package in SENT status inaccessible to the signer after it has been sent but before it has been signed? I sent this question e-SignLive support and Arthur recommended that I post it here in this forum. He said there is a way to do this. Thank you, Alan Hamby Web Developer AssuranceAmerica

harishaidary | Posts: 1812

Reply to: How to update package status to expired

0 votes
Hi Alan, Yes it definitely possible to set the package status to EXPIRED. The first thing you need to do is retrieve your document package. Once you have it, you can manually set the status to EXPIRED and update the package using the eSignLive client. The sample code below shows you how its done:
class setToExpire
    {
        private static String apiUrl = "https://sandbox.esignlive.com/api";
        // USE https://apps.e-signlive.com/api FOR PRODUCTION
        private static String apiKey = "your_api_key";

        public static void Main(string[] args)
        {
            EslClient eslClient = new EslClient(apiKey, apiUrl);
            PackageId packageId = new PackageId("03be60f0-276d-4911-9273-291d36eca4f0");
            DocumentPackage myPackage = eslClient.GetPackage(packageId);
            myPackage.Status = DocumentPackageStatus.EXPIRED;
            eslClient.UpdatePackage(packageId, myPackage);
        }
    }
Let me know if you run into any issues.

Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off