Verification URLs
For tasks created in the REST API, verification is configured in projects. For detailed instructions, see Adapt the sample project for use with the ABBYY FlexiCapture Cloud REST API. You can integrate the verification UI into third-party systems via an<iframe> element, eliminating the need for additional tenant authentication. To direct verification operators to the data to be verified, unique URLs are used.
A verification URL can only be opened once in one browser window; that is, documents from one task can only be verified by one user at a time. The total number of tasks that users can open in the verification UI is determined by the licensing restrictions of a tenant (see License parameters for details).
Open the verification UI
To open the verification UI for a REST API task:1
Create a task
Using the REST API, create a document processing task.
2
Track the task status
Track the task status. The verification UI can only be opened for tasks with the WaitForAction status. For more information about task statuses, see ABBYY FlexiCapture Cloud REST API task status.
3
Create a verification URL
Get the Here,
verification_id from the task object, and then use it to build a URL in the following format:{api-portal-host} is your region host and {verification_id} is the verification identifier. For example:4
Open the URL
Open the verification URL in a browser or via an
<iframe> element.No additional authentication is required to open verification URLs.
5
Wait for the completion message
Wait for the
FC_Verification_TaskClosed message from the <iframe> element. This message signals that the verification has been completed (see iframe element events below for details).6
Download the results
Track the task status. You can download the files after the processing is completed.
<iframe> element events
The table below lists the possible <iframe> events:
Once a message has been received from the
<iframe> element, the verification UI can be closed and the user can be returned to the third-party system.