Intelliflo Tech Blog

Currently our bulkvaluation API uses uppercase "Top" and "Skip":

After the change the API will accept lowercase "top" and "skip":

This change will align bulkvaluation API with the rest of our APIs and is scheduled to be deployed into production on the 25th of November. Please update your code to use lowerca

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:

• Fixed bug that caused a 500 internal error when requesting a manual fund via funds API
• Property "isVisibleToClient" has been added to new Plan API
• Fixed a bug that made it impossible to add dependant while using Tenant Client Credential (TCC) flow
  • A 500 internal server error was returned When a 3rd party app tried to POST a dependant through the API using tenant client credentials flow.
• Posting a relationship with type 'Employee,Employer' creates the relationship the other way around e.g. corporate client is 'Employee' and personal client is 'Employer'.
• Fixed an issue that gave a "403 Forbidden" on using PUT against any plan using new Plan API.

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.