The new intelliflo
tech blog

We've released a bug fix for productprovider API and aligned it with the rest of our APIs which means there is now a limit of 500 providers per request, and the default is 100 providers per request.

A note about our APIs and pagination

Most of our APIs support that returns big collections supports Top and Skip for pagination.

skip - Number of records to skip. Must be greater than or equal to zero.

top - The number of records to retrieve (default 100, max 500).

https://developer.intelliflo.com/docs/How-ToGuide#PagingApiResults

Please not that there might be some variations to default and max values for top. But never more than the above values.

This endpoint extends our Plan API (https://developer.intelliflo.com/apis?tags=plans) giving you the possibility to retrieve or add a collection of clients/person whose life has been covered by an assurance policy/plan.

The client address API at /v2/clients/{clientId}/addresses is being extended by adding property details to the address resource.  This post serves as notice to our developer community of this change, and while this is considered to be a minor update, it highlights some potential pitfalls that need to be avoided when we release this into production.  We'll discuss these below when we talk about the operations for managing them, but first things first - what do we mean by property details?

A new discriminator to our Plan API has been released that extends its capabilities to capture data that belongs to one of the following plan types:

Plans are a foundational resource in our public API and apart from Clients, probably the most important to our customers. Plans, as a concept, model the many varied financial products available in the market, both advised and non-advised, so in addition to being central to what our customers do, they are also fairly complex as a result.

The platform team have been working hard, releasing new APIs and fixes, quite steadily over the last few months and this will continue throughout this year and beyond. If you are on our mailing list then you may already be aware of the work that has been going on and that we recently announced the release of our new Document API for general availability. We are excited about this new Document API because we believe we have provided a simpler and more efficient way for customers to upload and download documents and have aligned these APIs with our flexible object storage architecture. Read on to find out more about the design and architecture or if you just want to know how to use them skip to How to use the APIs. 

We've been very busy at Intelliflo over the last few years re-engineering our platform. We are now releasing our public API which is a huge and exciting milestone in our journey that has included new products, a new platform architecture and an API first strategy. The intention to release an open API has been previously anounced and if you follow fin tech news or attended our 'Change the Game' conferences you may have already heard about our API and the significance this has in our sector. What you probably aren't aware of is the back story of how our API platform came to be and the engineering led journey we've been on over the last 6 years. This post serves as an open account of that journey. Since this is our first post on this blog it is also worth mentioning that this is a technology blog and is written by members of our engineering teams so expect the content to be technical in nature.