Cashier — My own operations

GET /v1/events/{eventId}/cashier/operations — the mirror image of the statement (see Look up and activate a wallet → statement): instead of every movement on one wallet, it's every operation you performed, across however many wallets you touched. Always self-service — there's no parameter to see another cashier's activity, only your own, identified from your own token.

curl "http://127.0.0.1:8787/v1/events/{eventId}/cashier/operations?limit=20" \
  -H "Authorization: Bearer <cashier accessToken>"

Response

{
  "items": [
    {
      "transactionId": "018f26d7-...",
      "type": "recharge",
      "userId": "018f26d7-...",
      "walletId": "018f26d7-...",
      "amountMinor": 5000,
      "occurredAt": "2026-09-03T16:30:29.377Z",
      "paymentMethod": "cash",
      "note": null,
      "createdByOperatorUsername": "CX-55130771",
      "createdByOperatorDescription": "Entrada Principal"
    }
  ],
  "nextCursor": null
}

Here createdByOperatorUsername/createdByOperatorDescription are always your own — this endpoint is self-service.

Same filters/pagination as the wallet statement (type, occurredAfter, occurredBefore, sortDirection, limit, cursor), plus one more: userId, to filter down to operations performed on one specific participant.

Important difference: occurredAfter has a ceiling here — the API never shows anything older than 48 hours, no matter what you ask for. It's not a default you can work around; it's a real limit, enforced by the server. It exists because there's no cashier shift concept yet — with no formal "shift start" to anchor against, this fixed window keeps a cashier session from browsing a huge, unnecessary amount of history.

This endpoint is for identification only — it's meant for you to check what you did (e.g. reconciling against the physical cash drawer at the end of the day), there's no recharge reversal action available from here (yet).