Go>Sign signing
Last updated
Was this helpful?
Last updated
Was this helpful?
To perform Go>Sign signatures via API using client-side signing, follow the steps mentioned below. These steps guide you through the required API calls and user interactions needed to complete the single document signing process on the client side.
The signatory is identified via the access token provided in the API call, which means is required before initiating the signing process. The access token must be issued directly to the signatory through API.
If modifications are needed before signing, the API should be called beforehand. Note that any mandatory input fields must be completed for the signing process to succeed.
To determine which Signing Servers should be displayed based on a signature field’s level of assurance, the signature application must call the API. This API provides details of all available signing servers along with their corresponding levels of assurance.
To perform local signing using Go-Sign, the API is called to initialize the Go-Sign service. This API returns a script that must be appended to an HTML element.
The script loads Go-Sign.js into the HTML document, enabling multiple functions to retrieve certificate chains.
Once the certificates list is retrieved, the application calls the API to obtain data to be signed(D2S) and a transaction ID.
The “GoSign_Process()” method is then triggered automatically to generate the signature and return the signature bytes.
Finally, the obtained signature bytes are placed on ADSS using the transaction ID, and the API is called to complete the signing process.
After the signing process is complete, if the signatory is the final signer, the API must be invoked. Without this step, the document will remain in an "In Progress" state for the owner. Once the API is called, the status updates to "Completed."
Finally, after signing, the API can be used to retrieve the verification response.