userId has been deprecated from the GET/authorising-user endpoint. userId is now under the GET/account-access-consents endpoint. This allows links a consent to a particular Tapico user ID.

userId has been added to the GET/account-access-consents endpoint and deprecated from the GET/authorising-user endpoint. This allows links a consent to a particular Tapico user ID.

Tapico Entity ID {entity}.id is now consistent across authorising users. Previously the Tapico Entity ID would differ for the same underlying source entity when the same entity is accessed via different consents — e.g. distinct authorising users who have access to the same account on the same platform.

The launchpad SDK has been updated to allow end-users to search for Apps that they are currently unsubscribed too. Making it easier for end-users to find new Apps and for your Apps to get in front of new end-users.

We've added some new properties to the response payload of the GET /external-accounts endpoint relating to the associated agent:

We've added some new properties to the response payload of the GET /customers endpoint, specifically for Individual type customers:

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 ServicerAccount Servicer - The entity that holds the account(s) that contains your end-user's account information, e.g. a bank like Natwest or a financial institution like Aviva. Tapico facilitates the connection between your application and the account servicer..

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