RAS signing

To perform RAS bulk document signing via API using server-side signing, follow the steps mentioned below. These steps detail the API calls required to sign multiple documents in a single 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. 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. The signature application needs to call Bulk Sign Packages API. This API will sign/sign & share and share multiple documents without displaying the documents to the end user. This API will respond with a "Pending" status. At this point, the server will send the authorization request to the client device.

6. Bulk Signing Status API will be used to get the status of a specific bulk signing transaction along with the details of document packages that were processed by the previous API call (repetitive call until status becomes COMPLETED).

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