RAS signing

To perform RAS signatures via API using server-side signing, follow the steps mentioned below. These steps outline the necessary API calls and conditions to successfully complete a single document signing operation through the server.

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. Signature applications can use Sign Document API to sign a single document. This API will respond with a "Pending" status if all validations are done. At this point, the server will send the authorization request to the client device.

5. Authorization Signing Request Status API will be used to get the status of signing that were processed by the previous API call (repetitive call until status become COMPLETED).

   1. You will get verification object in the response of this API if the request parameter skip_verification is not passed or set to false. (on success)

6. After the signing process is complete, if the signatory is the final signer, the Finish Processing 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."

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