The iProva Suite is a modular system, containing a collection of tightly integrated modules which all fit in the domain of quality, safety and risk management. From a technical point of view, iProva is a single package, which can either be deployed in a SaaS model or on premises servers at the customer location.
iProva contains a range of API’s, allowing other systems to interact with iProva. A common example is social intranet software, which retrieves and displays certain information from iProva.
Note that integrations with iProva already exist for various intranet solutions. Have a look at our intranet partner page for more information.
This diagram shows the modular architecture of iProva. Click on a module to get more information about its purpose, and to see which API’s are available for interaction with this module.
Front-end for end users
Content from core modules is made accessible to end users via keyword search, portals and personalized lists like “My tasks” and “My favorites”.
This is where the actual content is located.
All iProva modules share a common foundation which takes care of authentication, user management and so on.
iProva contains a mix of REST API’s, SOAP Webservices and Windows Communication Foundation (WCF) Services. Older parts of the API are implemented as SOAP Webservices or WCF Services, newer parts are implemented as REST API. Each of these API’s can be called from (almost) any platform, for example .NET, PHP, Java and JQuery.
The iProva API is an inseparable part of iProva. No additional licensing is required in order to use the API’s.
Customers with an active support & maintenance subscription for iProva have access to updates to iProva software, which can include improvements to the API.
The information provided on this website does always reflect the API features of the most recent version of iProva. This currently is version 5.14.
Starting with version 5.5, you can browse to /api in each iProva tenant (for example: https://organisation.iprova.nl/api). This page will give you access to local API resources and it will also inform you if the customer’s iProva is outdated and should be updated in order to take profit of all current API features.
Customers running iProva on-premises might not yet use the most recent version, resulting in a different (more limited) API feature set.
You can find out which iProva version the customer is running by clicking the “Go To” menu on the left and then the “Application management” menu link in the iProva user interface, the version is displayed at the bottom of the page. Each iProva API also contains a way to retrieve the version of iProva.
Customers with an active support & maintenance subscription for iProva are entitled to support on the iProva API.
Support is limited to inquiries about unexpected error messages and other API malfunctions.
Customers also have access to software updates which might include API improvements or bugfixes.
This kind of support can be requested via the Infoland Servicedesk.
When you are working as an (external) developer for a customer, please be aware that the Infoland Servicedesk will only accept service requests from their known contact persons; please ask your customer to contact the Servicedesk for you.
A support & maintenance subscription does not include programming guidance, assistance in solution design, or debugging of your code.
Such services are only available as paid services.
- Is your organization already using iProva and do you need additional services regarding the iProva API or other integration features?
Contact your account manager for more information or send us an e-mail.
- Are you an independent software vendor, interested in integrating your solution with iProva?
Feel free to contact us.