---
title: "Credit statement"
method: GET
path: "/client/credits/statement"
tags: ["Account"]
---

# Credit statement

`GET /client/credits/statement`

## Request

- Base URL: `https://api.roar-ai.com`
- URL: `https://api.roar-ai.com/client/credits/statement`
- Auth: HTTP bearer

Every movement of your balance, newest first, with the balance after each one.

Narrow it with `lens`: `payments` (card top-ups, refunds and manual adjustments), `usage` (AI gateway spend) or `hosting` (app hosting). Omit it for all three interleaved.

**Use `lens=payments` to find a card payment.** Gateway usage is written about once a minute while traffic flows, so an unfiltered statement on a busy account reaches back roughly an hour. `limit` defaults to 100 and caps at 500. `from` and `to` (ISO timestamps, `to` exclusive) bound it to a date range.

A day of metered app-hosting charges arrives as ONE line carrying `coversUtcDay` and `coversEntries`; the per-day hosting base fee keeps its own line with a note saying what it bought.

## Response `200`

Statement lines, newest first

---

[API](https://skmtc.dev/roar-ai/apis/roar-ai-api.md) · [All operations](https://skmtc.dev/roar-ai/apis/roar-ai-api/llms.txt) · [OpenAPI document](https://skmtc.dev/roar-ai/apis/roar-ai-api/revisions/37e4d0d5a7fe?raw)
