---
title: "Get a transaction by transaction identifier."
method: GET
path: "/v1/accounts/{accountId}/transactions/{transactionId}"
tags: ["Transactions"]
---

# Get a transaction by transaction identifier.

`GET /v1/accounts/{accountId}/transactions/{transactionId}`

## Path parameters

- `accountId` string, required
- `transactionId` string, required

## Headers

- `sessionId` string, uuid
- `authorizationId` string, uuid

## Response `200`

Request was fulfilled and transaction is returned.

- Transaction
  - `amount` number, double, nullable
  - `categoryId` integer
  - `title` string, nullable
  - `date` string, nullable
  - `info` string, nullable
  - `transactionId` string, nullable
  - `partner` string, nullable

## Other responses

- `204` — Indicates that the request was performed but no content is returned.
- `206` — Successful response, with a partial representation of a list of transactions.
- `400` — Error caused by invalid or missing data.
- `401` — Authentication failed due to missing or invalid credentials.
- `403` — Error caused by end user (PSU) not permitted access to the resource.
- `404` — Endpoint does not exist or URL is not constructed correctly.
- `429` — Error caused by exceeding unattended accesses to api due to calling to this api and account combination too many times in one day.
- `500` — Error caused by remote technical issues, this status code is used for unforeseen technical issues.
- `503` — Returned when service is unavailable due to scheduled reasons, such as maintenance.
- `504` — Returned when request has been timed out in the gateway.

---

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