The loose mode of integration is where your business application initiates the sign-off workflow, but the end users actually interact with the SigningHub web interface for reviewing and signing documents. The initial steps, i.e. creation of end user accounts on SigningHub, uploading of documents and sharing of documents for sign-off, is initiated by the business application through the SigningHub Restful API.

With loose integration, end users interact directly with SigningHub when it is their turn to sign the document. This contrasts with tight integration where they login to the business application.  Thus loose integration is valuable where a business application does not have an existing web-interface that can be used to allow internal or external users to view and sign documents.

The following image illustrates how a business application interacts with SigningHub through RESTful API calls.



Both tight and loose modes of integrations can be used together within one document workflow, e.g. your internal users interact with SigningHub through your own web application interface through tight integration, whilst external users are interact directly with SigningHub via loose integration.

To implement loose integration, see the Prerequisites section. Once done you can implement these calls in the order to implement loose integration:

Use Case
A sample use case is where a business application wants documents to be electronically signed by its end-users. Ensure the prerequisites are in place. The following describes the process steps:

1. Manual - Add a document to your Enterprise Library 
   Click here for details. This is an Optional step. 
   Skip this step if the document is dynamic and coming from your business application, see below on how to add document dynamically
   
   
2. Coding - Get an admin access token 
   Click here for details. No need to use the scope parameter
   
   
3. Coding - Create a package 
   Click here for details
   
   
4. Coding - Upload a document to the Enterprise admin account
   1. If document is already in your enterprise library then click here
   2. If a document identified dynamically then click here 
      
      
5. Coding – Apply a template 
   Click here for details. See the prerequisites on how to create a template. If template can't be used because the signature fields positions are dynamic then perform these steps in order:
   1. Add workflow users. Click here for details
   2. Create signature fields. Click here for details
      
      
6. Coding - Update user 
   Only implement if the recipients mentioned in the template require updating. Click here for details. This is an Optional step 
   
   
7. Coding - Share the document 
   Click here for details
   
   
8. Coding – Downloads the package/document 
   Once document is shared and you want to download the completed document back then perform these steps :
   1. Check whether the workflow is COMPLETED (find details here and check package_status) 
   2. Download the document
      1. If a single document is shared then click here
      2. If multiple documents is shared as a package then click here

Note: As an electronic signature is being requested hence no user account needs to be created to sign the document. If the signature field is of type 'Digital Signature' then a SigningHub account needs to be created. SigningHub will assist the user to create the account before presenting the document.

Contact your Ascertia sales or local partner if you wish to discuss the service plan that is right for your business needs.  Contact support if you need assistance with integration issues using the RESTful API.