3. Sign Document

Executing the Document Signature Process

The portal orders that the signature process be executed via the browser.

The URL to which the browser is redirected must be extracted from the JSON response from the previous operation i.e. creation of document signature process. Specifically, the redirect URL is extracted from the URL field of the only element currently contained in the tasks.pending array of a recently created signature process (an element whose type is always UserBrowserTask). The execution of the signature process of a document is finished by sending a redirect response to the application/portal browser with which the user requested the signature.

GET stg-id.uaepass.ae/trustedx-resources/esigp/v1/signatures/{signature_id}/result

Path Parameters

NameTypeDescription

signature_id

string

Identifier of the signature creation process whose result you want.

Headers

NameTypeDescription

Authorization

string

Bearer <token>

Location: https://localhost:8080/callback?status=finished&signer_process_id=sp_c4eed0a1f478f72454803695d53c4c52

Example: GET /trustedx-resources/esigp/v1/signatures/123-1234567/result HTTP/1.1 Authorization: Bearer mF_9.B5f-4.1JqM

Response

If the operation is performed successfully, the body contains a JSON object with the following structure

{
"status": {string}, "details": { "message": {string}}
}
PropertyUsage

Status

Required

Result of the document signature process:

  • "finished": The process finished after all the documents were correctly signed.

  • "failed": The process finished but no document was signed owing to an error.

  • "failed_documents": The process finished. Some of the documents were signed, but not all.

  • "canceled": The process finished but no document was signed because the process was canceled.

details.message

Optional

Additional information on the result of the document signature process.

Last updated