List credit ledger
OpenAPI contract
- Method
- GET
- Path
/api/v1/billing/ledger- Security
- jwtBearer (bearer)
- Response status
- 200 400 401 403 404 429 500
Request and response schemas
JSON
{
"requestBody": {},
"responses": {
"200": {
"description": "Ledger page",
"content": {
"application/json": {}
}
},
"400": {
"description": "Invalid request",
"content": {
"application/json": {
"$ref": "#/components/schemas/RequestError"
}
}
},
"401": {
"description": "Authentication required or invalid",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"403": {
"description": "Authenticated but not permitted",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"404": {
"description": "Ledger was not found",
"content": {
"application/json": {
"$ref": "#/components/schemas/ApiError"
}
}
},
"429": {
"description": "Rate limit exceeded",
"content": {
"application/json": {
"$ref": "#/components/schemas/SecurityError"
}
}
},
"500": {
"description": "Unexpected server error",
"content": {
"application/json": {
"$ref": "#/components/schemas/ApiError"
}
}
}
}
}GET /api/v1/billing/ledger is JWT-only and returns a Spring page of the authenticated user's credit entries. page defaults to 0 and is floored at 0; size defaults to 20 and is clamped to 1..100. Each entry includes total and bucket deltas, running balances, reason, reference fields, note, and creation time.
Build charging is represented by a BUILD_HOLD debit followed, when applicable, by a BUILD_REFUND credit; there is no separate consume entry.
http
GET /api/v1/billing/ledger?page=0&size=20
Authorization: Bearer <access token>