Skip to main content
GET
/
api
/
transactions
/
:id
Get Transaction
curl --request GET \
  --url https://api.example.com/api/transactions/:id \
  --header 'Authorization: <authorization>'
{
  "400": {},
  "401": {},
  "404": {},
  "id": "<string>",
  "type": "<string>",
  "amount": 123,
  "currency": "<string>",
  "description": "<string>",
  "date": "<string>",
  "userId": "<string>",
  "accountId": "<string>",
  "categoryId": "<string>",
  "account": {
    "id": "<string>",
    "name": "<string>",
    "type": "<string>",
    "balance": 123,
    "currency": "<string>"
  },
  "category": {
    "id": "<string>",
    "name": "<string>",
    "type": "<string>",
    "icon": "<string>"
  },
  "createdAt": "<string>",
  "updatedAt": "<string>",
  "deletedAt": "<string>"
}

Authentication

This endpoint requires authentication using a Bearer token.
Authorization
string
required
Bearer token for authentication

Path Parameters

id
string
required
UUID of the transaction to retrieve

Response

Returns a single transaction object with full details.
id
string
Unique identifier for the transaction
type
string
Transaction type (INCOME, EXPENSE, or TRANSFER)
amount
number
Transaction amount
currency
string
Currency code
description
string
Transaction description
date
string
Transaction date in ISO 8601 format
userId
string
ID of the user who owns this transaction
accountId
string
ID of the associated account
categoryId
string
ID of the associated category (if any)
account
object
Full account object
category
object
Full category object (if categoryId exists)
createdAt
string
Timestamp when the transaction was created
updatedAt
string
Timestamp when the transaction was last updated
deletedAt
string
Soft delete timestamp (null for active transactions)

Error Responses

400
error
Bad Request - Invalid UUID format
401
error
Unauthorized - Missing or invalid authentication token
404
error
Not Found - Transaction doesn’t exist or doesn’t belong to the authenticated user

Example Request

curl -X GET https://api.yourfinanceapp.com/api/transactions/a3c4e8f2-9d7b-4a1c-8e3f-2b5d9a7c1e4f \
  -H "Authorization: Bearer YOUR_JWT_TOKEN"

Example Response

{
  "id": "a3c4e8f2-9d7b-4a1c-8e3f-2b5d9a7c1e4f",
  "type": "EXPENSE",
  "amount": 1500.75,
  "currency": "ARS",
  "description": "Compra de comestibles",
  "date": "2026-03-04T14:30:00.000Z",
  "userId": "user-uuid-123",
  "accountId": "uuid-de-la-cuenta",
  "categoryId": "92b77be3-a14a-462c-a291-7eff27cbcf47",
  "account": {
    "id": "uuid-de-la-cuenta",
    "name": "Cuenta Principal",
    "type": "WALLET",
    "balance": 8499.25,
    "currency": "ARS"
  },
  "category": {
    "id": "92b77be3-a14a-462c-a291-7eff27cbcf47",
    "name": "Alimentos",
    "type": "EXPENSE",
    "icon": "🛒"
  },
  "createdAt": "2026-03-04T14:30:15.123Z",
  "updatedAt": "2026-03-04T14:30:15.123Z",
  "deletedAt": null
}

Notes

  • The endpoint only returns transactions that belong to the authenticated user
  • Soft-deleted transactions (where deletedAt is not null) are not accessible through this endpoint
  • The UUID must be a valid v4 UUID format, otherwise a 400 error is returned

Build docs developers (and LLMs) love