Skip to content

[Bug] API v2 has no account balance endpoint — clients must keep a deprecated GraphQL call alive #810

Description

@vincenzoml

Hello, we have migrated our app to the new API. It's a comfyui frontend that also now helps end users create pods on runpod without effort; but claude opus reported no way to migrate the credit balance we show to our users in the app:

v2's OpenAPI (api.runpod.io/v2/openapi.json) has no endpoint returning
remaining account credit. "balance" appears 8 times: 7 are "load balancer",
1 is the 402 "Insufficient balance" a pod create returns.

/v2/billing returns historical spend, bucketed by time. It says what was
burned, never what is left.

The only source of remaining credit is GraphQL:
query { myself { clientBalance currentSpendPerHr } }

The v2 announcement says v2 "covers everything Runpod does... including
billing", and the docs say GraphQL will be deprecated. Both being true
means remaining balance becomes unreachable.

Please expose remaining balance in v2 — clientBalance and
currentSpendPerHr equivalents, e.g. on /v2/billing — before GraphQL is
retired.

Related, runpod/runpodctl#147 was resolved by adding runpodctl user — which is
itself GraphQL-only (internal/api/gpu.go, GetUser), as far as the agent reports.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions