Description
Compared to the previous example, added to the integration is:
- Result url
- Delete document service
What is improved compared to the Example 1 is that information about the document being signed is transferred to the Portal. The Portal now knows that the document was signed
and the status has changed and therefore can determine exactly when the document was signed.
In this example, we assume that the Portal has prepared web page where user is redirected after signing the document.
How it works
We are again sending a PDF through the Create signature Request service, that does not have precisely defined signature places. In addition, a resulturl parameter is defined in the service, which is called when the document is signed and closed.
The response, as in Example 1, is the url of the document for signature that the signer opens in a web browser.
After signing and confirming the signature (or after canceling the signing), the signer is redirected to the resulturl defined when calling the Create signature Request service. When
redirecting the signer to the resulturl, OKdokument transmits information about the signing statue (not the state of the document):
- Success – the signer has confirmed the document
- Cancel – the signer did not sign the document (pressed the cancel button)
The signed document can be downloaded and saved in the Portal using the Download document service.
After downloading the signed document, the document is deleted by calling the Delete document service.
