ggbucks Docs

SandboxBuild and validate with TEST ggbucks.

One integration. A portfolio of games.

Organize games into projects, define reward rules, and allocate a budget to each game. Every reward is checked against the project ceiling, game ceiling, and daily player cap.

Start building

Set up an invited developer account and your first sandbox game.

Follow the guide

Explore the API

Read the current authentication, request, and response contract.

10 public operations

Sandbox accounting only

TEST ggbucks have no cash value and do not credit a production wallet. Unlimited organization test funding still obeys project and game payout caps.

Choose the right boundary

Keep each credential in the environment where it belongs. A key authenticates a request; your authoritative game server must still verify that play happened.

Game client

Read public configuration. Keep ordinary gameplay available when networking fails.

Public game key

Game server

Verify gameplay, send recorded events, and create player link intents.

Server secret

ggbucks native app

Show the game and accounts, then obtain the player's explicit approval.

Native session

Developer portal

Manage projects, game limits, reward rules, keys, and organization members.

Invited session

Native consent prerequisite

Player linking requires a compatible ggbucks mobile build with v2 consent. Confirm that build is available before promising end-to-end linking. Game integrations never collect a player's Clerk session or approve consent themselves.

Build with the current contract

This site reads the public backend OpenAPI contract every five minutes. Endpoint schemas, console actions, and generated integration skills use the same validated version.

curl --fail \
  https://api.ggbucks.com/developer-api/openapi.json

Integration skillsPortable instructions and examples tied to the contract hash.

Developer portalSign in with an approved, verified primary ggbucks email.