ANVA is an important source of data for its customers. Through various methods, we have met the need to be able to link with our software in the past. However, the desire to exchange data in an even easier way remained. ANVA's API strategy fulfills this wish and together we take the next step towards better data quality.
ANVA's software may be fairly complete, but we do not provide a total solution that can fulfill all of our customers' needs. In fact, we deliberately choose to limit ourselves to the things we are good at and outsource other things to partners. For example, the data in ANVA is indispensable to complete solutions from partners and customers. At the same time, we increasingly see the need for a Single Point of Definition, where all data is stored and accessed in one place. Now that data quality is high on the agenda of parties such as the Dutch Association of Insurers, you quickly see that both the quality and connectivity of data are important agenda items for now and in the future.
The ability to easily interface with ANVA's software is one of the most frequently heard needs during customer sessions. To increase the connectivity of our software while standardizing technological links, software engineers at ANVA are working on APIs. An API (Application Programming Interface) is a software link that allows two applications to communicate with each other. The standardized way to exchange data allows you to connect systems and use ANVA's established business logic. This integration eliminates the need to duplicate data. To give ANVA's customers the scope to set up their IT landscape in the best possible way, the importance of interconnections is great. Indeed, without these essential links, it is impossible to create an integration that optimally facilitates users from start to finish.
ANVA's move to a cloud-based software application (ANVA Hub) also resulted in the decision to use APIs as the foundation from day one. This so-called API-first approach puts API links at the heart of ANVA Hub's IT landscape. By decoupling the front and back end (front and back end) of the software, it became possible to base the front end entirely on the APIs modeled in the back end. This allows us to offer users all freedom in the future, with of course some caveats around contractual obligations, licenses and user fees. The completely customizable puzzle this creates offers a great diversity of possibilities and, possibly in combination with other applications, results in a solution that suits everyone.
For the API-first approach to succeed, many technical steps have already been taken in recent months. The first step involved setting up authorizations and authentications using the open ID connect protocol. With ANVA Hub, it is possible to manage the rights of a person and/or organization within the relevant application. This allows the application, through the issued set of permissions to both an application and the user, to extract specific data from the system. A very nice step to comply with the need to know principle, which means that users only have access to data they really need. Gradually, we are replacing all existing links with APIs. We are taking the first step by launching a developer portal where we will make the first APIs available.
