ggbucks.docs
Developer portal

Public sandbox API

API reference

Exact request and response schemas, grouped by the credential and environment that owns the call.

Base URLhttps://api.ggbucks.comSandbox
Read the decision
An event response can report a rejected reward even when HTTP delivery succeeds. Persist its status, reason, and replay flag. Never infer a live payout from an API success.

Developer console

Invited developer sessions manage organizations, projects, games, and scoped reward policy.

GET
Check developer dashboard admission/api/developer/v1/access
GET
Read the developer console/api/developer/v1/console
POST
Manage organizations, projects and games/api/developer/v1/console
GET
Page through linked players or reward decisions/api/developer/v1/records

Game integration

Public client reads and trusted game-server writes. Keep game secrets out of clients.

GET
Read game configuration with a public identifier/api/game-sdk/v2/config
POST
Record a server-verified rewarded-play event/api/game-sdk/v2/events
POST
Create a native account linking intent/api/game-sdk/v2/links
GET
Poll whether a game player is linked/api/game-sdk/v2/players/{playerId}

Native ggbucks app

App-owned consent endpoints. A game backend creates intents and polls status; approval belongs to the human in ggbucks.

POST
Approve linking after native user consent/api/v0/game-sdk/v2/links/approve
POST
Inspect a linking request in the native consent flow/api/v0/game-sdk/v2/links/inspect