List a user's credit lots

GET /v1/admin/billing/lots

• Operation ID: listBillingCreditLots
• Tags: Billing credits
• Base URL: http://localhost:8787

Up to 200 lots (including drained and expired), newest first. expires_at is null for lots that never expire.

Workflow: Integration guide.

Authentication: staff Bearer JWT with permission billing.read.

Authentication

• Auth: staff Bearer JWT (Authorization: Bearer <access_token>) with the permissions below.
• Required permissions: billing.read

Parameters

Name	In	Type	Required	Description
userId	query	string<uuid>	yes	-

Responses

200

Lots.

• Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (BillingCreditLots)

Field	Type	Required	Description
data	(object (MyCreditLot))[]	yes	-
data[].id	string<uuid>	yes	-
data[].source	string	yes	-
data[].tier_key	string | null	yes	-
data[].granted	string | number	yes	-
data[].remaining	string | number	yes	-
data[].expires_at	string | null	yes	-
data[].created_at	string	yes	-

Errors

400

Request validation failed.

• Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ValidationErrorBody)

Field	Type	Required	Description
success	boolean	yes	One of: false
error	object	yes	-
error.name	string	yes	One of: "ZodError"
error.issues	object[]	yes	-
error.issues[].code	string	yes	-
error.issues[].path	(string | number)[]	yes	-
error.issues[].message	string	yes	-

Request validation

{
  "success": false,
  "error": {
    "name": "ZodError",
    "issues": [
      {
        "code": "custom",
        "path": [
          "field"
        ],
        "message": "Invalid value"
      }
    ]
  }
}

401

Missing, malformed, expired or wrong-audience Bearer token (missing_token, invalid_token, invalid_audience).

• Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody)

Field	Type	Required	Description
error	string	yes	Stable machine-readable error code, e.g. forbidden, not_found.
details	any	no	Optional structured context. For 403 it is { perm }.

Error response

{
  "error": "missing_token"
}

403

Authenticated but lacking the required permission. details.perm lists the accepted permission keys.

• Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

{
  "error": "forbidden",
  "details": {
    "perm": "billing.read"
  }
}

500

Unexpected server error (internal). No details are returned.

• Header x-request-id: Request identifier; quote it when reporting an error. Content type: application/json

Schema: object (ErrorBody), fields as described above.

Error response

{
  "error": "internal"
}

Examples

curl

curl -X GET 'http://localhost:8787/v1/admin/billing/lots?userId=3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90' \
  -H "Authorization: Bearer $ACCESS_TOKEN"

TypeScript

const accessToken = process.env.ACCESS_TOKEN; // user JWT from your sign-in flow

const response = await fetch("http://localhost:8787/v1/admin/billing/lots?userId=3f6c2a1e-8b4d-4e7a-9c1f-2d5b6a7e8f90", {
  method: "GET",
  headers: {
    "Authorization": `Bearer ${accessToken}`,
  },
});
if (!response.ok) throw new Error(`HTTP ${response.status}: ${await response.text()}`);
const data = response.status === 204 || response.status === 205
  ? undefined
  : response.headers.get("content-type")?.includes("json")
    ? await response.json()
    : await response.text();