---
title: "Get account transaction"
method: GET
path: "/companies/{companyId}/connections/{connectionId}/data/accountTransactions/{accountTransactionId}"
tags: ["Account transactions"]
---

# Get account transaction

`GET /companies/{companyId}/connections/{connectionId}/data/accountTransactions/{accountTransactionId}`

The *Get account transaction* endpoint returns a single account transaction for a given accountTransactionId.

[Account transactions](https://docs.codat.io/accounting-api#/schemas/AccountTransaction) represent bank activity within an accounting software. All transactions that go through a bank account are recorded as account transactions.

Before using this endpoint, you must have [retrieved data for the company](https://docs.codat.io/codat-api#/operations/refresh-company-data).

## Path parameters

- `companyId` string, uuid, required — Unique identifier for your SMB in Codat.
- `connectionId` string, uuid, required — Unique identifier for a company's data connection.
- `accountTransactionId` string, required

## Response `200`

Success

- AccountTransaction, nullable — > **Language tip:** In Codat, account transactions represent all transactions posted to a bank account within an accounting software. For bank transactions posted within a banking platform, refer to [Banking transactions](https://docs.codat.io/banking-api#/operations/list-all-banking-transactions). ## Overview In Codat’s data model, account transactions represent bank activity within an accounting software. All transactions that go through a bank account are recorded as account transactions. Account transactions are created as a result of different business activities, for example: * Payments: for example, receiving money for payment against an invoice. * Bill payments: for example, spending money for a payment against a bill. * Direct costs: for example, withdrawing money from a bank account, either for cash purposes or to make a payment. * Direct incomes: for example, selling an item directly to a contact and receiving payment at point of sale. * Transfers: for example, transferring money between two bank accounts. Account transactions is the parent data type of [payments](https://docs.codat.io/accounting-api#/schemas/Payment), [bill payments](https://docs.codat.io/accounting-api#/schemas/BillPayment), [direct costs](https://docs.codat.io/accounting-api#/schemas/DirectCost), [direct incomes](https://docs.codat.io/accounting-api#/schemas/DirectIncome), and [transfers](https://docs.codat.io/accounting-api#/schemas/Transfer).
  - `id` string — Identifier of the direct cost (unique to the company).
  - `transactionId` string, nullable — Identifier of the transaction (unique to the company).
  - `note` string, nullable — Additional information about the account transaction, if available.
  - `bankAccountRef` BankAccountRef — unresolved $ref
  - `date` string — In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>. Date and time fields are formatted as strings; for example: ``` 2020-10-08T22:40:50Z 2021-01-01T00:00:00 ``` When syncing data that contains `DateTime` fields from Codat, make sure you support the following cases when reading time information: - Coordinated Universal Time (UTC): `2021-11-15T06:00:00Z` - Unqualified local time: `2021-11-15T01:00:00` - UTC time offsets: `2021-11-15T01:00:00-05:00` > Time zones > > Not all dates from Codat will contain information about time zones. > Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced.
  - `status` 'Unknown' | 'Unreconciled' | 'Reconciled' | 'Void' — The status of the account transaction.
  - `currency` Currency — unresolved $ref
  - `currencyRate` CurrencyRate — unresolved $ref
  - `lines` AccountTransactionLine[], nullable — Array of account transaction lines. — unresolved $ref
  - `totalAmount` number — Total amount of the account transactions, inclusive of tax.
  - `metadata` Metadata
    - `isDeleted` boolean, nullable — Indicates whether the record has been deleted in the third-party system this record originated from.
  - `modifiedDate` string — The date when the record was last fetched from the accounting software, commerce software, or open banking provider and updated in Codat’s data cache. Use it to identify and retrieve records that have changed since your last fetch. For example, filtering `modifiedDate` to today will provide new records updated in Codat today. This date is populated for all data types except for attachments, balance sheets, company information, and profit & loss reports ([read more](https://docs.codat.io/using-the-api/modified-dates#modified-date)). In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>.
  - `sourceModifiedDate` string — The date when a record was last modified in the accounting software, usually by the business or a business process. For example, when payments are made against an invoice. It is not populated ([read more](https://docs.codat.io/using-the-api/modified-dates#source-modified-date)) when: - Pulling attachments - The accounting software does not provide modification dates for a data type - A record has been deleted from the source platform and Codat doesn't have a record of when the deletion occurred - A record has been voided. For certain platforms that soft delete records, `isDeleted` metadata is used to identify void records In Codat's data model, dates and times are represented using the <a class="external" href="https://en.wikipedia.org/wiki/ISO_8601" target="_blank">ISO 8601 standard</a>.

## Other responses

- `401` — Your API request was not properly authorized.
- `402` — An account limit has been exceeded. The type of limit is described in the error property: - You have exceeded the 50-company limit that applies to a Free plan. Delete any companies you no longer need and retry the request. - The requested sync schedule is not allowed. You requested an hourly sync schedule but this functionality is not included in the Free plan. - Your Free account is older than 365 days and has expired. Contact support@codat.io.
- `403` — You are using an outdated API key or a key not associated with that resource.
- `404` — One or more of the resources you referenced could not be found. This might be because your company or data connection id is wrong, or was already deleted.
- `409` — The data type's dataset has not been requested or is still syncing.
- `429` — Too many requests were made in a given amount of time. Wait a short period and then try again.
- `500` — There is a problem with our server. Please try again later.
- `503` — The Codat API is temporarily offline for maintenance. Please try again later.

---

[API](https://skmtc.net/codatio/apis/accounting-api.md) · [All operations](https://skmtc.net/codatio/apis/accounting-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/codatio/accounting-api/revisions/21d41189c461/schema)