⚠️ Marked the section "Data API" as obsolete. This content is no longer maintained. To access user bank account data, please refer to the Stored Data API section.

🆙 Added IncomeForMonth and AffordabilityForMonth to MonthAffordabilities field of Stored Data API > Affordability. These represent the actual recorded income and affordability for each given month, as opposed to the existing fields which are working values for determining the forward-looking estimates for income and affordability. MonthAffordabilities are now returned in descending date order.

🆙 Added VerificationError to Credit Data > Accounts. This will be populated if the end user encountered any error during the credit information sharing process and we were not able to retrieve the user's credit report as a result, otherwise it will be null.

🆙 Added UserId field to V2 Email notifications that uniquely identifies an end-user in our system.

🆙 Added UserId field to Connect Integration Parameters which will allowing linking existing consents under the same user id. This provides a way to add additional consents for an existing user.

🆕 Added Get User Report endpoint to Stored Data API for retrieving PDF containing all the data held for a user.

🆙 Updates have been made to the User Report design:

• Updated tables to monospace font for visual clarity

• Added more details to the User Summary section:

  • Avg Income
  • Avg Affordability
  • Min EoD Balance
  • Max EoD Balance

• Added more details to the Consolidate Income / Affordability section:

  • Total Average Income
  • Total Average Affordability

• Added a new Credit Profile section which will be available for users that went through the Credit Information enabled connection journey. This shows:

  • Number of missed or defaulted payments
  • Estimate of total unsecured debt
  • Details of any accounts tied to the user
  • Negative indicators such as CCJs, insolvencies, and Cifas filings
  • MODA details for any key changes to the user's credit record

• Added highlighting to any data points which indicate a potential credit risk such as negative affordability, overdraft usage, defaulted accounts, etc.

• Added application level configuration that allows for control of which sections to output when generating User Reports. The sections available are as follows:

  • User Summary
  • Credit Profile
  • Income and Affordability
  • Account Overview
  • Significant Transactions
  • Statement

  Multiple configurations can be supported for an application and each will be available for use via both Dashboard export function and the new dedicated API endpoint.

  If no custom configurations are created then by default all sections will be output.

🆙 Added UserId field to Consent schema Webhook notifications that uniquely identifies an end-user in our system. This will be available for any notifications sent after April 22, 2026.

🆙 Updates have also been made to Webhook notifications to emit null values for fields without value rather than omitting the fields entirely.

This includes the following fields of the Consent schema webhooks:

• ConsentEnd
• ConsentJourney
• DataAvailability

🆙 Updates have been made to various API response models to emit null values for fields without value rather than omitting the fields entirely from responses.

This includes:

• Parties field of Account
• MerchantDetails and EnrichedData fields of Transaction
• ConfidenceScoreFlags field of IncomeVerification's IncomeStreamsSummary

See our page on Null Value Handling for more details.

🆕 Added Balance field to API - Returns a list of transactions for an account for a consent.
Balance: The running balance (if available) on the account as of the date and time of this transaction.

Running balances will be available for accounts connected after April 14, 2026 and for any account that has been refreshed since April 14, 2026. For other accounts this field returns null.

🆕 Added Transfer object to API - Returns a list of transactions for an account for a consent.

• Transfer represents a transaction between two associated accounts, it can be nullable and will contain the following properties
  • AssociatedAccountId(string): this will be the account ID that the transfer has either gone to or come from, depending on whether this is a debit or credit
  • PairId(int): this is the Id which both the transaction out and transaction in will share.

🆕 Added CounterPartyName field to API - Returns a list of transactions for an account for a consent.
CounterPartyName: Name of the counterparty involved in the transaction (if available) — the creditor for debits and the debtor for credits.

🆕 Added GET /connect/users/v1/{userId}/accounts to Credit Information API to retrieve list of credit bureau accounts for a user.

🆕 Added GET /end-of-day-balances to Stored Data API to retrieve end-of-day balances for an account.

✅ New Atto Stored Data API balances endpoint released
✅ New endpoint is returning nullable object in case bank hasn't returned any value for available or current balance

🆕 Atto Score API (Beta) endpoint released

🆕 HSBC MiVision (UK) added to Connect coverage

🆕 API Rate limits introduced for Atto APIs
🆕 Change management page introduced in Atto Developer documentation

🆕 Smile bank (UK) added to Connect coverage