5th August 2026

Added Categorisation-as-a-Service (CaaS) and related API endpoints.

Partners who already hold banking data for a user can now create users, accounts, and transactions in DataOne so that data can be categorised and used across the platform. Supporting retrieve and consent endpoints are also available.

Create and update

• POST /v2/users — create a user when one does not already exist in DataOne
• PUT /v2/users/{userId} — update an existing user
• POST /v1/users/{userId}/accounts — create a CaaS account associated with that user
• POST /v1/users/{userId}/accounts/{accountId}/transactions — insert transactions into a CaaS account and initiate categorisation

Retrieve

• GET /v2/users/{userId} — retrieve a user
• GET /v2/users/search — search users
• GET /v2/users/recent — retrieve recently created users
• GET /v2/users/{userId}/accounts — retrieve all accounts for a user, including CaaS accounts
• GET /v1/jobs/{jobId} — monitor the status of a categorisation or other asynchronous job

Consents

• POST /v1/user-consents — create a user and generate consents for recipient partners

Account responses

Account responses from the GET and POST accounts endpoints now include a populated providerName field with the human-readable name of the financial institution, alongside the existing providerId.

For the full CaaS flow and schema requirements, see the Categorisation-as-a-Service guide.