> ## Documentation Index > Fetch the complete documentation index at: https://docs.topcalls.ai/llms.txt > Use this file to discover all available pages before exploring further. # List credit ledger entries > Cursor-paginated credit ledger for the account, newest first. Each row is one wallet movement: a purchase, a call spend, starter credit, a transfer, or an adjustment. Amounts are signed integer microdollars ($1 = 1,000,000). A call spend is negative. Holds placed and released for a call in progress are omitted, as are movements that moved no money. `talk_seconds` is set on a call spend and null otherwise. `source_id` is the call id for a spend. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/usage/movements openapi: 3.0.3 info: title: TopCalls Voice API description: > TopCalls Voice Gateway API for creating and managing AI-powered phone calls. ## Authentication All API requests require authentication. Include your API key in the `Authorization` header: ``` Authorization: Bearer tc_live_xxxxx ``` ## Rate Limits Direct call creation via `POST /v1/calls` is limited to your account's `max_calls_per_minute` setting (default: 20) counted over a fixed 60-second window. Exceeding it returns `429 Too Many Requests` with a `Retry-After: 60` header. The limit is per account and shared across all of the account's API keys. A request counts toward the limit as soon as it passes body validation, so an attempt that then fails on a missing reference (for example a `404` for an unknown `lead_id`/`campaign_id`) still consumes a slot. All endpoints are additionally subject to a flat limit of 120 requests per minute per account (all methods). On a `429`, wait for the number of seconds in the `Retry-After` header, then retry the same request. For automated clients, back off progressively on repeated `429`s. Limits are per account and are shared by all API keys. ## Error Format All errors follow RFC 7807 Problem+JSON format: ```json { "type": "https://api.topcalls.ai/errors/insufficient_quota", "title": "Insufficient Quota", "status": 402, "detail": "Not enough credit to place this call. Add credit in Billing." } ``` version: 1.0.0 contact: name: TopCalls Support url: https://topcalls.ai license: name: Proprietary servers: - url: https://api.topcalls.ai description: Production security: [] tags: - name: Calls description: Create and manage phone calls - name: Phone Numbers description: Manage phone numbers and carriers - name: Account description: Account information and usage - name: Webhooks description: Webhook configuration and events - name: Configuration description: Available AI models, voices, and platform capabilities paths: /v1/usage/movements: get: tags: - Account summary: List credit ledger entries description: | Cursor-paginated credit ledger for the account, newest first. Each row is one wallet movement: a purchase, a call spend, starter credit, a transfer, or an adjustment. Amounts are signed integer microdollars ($1 = 1,000,000). A call spend is negative. Holds placed and released for a call in progress are omitted, as are movements that moved no money. `talk_seconds` is set on a call spend and null otherwise. `source_id` is the call id for a spend. operationId: listUsageMovements parameters: - name: limit in: query description: Page size schema: type: integer minimum: 1 maximum: 100 default: 50 - name: cursor in: query description: >- Return rows with `created_at` strictly before this ISO timestamp (from a previous response's `next_cursor`) schema: type: string format: date-time - name: created_after in: query description: Only rows with `created_at` on or after this ISO timestamp schema: type: string format: date-time - name: created_before in: query description: Only rows with `created_at` on or before this ISO timestamp schema: type: string format: date-time responses: '200': description: Usage movements content: application/json: schema: type: object required: - data - next_cursor properties: data: type: array items: $ref: '#/components/schemas/UsageMovement' next_cursor: type: string format: date-time nullable: true '400': description: Invalid query parameters content: application/problem+json: schema: $ref: '#/components/schemas/Problem' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' security: - bearerAuth: [] components: schemas: UsageMovement: type: object required: - id - kind - amount_micros - balance_after_micros - source_id - talk_seconds - created_at properties: id: type: string format: uuid description: Ledger entry id. kind: type: string enum: - starter_grant - purchase - spend - transfer_out - transfer_in - plan_conversion - admin_adjust - concurrency_fee - lot_clawback description: Why the wallet moved. example: spend amount_micros: type: integer description: >- Signed microdollars. Negative when credit left the wallet (a call or a transfer out), positive when credit arrived. example: -350000 balance_after_micros: type: integer description: Wallet balance after this movement, in microdollars. example: 9650000 source_id: type: string nullable: true description: Call id when `kind` is `spend`. Null for other kinds. example: 564d4fd4-03bc-400a-abe0-05540fbeff88 talk_seconds: type: integer nullable: true description: >- Talk time for a call spend, in whole seconds. Null when the movement is not a call. example: 60 created_at: type: string format: date-time Problem: type: object required: - status - title properties: type: type: string format: uri description: Error type URI title: type: string description: Error title status: type: integer description: HTTP status code detail: type: string description: Human-readable error detail code: type: string description: > Machine-readable error code for programmatic handling. Present on errors that carry a stable identifier (e.g. `PROMPT_SAFETY_FRAUD`, `job_not_found`, `too_many_ids`, `no_matches`). Distinct from the per-field `errors[].code` used for validation failures. Scenario- specific — see each endpoint's response examples for the exact value. instance: type: string format: uuid description: Request instance ID errors: type: array description: Validation errors (for 400 responses) items: type: object properties: path: type: string description: Field path (e.g., "phone_number", "metadata.from_number") message: type: string description: Error message code: type: string description: Error code (e.g., "invalid_string", "custom") details: type: string description: Additional error details (for provider errors) responses: Unauthorized: description: Unauthorized (missing or invalid API key) content: application/problem+json: schema: $ref: '#/components/schemas/Problem' example: status: 401 title: Unauthorized detail: Invalid or missing API key Forbidden: description: Forbidden (missing required scope) content: application/problem+json: schema: $ref: '#/components/schemas/Problem' example: status: 403 title: Forbidden detail: 'Missing required scope: calls:write' securitySchemes: bearerAuth: type: http scheme: bearer description: | Use `Authorization: Bearer tc_live_xxxxx` ````