Go>Sign signing

To perform Go>Sign bulk document signing via API using client-side signing, follow the steps mentioned below. These steps outline the APIs and user actions involved in signing multiple documents directly from the client side.

1. The signatory is identified via the access token provided in the API call, which means authentication is required before initiating the signing process. The access token must be issued directly to the signatory through authentication API.

2. If modifications are needed before signing, the Fill Form Fields API should be called beforehand. Note that any mandatory input fields must be completed for the signing process to succeed.

3. To determine which Signing Servers should be displayed based on a signature field’s level of assurance, the signature application must call the Get Signature Settings API. This API provides details of all available signing servers along with their corresponding levels of assurance.

4. The signature application needs to call Bulk Signing Pre Validation API. This API executes pre-signing validations for each document package and respectively returns any errors along with the list of tasks that the application needs to perform to complete the signing process.

5. To perform local signing using Go-Sign, the Load Applet API is called to initialize the Go-Sign service. This API returns a script that must be appended to an HTML element.

6. The script loads Go-Sign.js into the HTML document, enabling multiple functions to retrieve certificate chains.

7. Once the certificate list is retrieved, the application calls the Pre Bulk Local Signing API to initiate the processing of all packages. This API returns a transaction ID along with the signing status and any failed packages.

8. If the status is Pending the signature application periodically calls Bulk Signing Status API to check the status. Once the Data to be Signed (D2S) for all packages is received, the process continues.

9. When the D2S array becomes available, Go-Sign calls the “GoSign_SetD2S()” method to set the hash on ADSS, followed by the “GoSign_Process()” method to process the signature and return the signature bytes array.

10. The list of raw signature bytes, along with their corresponding package IDs is then sent to the Post Bulk Local Signing API to complete the signing process.

11. Finally, after signing, the Get Document Verification API can be used to retrieve the verification response.