Signing document with Autenti service

A technical text field named External Document ID must also be added to the form. This field is crucial for the subsequent course of the process. It stores the document identifier (GUID) assigned by Autenti after the document has been successfully saved in the platform database.

According to the Autenti REST API documentation, make sure that Autenti has returned a valid GUID. If this identifier is missing, it means that the document has not been registered correctly, and the technical field will remain empty. Such a situation indicates an integration-side issue and prevents the signing process from continuing correctly.

Integration configuration should begin with creating two REST Web Service connections to the Autenti REST API. These connections are used to send PDF documents for signature and to handle authorization.

 Fig. 5. API connection configuration

The connections use the JWT Bearer grant authentication mechanism, described in detail in the Autenti documentation. To connect to Autenti, you must first generate a key pair. The public key must be converted to the JWKS format and configured in the API application on the Autenti side. The private key must be kept in the .PEM format, as it will later be used in the connection configuration in WEBCON.

Two connections must be created:

• connection with the PEM key – in this connection, enter the base URL of the service instance and provide the private key in .PEM format in the Client Secret field.

Fig. 6. Connection with the PEM key

• second connection – in this connection, enter both URLs and complete the Client ID and Client Secret fields.

Fig. 7. Second REST Web Service connection

In the connection configuration, provide the following URLs:

1. For the test environment:

• authorization service URL –  https://api.accept.autenti.net/api/v2/auth/token ,
• base service instance URL  –  https://api.accept.autenti.net/api/v2 .

2. For the production environment:

• authorization service URL –  https://api.autenti.net/api/v2/auth/token ,
• base service instance URL  –  https://api.autenti.net/api/v2 .

The above URLs are valid as of April 30, 2026, and may change in future versions of the Autenti platform. It is recommended to verify them in the official documentation before starting the configuration.

The next stage is to configure the action that sends the document for signature. In the example described here, the action was added in the Manager approval step. An automation should be added on the Accept path, and the appropriate SDK action should be placed inside it.

Fig. 8. Preview of the send document action

The configuration of the individual action sections is presented below:

Fig. 9. Send for signature action configuration

In the action configuration, indicate both previously created connections that use the JWT Bearer grant mechanism, as well as the email address of the user in whose context the action is executed in Autenti. At this point, you must also define two technical fields used by JWT Bearer for identification: Unique organization identifier and Unique user identifier.

In the Document properties section, indicate the fields containing the title and description of the document that will be sent for signature. This information will be visible in the body of the email message sent to the people invited to sign the document. Selecting the Send document as organization checkbox allows messages to be sent on behalf of the organization.

The next section concerns Attachments. Attachment selection can be configured in two ways:

• Category – specify the attachment group from which files for signature should be retrieved. Additionally, a regular expression can be provided to narrow down the filtering, for example to files with the .pdf extension.
• SQL – in this case, complete the field with an SQL query to the WFDataAttachmets table. The query should return the identifiers of the attachments intended for signature.

Fig. 10. Attachment selection

SELECT

ATT_ID

FROM WFDataAttachmets

WHERE

ATT_WFDID = {WFD_ID}

AND ATT_IsDeleted = 0

If only the attachment indicated in a specific form field is to be signed, the query can be further narrowed down, for example as follows:

SELECT

    ATT_ID

FROM WFDataAttachmets

WHERE

    ATT_WFDID = {WFD_ID}

    AND dbo.ClearWFElemID(ATT_Attribute1) = 1

    AND ATT_IsDeleted = 0

In the next section, define the key recipient fields that determine the data sent to the electronic signature service.

Fig.11. Recipient data

1. Recipient list
   • Select the Item list containing the data of the people who will participate in the document signing process. The columns of this list were discussed earlier in the article. Fields marked with an asterisk are mandatory.
2. Include signing order
   • This field is required if at least one row in the Item list contains the Approver role.

The last section in the SDK action configuration is Response. In this section, specify the fields in which the external document ID, the link to the document in Autenti, and the document status will be stored.

Fig.12. Output data

After configuring the action, you can go to the Portal and test the solution. To do this, create a new instance, complete the list of signers, and then follow the path to the Manager approval step.

Fig. 13. Form window

After approval by the supervisor, the document is sent for signature to the people specified in the Signers Item list. These people receive the following email message from Autenti:

Fig. 14. Content of the email from Autenti

The View and sign the document button is also a hyperlink that leads to the document that is ready to be signed. Clicking the link redirects you to the authorization page, where you need to enter the SMS code to unlock the document. If the Unlock via SMS option is not selected, the document is displayed immediately, without requiring authorization.

If the process includes the action for retrieving the signing link, the user can use the link available directly on the form, without having to open the email message. If the document has been locked using SMS, the action for retrieving links will not work.

Fig. 15. Document secured with SMS code

After entering the SMS code correctly, the document to be signed will be displayed along with the key details. After reading the document, click the Next button.

Fig. 16. Document to be signed

After clicking the hyperlink, you’ll be prompted to confirm your signature by entering a one-time code sent to your phone number. Entering a one-time code is required because, when registering the instance in the BPS Portal, additional SMS authentication was enabled for this user.

If this option is not enabled, signing the document requires no additional confirmation – simply click the Sign button to complete the process.

Fig. 17. Document - confirmation of signature

After entering the code, the system will display confirmation details about the document signing.

Fig. 18. Signed document screen

A confirmation of the completed document signing, along with a copy of the signed contract, will be sent to all individuals listed as signatories.

Fig. 19. Return mail

If the document is signed successfully, it will include a certificate and stamp verifying the authenticity of the signature.

Fig. 20. Autenti signature certificate

While the document is being signed in Autenti, the WEBCON instance remains in the Awaiting for signatures step. At this stage, additional actions can be configured and then triggered, for example, by using a Timer or buttons available in the menu, as shown in the screenshot below.

Fig.21. Action buttons in the menu

The Download status of signers action retrieves the document signing status in the context of each person and then saves it to the Item list in the Signature status column.

Fig.22. Configuration of the action for retrieving signers’ statuses

Another action that can be triggered at this step using a button in the menu is Send reminder. After it is executed, users receive a reminder message about the document awaiting signature.

Fig.23. Configuration of the action for sending a reminder

To complete the process, configure an action that checks the signature status of the entire document and then downloads the document once its status changes to COMPLETED. This automation should be added on the Check status path.

Fig. 24. Document download action preview

The authentication settings are the same as for the action used to send the document. In the Autenti ID field, indicate the field that stores the document identifier assigned by Autenti.

The next step is to configure the conditional step Is it signed?, which is preceded by the Check Status path.

Fig. 25. Configuration of the Is it signed? conditional step

If the document download action results in the value COMPLETED being provided in the Document status from Autenti form field, the instance is routed to the final step. Otherwise, the item will return to the Awaiting for signatures step.

The system can return different statuses retrieved from the SDK source:

• PROCESSING 
• COMPLETED
• SUCCESS
• REJECTED
• FAILED
• WITHDRAWN
• ERROR

In the Awaiting for signatures step, configure a Timer function that checks every hour whether the document has been signed.

Fig. 26. Timer function configuration

Set the operation mode to Path transition after action call. If no action is defined, the Timer function will attempt to move the document to the next step every hour.

After the action is successfully performed, the value COMPLETED appears in the Document status, indicating that the signature process has been completed and all participants have signed the document. As a result, the instance is forwarded to the final step, and the signed document is saved in the Signed category.

Fig. 27. Instance at the final step

Conclusion

The workflow described above serves as a sample implementation of the WEBCON add-on for integration with Autenti.

The source code for all add-ons is available on the official GitHub repository: https://github.com/WEBCON-BPS and is released under the MIT License.