Getting Started Questions

Hi, Just a little bit of background first on what my objective is: We have a Web Application for Institutions used by their staff (brokers). The Application which creates legal forms with merged data in PDF. The final output is a combined set of legal forms with merged data from the back end. In the conventional approach, the broker will print the set of forms and have his client sign them, scan them with the signature and save it back to the application as a digital attachment into the Web Application for future references or auditing trail. I've taken a look at the 2 blogs how to create and how to check package status and the available methods with REST. In our modified work flow, here are the places we've identified where the Signature API are required. (Can you identify the Web REST Methods I need in each case?) 1. On creation of new Form Set for a New Application, We need to call a method to Upload our Merged PDF which has predefined (Text Fields) fields over signature area (where a Signature is required) in different parts of the set of forms - ie multiple forms. This is also where we will send all the info of the Signing parties required- Example : We can have 2 applicants with their respective emails on the application and as such require both their signatures each in a specific area across the forms. 2. We also need a way to to retrieve the Signing URL ( I understand , the default , an email is privately sent to the applicants ) which our Web Application can retrieve and present them . The Applicants can be either remotely in which case the private email for signing will be used OR in front of the broker doing the application. In the latter case, we plan on retrieving the Signing URL to present them to the applicants on a mobile device like a Tablet which will sum up basically the Application AND provide them the option to sign over eSignLIve but on the Broker's Tablet. 3. On reviewing an existing Application, If a previous Signing Event was submitted but not completed by all parties, we need a way to identify the status and present the broker with either a "COMPLETED" Status or Retrieve the Signing URL ( as #2 above ) 4. When all parties has completed the signing process on a particular Application, we need to be able to download the SIGNED documents - ideally automatically PUSH from your Web Services or on demand from our Web Application. Finally, once downloaded, we would deleted the forms from your server. 5. Our Application supports multiple Institution with brokers working for them. We would probably support 2 types of set up:

• a. a Single eSignLive Front end... where ALL Institutions forms are stored on one Account ( ours ). We figured , the institutions , wouldn't necessarily need a Front end to ESignLive as they are only concerned with the Capturing of the Signature and Archiving it in our Application
• b. Each Institution who would like to use your Front end for all their ESignatures outside those we generate in our application.

Do you foresee any caveats or precautions i need to take care - example: In the case of a Single Set up, is there a way to send an InstitutionId to your WebS so that we can distinctively identify which Institution are the forms from - I would probably need a filter by this InstitutionId in the Front End. Also, is the Auth Token will be the different for each Institution, if we do the multiple Accounts. I'm just getting my feet wet .... trying to identify the different web methods i need to consume based on our work flow ...etc. Based on my workflow, I've identified 5 calls which I'll be using - POST /packages Can I send only one call with all the Applicants Info , Upload the Binary or do I need multiple REST calls ? How do I send References from our Applications like the InstitutionId and the Application Number where these can be searched on or filtered on your UI? - GET /packages/{packageId}/roles/{roleId}/signingUrl : Is the RoleId generated by your system returned to me on the POST/packages - since this is where I first send the applicants within the or is it our own unique Id which we pass to you? -GET /packages/{packageId}/signingStatus: How do I check who hasn't signed? - GET /packages/{packageId}/documents/zip -DELETE /packages/{packageId} SNIPPETS & SAMPLE CLASSES: From your example blog, I saw you created the JSON payload from scratch - using the string. Would you have a complete JSON ( which I can use to construct a class) or CLASS which I can use to serialize directly ( I'm using C#) for the package method? Similar, would you have one for the response which will define all the possible nodes and their enumerations ( exampl different status SENT, SIGNING_COMPLETED, etc ) Thanks