Skip to main content
The API indexes the full bet lifecycle, so wallet history is one GraphQL query - no log scanning.

List a wallet’s bets

GraphQL

Arguments

Response

PlayerBetConnection returns items, totalCount (for pagination), and source - indexed when served from the indexer, unavailable when the indexed store is not configured (you get an empty list, not an error). Each PlayerBet carries the full lifecycle: identity (betId, player, mode, commitId), amounts (stake, liability, payout - decimal strings in USDG units), status timestamps, per-step transaction hashes, attribution (platform, game), and the proof bundle (proof, entropy, commitment, clientSeed, proofStatus). Full field reference: GraphQL - playerBets.

Count pending bets

GraphQL
Returns the number of indexed, unsettled bets for the wallet - useful for a “you have unresolved bets” badge without fetching pages.
For a claim back-fill (user returns after being offline), combine playerBets(filter: { status: SETTLED }) with the batch betResults query to fetch proofs for anything still unclaimed, then offer a single claimBets transaction.