Deposits
GET /v1/deposits
Section titled “GET /v1/deposits”Returns transfers to/from the user’s CVU, fetched live from the bank rail by legal ID (up to 100 most recent). Despite the name, this includes both incoming and outgoing legs — check direction.
Request
Section titled “Request”curl https://sandbox-api.nuez.app/v1/deposits \ -H "Authorization: Bearer <jwt>"Response
Section titled “Response”{ "deposits": [ { "id": "...", "from": "...", "to": "...", "fromLegalId": "...", "toLegalId": "...", "fromName": "...", "toName": "...", "amount": "5000.00", "currency": "ARS", "status": "completed", "creationTime": "2026-07-18T10:00:00Z", "direction": "credit" } ]}Returns {"deposits": []} (not an error) if the user has no legal_id on file yet — i.e. onboarding hasn’t progressed far enough to have one.
The MCP equivalent, list_recent_deposits, wraps the same data under a transfers key with an added count field and accepts a limit parameter (1–50, default 10) — see MCP tools.