Skip to main content
A list of all active or completed transactions can be used to:
  • Track active transactions currently at the Manual Review stage.
  • Obtain a manual review link for active transactions.
  • Download the result files of completed transactions.
  • Pick up finished transactions in the order they completed, without tracking which ones you have already collected.
You can get a list of transactions with their identifiers using the Vantage API. You can use Skill Monitor to apply more advanced filters.

List of active transactions

To get a list of active transactions, send a GET request to the transactions/active resource. In the request body, specify the following parameters: Sample request:
The response to a request with a specified skill identifier will contain a JSON file similar to the following:
The response to a request with a specified stage and action will contain a JSON file with all active transactions similar to the following:
You can also obtain a Manual Review client link for currently active transactions. To do so, send a GET request to the transactions/<transaction_id> resource with the transaction identifier in the request URI. Sample request:
The response will contain code similar to the following:
The manualReviewLink key will contain a link to the web interface of the Manual Review client and a Vantage access token, if manual review is required. This link and token can be used to review and correct the classification and field extraction results of a particular transaction. The provided link is valid for 168 hours, after which a new link should be created and obtained for another period of 168 hours using the same method. For more information, see Integrating manual review.
Users authorized via this link will not be able to view or modify any other documents or transactions.

List of completed transactions

To get a list of completed transactions, send a GET request to the transactions/completed resource. In the request body, specify the parameters: The response will contain a JSON file with all completed transactions and a number of processed pages similar to the following:

Picking up finished transactions

The transactions/completed resource returns every completed transaction in a date range, so an integration that collects results has to keep its own record of which transactions it has already handled. The transactions/pending-pickup resource removes that bookkeeping. It returns finished transactions that you have not yet deleted, in the order they finished, and a transaction drops out of the list once you delete it. A typical pickup loop looks like this:
  1. Send a GET request to transactions/pending-pickup.
  2. For each returned transaction, download the result files. See Downloading source files and result files.
  3. Delete the transaction with a DELETE request to transactions/<transaction_id>. This removes it from the pickup list.
  4. If the response contains a nextCursor, repeat from step 1 with that cursor to get the next page. When nextCursor is empty, you have reached the end of the list. Wait for your polling interval and start again without a cursor.
In the request, specify the following parameters: Sample request:
The response contains the finished transactions and a cursor for the next page:
To get the next page, pass the cursor back in the request:
Keep the following in mind when building a pickup integration:
  • Delivery is at least once. Every finished transaction appears at least once, but in some conditions, such as the few minutes between a DELETE request and the actual removal, the same transactionId can appear more than once. Store the identifiers you have already processed and skip any that appear again.
  • Pick up results before they expire. A transaction stays in the pickup list only as long as its data is kept in Vantage. If the transaction is removed by the data retention policy before you pick it up, it no longer appears in the list. Historical records remain available in the Reporting API.
  • Permissions. The request returns transactions only for skills that the authenticated user has permission to access, the same as for transactions/completed.
  • Polling interval. The pickup list is pull-only. Poll it on a schedule that matches how quickly you need results, rather than continuously. For general guidance, see Polling.