Web Services API

infoXpert includes a full Web Services API which allows programmers to develop custom solutions based on the infoXpert Document Management Software.

infoXpert already provides seamless integration with a wide range of Finance, CRM, Property, Rating, Administration and GIS/Mapping products including: Technology One, Practical, MapInfo Exponare, InfoSphere, ContactTracker, Google Maps and CivicView.

Using the extensive range of Web Services API functions, you can easily create new applications and integrate your existing applications with infoXpert. You will be able to perform functions such as document retrieval, document search, user authentication, assign workflow and upload new documents. 

Key features & benefits of the infoXpert Web Services API:

• Deliver content to remote applications via its Web Services interface 
• Web Services API provides a programmable environment for organisations to deliver an  integrated platform for all their in-house applications 
• Standard Web Services Interface that can be called from remote servers to access infoXpert content 
• Integrate with both GUI (Windows Client) or Web based applications 

Integration Methods & Examples

Three of the most common methods of integration are:

1. Web Services API
This method of integration provides the most comprehensive level of integration. Not only does it allow retrieval from the eDRMS repository, but it also enables uploading of documents to the eDRMS repository.

(Click here to view the complete Web Services API command list.)

2. Linking Using URL and Folder / Document ID
This is the simplest (and easiest method) of integration using the infoXpert Folder or Document ID, which would mean the Folder / Document ID is held in the Third Party application.

3. Linking Using URL and Third Party ID Using Custom Property Set
This is similar to "Linking Using URL and Folder / Document ID" above except it uses the ID from the Third Party application that is stored in infoXpert as a Customer Property Set (e.g. property number, supplier ID, etc.). Therefore, it requires that the customer to store the ID of the Third Party record as a Custom Property Set on the relevant infoXpert Folder or Document.

Custom Meta Data "Lookup" Integration
In addition to the above integration methods, infoXpert provides the facility to use a table/view from a third party application as the source "lookup" when entering data in an infoXpert custom property field.

For example: a user can click on the "Lookup" button for custom Supplier field in infoXpert, which displays a list of matching records from the external Finance/Land Information System table in SQL Server, Oracle or MySQL.