Overview
Typical eSign integrations follow the same general workflow: authentication, user management, and session creation. Once a session is created through the API, the user is redirected to the eSign web application for session customization. After a signer has completed signing, eSign will post updates to a client’s endpoint acting as a listener service, notifying the client when documents are available for collection in addition to pushing documents once they are signed. This is simply a high level description and below is a flow chart of the general workflow.