Skip to main content
GET

Request

Headers

string
required
Bearer token (JWT or API key)

Query Parameters

number
default:"1"
Page number for pagination
number
default:"20"
Items per page (max 100)
string
Filter by service type. Options: TTS, STT, LLM, MEMORY_INGEST, MEMORY_EXTRACT, MEMORY_RECALL, MEMORY_CONTEXT, TOP_UP, AUTO_TOP_UP, SA_TOP_UP

Response

array
Array of transaction log entries
string
Unique transaction ID (UUID)
string
Service that was charged (TTS, STT, LLM, MEMORY_INGEST, etc.). Credit top-ups use TOP_UP (bought by the customer), AUTO_TOP_UP (automatic, coming soon) or SA_TOP_UP (recorded by a superadmin for an offline payment).
number
USD amount deducted. Negative values indicate refunds. For top-up rows (TOP_UP, AUTO_TOP_UP, SA_TOP_UP), a negative value is a credit added to the wallet. The metadata field holds credits, paid_usd and source (self, auto or sa_manual).
number
Units consumed (characters for TTS, minutes for STT, tokens for LLM, bytes/queries for Memory)
number
Workspace balance before this operation
number
Workspace balance after this operation
string
Name of the user who performed the operation
string
ISO 8601 timestamp
array
Aggregated totals grouped by service type
Only the workspace owner can view usage logs. This endpoint is protected by billing:manage permission. Every API operation (TTS, STT, LLM, Memory) that costs money is logged here — this is your complete billing audit trail.