Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Gianluca-X/DigitalMoney/llms.txt

Use this file to discover all available pages before exploring further.

Retrieve the complete activity history for a digital-money account. Results are sorted in descending chronological order (most recent activity first) so the latest transactions always appear at the top. Every deposit from a linked card, every outgoing transfer, and every incoming transfer is recorded as a separate Activity entry and returned in this list.

Endpoint

GET /accounts/{accountId}/activity
Base URL: http://localhost:8085

Authentication

Pass a valid Bearer JWT in the Authorization request header. The header is read directly by the controller — the gateway pre-validates it and the service layer may raise InvalidTokenException on a token that passes gateway validation but fails internal checks.

Path Parameters

accountId
long
required
The numeric identifier of the account whose activity history is to be retrieved.

Response

Returns 200 OK with a JSON array of ActivityOutDTO objects, ordered by date descending.

Response Fields

id
long
Auto-generated unique identifier for the activity record.
accountId
long
The account this activity entry belongs to.
type
string
The kind of activity. One of:
  • "deposit" — funds loaded from a linked card
  • "transfer-out" — outgoing transfer to another account
  • "transfer-in" — incoming transfer from another account
amount
BigDecimal
The monetary amount involved. Negative for transfer-out entries.
date
string
ISO-8601 timestamp of when the activity was recorded (e.g. "2024-03-15T10:30:00").
cvu
string
For transfers, the CVU of the counterpart account (sender or recipient). May be null for deposit entries.

Example Request

curl -X GET "http://localhost:8085/accounts/42/activity" \
  -H "Authorization: Bearer eyJhbGciOiJSUzI1NiJ9..."

Example Response

[
  {
    "id": 301,
    "accountId": 42,
    "type": "transfer-in",
    "amount": 2500.00,
    "date": "2024-03-15T14:22:05",
    "cvu": "0000003100012345678901"
  },
  {
    "id": 298,
    "accountId": 42,
    "type": "deposit",
    "amount": 1500.00,
    "date": "2024-03-14T09:11:33",
    "cvu": null
  },
  {
    "id": 290,
    "accountId": 42,
    "type": "transfer-out",
    "amount": -750.00,
    "date": "2024-03-12T17:45:00",
    "cvu": "0000003100098765432101"
  }
]

Error Responses

StatusExceptionCondition
400 Bad RequestIllegalArgumentExceptionThe request is malformed (e.g. non-numeric accountId).
403 ForbiddenInvalidTokenExceptionThe provided token is invalid or has been tampered with.
404 Not FoundResourceNotFoundExceptionNo account exists with the given accountId.
An empty array [] is returned — not a 404 — when the account exists but has no recorded activity yet.

Build docs developers (and LLMs) love