### April 22, 2026

🆙 Added `UserId` field to `Consent` schema [Webhook notifications](https://docs.atto.co/content/docs/guides/platform-integration/notifications#v2-webhooks) 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](https://docs.atto.co/content/docs/guides/platform-integration/notifications#v2-webhooks) 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`


### April 20, 2026

🆙 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](https://docs.atto.co/content/docs/guides/platform-integration/null-value-handling) for more details.

### April 14, 2026

🆕 Added `Balance` field to API - [Returns a list of transactions for an account for a consent](https://docs.atto.co/content/apis/bank-data-(stored)/paths/~1stored-data~1v1~1consents~1%7Bconsentid%7D~1accounts~1%7Baccountid%7D~1transactions/get). 
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`.

### March 31, 2026

🆕 Added Transfer object to API - [Returns a list of transactions for an account for a consent](https://docs.atto.co/content/apis/bank-data-(stored)/paths/~1stored-data~1v1~1consents~1%7Bconsentid%7D~1accounts~1%7Baccountid%7D~1transactions/get).

- 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.


### March 17, 2026

🆕 Added `CounterPartyName` field to API - [Returns a list of transactions for an account for a consent](https://docs.atto.co/content/apis/bank-data-(stored)/paths/~1stored-data~1v1~1consents~1%7Bconsentid%7D~1accounts~1%7Baccountid%7D~1transactions/get). 
CounterPartyName: Name of the counterparty involved in the transaction (if available) — the creditor for debits and the debtor for credits.

### August 8, 2025

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

### May 19, 2025

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

### November 20, 2024

✅ 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

### November 05, 2024

🆕 Atto Score API (Beta) endpoint released

### October 30, 2024

🆕 HSBC MiVision (UK) added to Connect coverage

### September 18, 2024

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

### September 16, 2024

🆕 Smile bank (UK) added to Connect coverage