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.
The new intelliflo
tech blog
Christofer Andersson
Recent Posts
By Christofer Andersson
10/08/20 15:55
We are adding new properties on Client API for Trust and Corporate records. Please see Client API documentation
By Christofer Andersson
20/07/20 14:56
The following APIs will be updated to increase security and align them with our other APIs.
By Christofer Andersson
02/03/20 10:53
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.
By Christofer Andersson
10/02/20 21:43
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.
By Christofer Andersson
28/01/20 10:27
As part of Intelliflo’s ongoing work to secure our platforms, we will be disabling TLSv1.0 and 1.1 on all endpoints on February 14th 2020.
By Christofer Andersson
16/01/20 16:30
By Christofer Andersson
20/12/19 15:16