---
updatedAt: 2025-09-19T11:26:11.000Z
agentTools:
  projectIndex: https://docs.atlar.com/llms.txt
---

# API Deprecations

***

title: Deprecation Policy
description: Learn how Atlar handles deprecations, including key terms, timelines, and current active deprecations.
-------------------------------------------------------------------------------------------------------------------

> ⚠️ **Important**
>
> When a product, feature, or API endpoint is **deprecated**, it enters a grace period during which it remains functional but should no longer be used.
> After this period, the feature is **decommissioned**, meaning it is removed and no longer supported.

> :blue\_book: Key term: ***Deprecated*** means a feature, API endpoint, behaviour etc is still available but should no longer be used. Reasons may include:
>
> * A better alternative exists, e.g. a new API endpoint.
> * The functionality is about to be decommissioned (removed).

<br />

> :blue\_book: Key term: ***Decomissioned*** means a feature, API endpoint, a field in a API request/response structure etc is no longer supported and may have been removed. Calling such an endpoint, or relying on deprecated properties in API responses may led to unpredictable behaviour.

# Active Deprecations

The following section lists deprecations, removals of functionality or changes in behavior impacting the Atlar API and products.

### /v1/accounts

**Deprecation notice date**: 2025-05-01
**Target demission date**: 2025-12-01

Replaced by v2 [/v2/accounts](https://docs.atlar.com/reference/get_financial-data-v2-accounts-id)

### /v1/transactions

**Deprecation notice date**: 2025-05-01
**Target demission date**: 2025-12-01

Replaced by v2 [/v2/transactions](https://docs.atlar.com/reference/get_financial-data-v2-transactions)

### /v1/credit-transfers

**Deprecation notice date**: 2025-05-01
**Target demission date**: 2025-12-01

Replaced by v2 [/v2/credit-transfers](https://docs.atlar.com/reference/post_payments-v2-credit-transfers)

### /v1/direct-debits

**Deprecation notice date**: 2025-05-01
**Target demission date**: 2025-12-01

Replaced by v2 [/v2/direct-debits](https://docs.atlar.com/reference/post_payments-v2-direct-debits)

### /v1/external-accounts

**Deprecation notice date**: 2025-05-01
**Target demission date**: 2025-12-01

Replaced by v2 [/v2/external-accounts](https://docs.atlar.com/reference/get_payments-v2-external-accounts-id)

### /v1/mandates

**Deprecation notice date**: 2025-05-01
**Target demission date**: 2025-12-01

Replaced by v2 [/v2/mandates](https://docs.atlar.com/reference/post_payments-v2-mandates)

### v1 Account.balance

**Deprecation notice date**: 2024-08-16
**Decomissioned date**: TBA
**Scope**: API `v1`, resource `Account`.

The property `Account.balance` is deprecated. Instead, use the API endpoint [List Balances](https://docs.atlar.com/reference/get_financial-data-v2-accounts-id-balances).

### v1 Transaction field `account.bank.name` and `account.bank.id`

**Decomissioned date**: 2023-08-14
**Deprecation notice date**: -
**Scope**: API `v1`, resource `Transactions`.

Transactions impacting accounts created after the effective deprecation date will not have the fields `account.bank.name` and `account.bank.id` populated. The values will be an empty string. Note though that `account.bank.bic` will still be populated when available.