The 12th beta release coincides with an upcoming soft launch of our first App Store alongside a partner platform. As well as the usual security and general improvements this release introduces the “Tapico Help Centre” that users of the Universal API can use to raise and track issues.
Universal API - Breaking Changes
Unfortunately any existing consents will have to be reran.
GET / customers - Notification of pending breaking change
The schema of the universal API can now support customers of type Organisations (EG: Companies, trusts, charities etc).
NOTE: This is a breaking change but it is disabled. There is a dependency on a downstream service. Separate communications will be announced with sufficient lead time before the date it will be deployed. We encourage existing applications that rely on the customers endpoint to review the spec now to understand how these changes could impact them.
The Tapico Help Centre
Users can raise and track issues they encounter with Tapico’s API and other services.
More details can be found here
URL taxonomy in the Application - Basic Detail page
The URLs on the app basic details page are now grouped into Functional URLs and OAuth.
The following URLs only accept URLs derived from the organisation's registered domain.
Consent Request Callback URL
NOTE: In order to edit an existing apps in sandbox you will have to first update the above URLs with your Organisations registered domain. If no domain is registered against your organisation you can add one.
Entity name length limitation
The input value of the names for the following entities has been limited to 100 characters.
API documentation improvements
Centralised public face Developer Docs page
API Reference Document updated to detail Enumerations and payload examples
GET /account-access-consents endpoint
Added lastRefreshDateTime attribute.