Whilst breaking changes are kept to a minimum when they do occur a new version of the Tapico API will be created. See the API Versioning guide for more details.

The dynamic error messages returned by the Tapico API are now grouped into standardised error codes. A complete list can be found on the error code guide.

The GET / customers endpoint now returns an individual's target retirement age and/or date if held by the Account Servicer.

You can now search for a particular record by name on the following endpoints by using the search query parameter:

Applications are now required to provide a default Landing Page URL as part of the Basic Details. This Landing Page URL is used in cases where deep links cannot be used.

If your application does not support a self service onboarding journey for new users. You can now add an email address to receive the details of prospect customers should they select your application in a partner app store.

To allow your application to stay up to date with events relevant for your integration we have introduced webhooks. This provides a more responsive and more scalable alternative to polling (periodically checking) for updates. We will be continuing to add relevant webhook events over time. In the meantime here is the list of webhook events we have added under this release

We have added additional filter parameters to the consent and payment results tables in the Tapico Developer Portal

We have completed a major overhaul of our Developer Documentation and API Reference Specification. They along with our change log are now centralised under the docs.tapico.io website.

We have made the following improvements to our developer portal: