We are changing our enum values for address type. 'Other' becomes 'Correspondence'. All pre-existing records of type 'Other' will be updated to 'Correspondence'
Correction of spelling mistake on 'PersonalProtectionPlan'
Current behaviour:
When POSTing (or PUT) a personal protection plan with benefit option 'terminalillnes' we will reject it as we currently only accepts the misspelled work 'terminalilness'
New behaviour:
we will accept the correct spelling and reject the misspelled word.
Properties to be added or removed for PensionDefinedBenefitPlan and PensionContributionDrawdownPlan discriminator:
The following properties has been added for PensionDefinedBenefitPlan and PensionContributionDrawdownPlan discriminator:
"guaranteedAnnuityRate " : "string" // string
The following property will be removed for PensionDefinedBenefitPlan and PensionContributionDrawdownPlan discriminator:
"guaranteedMinIncome" : {
"currency" : "string" // string
"amount" : "string" // string
}
Endpoint affected https://developer.intelliflo.com/apis?tags=plans
We will update you 4 weeks in advance of the deprecation of guaranteedMinIncome.
We are adding new properties on Client API for Trust and Corporate records. Please see Client API documentation
Intelligent Office and its APIs are constantly evolving, and we are now introducing a new way of how Plan API handles currency.
We are changing how IO and our APIs handle currencies and are introducing a preferred header for Plans. "Prefer: currency=base" will retrieve the plan in the base currency . By default, the API will return the plan in plan.Currency which can be any currency.
This new feature gives you the ability to record contributions, withdrawals, and valuations in plan currency which is different than the regional base currency. Currently, a Plan can be set to use a different currency but all underlying valuations, etc are in GBP within the API.
There is no contract change, but if you do not apply the preferred header there is a chance you might get a plan and its latest valuation in a currency you didn’t expect.
The changes are due to be implemented during Q2. This post will be updated when we have a exact date.
The following APIs will be updated to increase security and align them with our other APIs.
We have released our expenditure API for general availability after an extended period of internal testing of our own products. With Expenditure API you will be able to get more fact find data from your client records in IO or if you collect this type of data in your own system you can now post it back to IO.
We have added IntellifloStandard and IntellifloEnterprise to the list of providers on Documents API. Please make sure your code is updated to take these new values in consideration or you might experience errors while calling this endpoint.
