Continued from page 4.
Each signer receives a request to sign, here's the email to Acme Committee, my example customer:
When recipients click on email requests, they are taken to the vanity URL for your company. A simple signing wizard is presented:
Recipients can configure their eversign signatures too:
After signing it looks like this:
When completed, they'll have an option to store the document in their own eversign accont:
At any point in time, the requestor can view the status of the document and send a reminder to those who haven't yet signed:
When both parties have signed the document, everyone can download a copy of the completed, signed document.
Now, you've seen what a simple case of creating and configuring a template and gathering signatures looks like. Now, let's begin using the eversign API to automate this process.
Using the eversign API
Hope you're excited to dig into the eversign API. The company does a great job at developer documentation, let's take a look at the eversign API Documentation:
Your API Access Key
Let's get our API Access Key. Dropdown your company name on the top left side of the dashboard:
Then, click the Developer menu, you'll see your access key and business ID:
Most API calls go to an endpoint like this one with the access key:
All transactions between your application(s) and the eversign API are confidential and contain sensitive data, which is why they encrypt all datastreams using 256-bit HTTPS encryption. It's best to use the eversign API with HTTPS.
Performing eversign API Requests
In order to specify our business for each API request, we'll append the API's business_id parameter (shown blacked out earlier above):
https://api.eversign.com/api/document & access_key = YOUR_ACCESS_KEY & business_id = ####
Some methods have different URL endpoints. Sometimes, hash_id's are used to identify document. Hash_ids can be obtained either from the eversign website or through the API's list_documents.