Transact Web Services API

Ephesoft Transact’s OpenAPI-Compliant web services provide a simple method for real-time integration and exposure of Ephesoft Transact capabilities to external applications, allowing developers to embed advanced capture features in their own solutions without having to display the Transact user interface.

Ephesoft provides over 60 Transact web services to perform advanced capture actions in your custom applications. These web services perform tasks that range from simple actions like determining which batch instances can be seen by an individual user, to performing complete OCR/classification/extraction procedures on a collection of documents.

Ephesoft Transact web services support the self-documenting feature of the OpenAPI Specification v2.4.0 (formerly known as the Swagger Specification). This means that tools like Swagger UI can be used to browse the collection of web services and view detailed documentation for each web service. The Swagger UI tool is bundled with Ephesoft Transact, and can be accessed by navigating to the following URL in your Transact instance:

http://<server_name>:<port>/dcma/rest/swagger-ui.html

Navigating to this URL will take the user to the Ephesoft Transact Web Services Explorer, as shown below. This interface lists all Ephesoft Transact web services on a single page, allowing both seasoned developers and “citizen developers” to browse and navigate through the Ephesoft Transact web services available within their server.

Ephesoft Web Services Documentation Screen

This interface also allows the user to review detailed information about each web service. Clicking a web service in the Web Services Explorer allows you to drill further into the web service to view additional details, as shown below.

Ephesoft Web Services Implementation Notes

The overall Ephesoft Transact OpenAPI-compliant web services definition file for all API endpoints is represented in JSON format. This definition file can be found at the following location in your Transact instance: http://<server_name>:<port>/dcma/rest/v2/api-docs.json

Ephesoft Transact Web Services Optimized for Workflow Engines

All Ephesoft Transact web services support the self-documenting capabilities of the OpenAPI Specification, but only two Ephesoft Transact web services, v2/ocrClassifyExtract and v2/ocrClassifyExtractBase64, provide simplified JSON responses, allowing them to be embedded into workflow engines like Nintex and Microsoft Flow. These minimized JSON responses have a smaller footprint and improved interoperability. An example of this minimized JSON response is shown below.

Minimized JSON Example

These two web services have been optimized specifically for advanced workflow engines. See the following links for more information about these two web services:

Because they support minimized JSON responses, these two web services can be fully integrated into advanced workflow engines such as Nintex or Microsoft Flow. These tools allow users to develop complex workflows that can integrate different products and services together, enabling decision-making processes with or without human intervention.

For example, a workflow can easily be constructed to monitor Box to look for any new invoices created in the “Incoming” folder. When a new invoice is created in that folder, the v2/ocrClassifyExtract web service can extract the invoice amount from the invoice and feed that data into a decision tree. Invoices with amounts of $1000 or less can be approved automatically and routed to a “Processed” folder in Box. Invoices with amounts greater than $1000 can trigger a notification for an employee to review and approve the invoice before releasing it to the “Processed” folder.

The following document provides detailed information on how the new v2/ocrClassifyExtract web service can be integrated into complex workflow designs using Nintex:

Integrating Transact Web Services with Nintex

Note: Currently we support only basic authentication for Transact web services (base 64 encoded user name and password). Token-based authentication usually used with SAML, OAuth and other Single Sign-On authentication frameworks is not supported.