Document Simple API

This solution is fairly similar to the Document Simple Forensic API. It provides a Simple Electronic Signature (SES) with an audit trail, but in this case there won’t be an OTP identification, and the audit trail is not forensic.

During the integration inside a Company’s process, to create a signature using this API, one must call the endpoint [operation/createSignature], although in this context using the property isForensic = false.

The following diagram shows, at a certain level of abstraction, how the signature interaction takes place once WT is integrated within the company's process.

  1. A user/signer wants to sign a document.

  2. The company creates a signature using the endpoint createSignature with property isForensic = false.

  3. WT initialises the signature entity that will represent the interaction during the whole process.

  4. WT will return to the caller the created signature object containing the forwarding URL (F-URL) to which the company will redirect the signer.

  5. The company's Web Server responds to the HTTP request sent by the user in step 1 with an HTTP redirectionF-URL.

  6. The signer’s browser visits the F-URL to WT.

  7. WT will request the corresponding signature interaction for the effective URL (E-URL) where the page with the PDF will be served.

  8. The E-URL is returned to WT.

  9. WT will respond to the signer’s request in step 6 with an HTTP redirection to E-URL.

  10. The signer's browser visits the E-URL served from the secured container where the signature will effectively take place.

  11. The secured container responds with the page containing the PDF to be signed.

  12. The signer will interact with the page by viewing the PDF, fill-in fields, and drawing the signature (depending on the configuration), and finally will press the button that will conclude this interaction.

  13. The secured container will respond to the signer with an outcome page.

  14. The container concludes the signing session.

  15. The container updates the signature interaction with the signature-specific data.

  16. If configured, the outcome page may redirect the signer to a company outcome page.

  17. The company will respond with its outcome page.

  18. Asynchronously, WT will perform the finalisation of the interaction by applying the signatures to the PDF and by creating the Audit Trail that will accompany the signature.