{"id":31705,"date":"2018-11-20T23:27:32","date_gmt":"2018-11-21T07:27:32","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/developers\/web-services-api\/transact-web-service-definitions\/"},"modified":"2021-06-11T12:45:42","modified_gmt":"2021-06-11T19:45:42","slug":"transact-web-service-definitions","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/developers\/web-services-api\/transact-web-service-definitions\/","title":{"rendered":"Web Service Definitions and Code Samples"},"content":{"rendered":"

Overview<\/span><\/span><\/h2>\n

The Ephesoft Transact web services API provides a simple method for real-time integration and exposure of Ephesoft processes to external applications. This allows developers to embed and employ advanced capture capabilities and technologies in content management systems and other workflows.<\/p>\n

Ephesoft Transact web services support the OpenAPI standard, and the Ephesoft Transact Web Services Explorer utilizes the Swagger interface to enable documentation and testing for Ephesoft Transact web services. Web services that return XML responses can be tested directly in the Swagger interface, but due to a limitation of the Swagger interface, web services that return non-XML responses cannot. Refer to the\u00a0Swagger\/OpenAPI Capabilities<\/b>\u00a0section of each web service for information about whether a web service supports being tested directly in the Swagger interface or not. All Ephesoft Transact web services, including those that can’t be tested in the Swagger interface, can still be tested in other web service testing tools, such as Postman.<\/p>\n

This document provides a brief description of each web service followed by a code sample showing how the web service can be used.\u00a0 All code samples are written in Java and utilize the Apache Commons HttpClient library.<\/p>\n

Web services on this page are grouped into the following sections:<\/p>\n