Getting started

Start with invited portal access

Open developers.ggbucks.com and sign in with the verified primary email approved by a ggbucks administrator. An active portal invitation and organization membership are separate checks. The public docs site has no sign-in requirement.

Create an organization, a project and a game in the portal UI. Choose the platform and finite project/game payout ceilings, allocate TEST funds, then define the accepted event types and fixed rewards. A managed first-party organization can have unlimited TEST funding; every project and game still has a hard payout cap.

Separate the client from its server

Issue a public key (ggb_pk_sandbox_ plus 43 random suffix characters) for game configuration. The client key can be extracted and provides no gameplay proof.

Issue a secret key (ggb_sk_sandbox_ plus 43 suffix characters) for the authenticated game server. Copy its one-time reveal into a server secret manager. Revocation disables further use. Keep secret keys out of Unity, browser bundles, logs and remote config. Developer console requests use the invited portal Clerk session, never a game key or a fabricated long-lived bearer.

Verify a complete sandbox flow

Read public configuration, arrange native player consent, verify an action on the authoritative game server, persist its event in a durable outbox, and observe the immutable accepted/rejected decision. Keep gameplay usable when networking or linking fails.

The self-contained Unity and server examples are downloadable source. No published SDK registry or legacy v1 endpoint is implied. Native linking requires a compatible ggbucks mobile build implementing v2 consent; confirm that build is available before promising account linking.

Use the same contract in your project

Read the focused agent skill or download its source and contract ZIP. Review the included source before adding it to your game. Exact fields and action variants are available in the API reference.