Wallet

Read debit history attributable to the API key application in a linked wallet. Balances, credits, recharges, exports, and other applications are outside this scope.

📄️List wallet debits grouped by conversation session

Returns only debits attributable to the application selected by the API key. The wallet is resolved from that application's unique wallet link, so callers do not provide a wallet identifier. The top-level `data` array contains parent groups: a standalone debit consumes one parent slot and a session consumes one parent slot regardless of how many debits it contains. `limit`, `pagination.total`, and `totalPages` count those parent groups after application and query filters. A session's nested `services` array contains summaries and consumes no extra parent slots, so `limit=10` can represent more than ten service summaries and many more than ten raw debits. Retrieve individual events through the items endpoint for one session and service.

📄️List one service's debit events in a session

Lists raw debit events for one service inside one session. The wallet is resolved from the API-key application's unique wallet link. Use the same application scope as the parent group request: an application key never returns sibling-application events. This is the second pagination layer: `limit` counts raw events, while `nextCursor` is an opaque value from the previous response that must be forwarded unchanged to append the next page. Reuse the parent request's date filters when the child events must match the displayed group totals.