Customer integration guide

One clean connection for your game wallet.

Keep your existing request body and callback response. Change the API origin to your GGR Point2 workspace and use the credentials generated in your dashboard.

Launch endpoint

https://ggr.point2.us/api/GetGameUrl.php

Call it from your server. Never place the API secret in browser code. The response includes a play URL on your GGR Point2 domain.

01 · Credentials

Create an API credential

Open API credentials in your workspace. Copy the API key and secret when they are shown. The API secret is shown only once.

02 · Launch

Send your existing request

Use the customer API key as the Bearer token and keep your JSON fields unchanged.

03 · Wallet

Configure your webhook

Save your HTTPS callback URL in Webhooks, then copy the separate webhook signing secret to your wallet service.

Launch request

Headers


Authorization: Bearer gapi_live_…
Content-Type: application/json

POST https://ggr.point2.us/api/GetGameUrl.php


{
  "member_account": "player-123",
  "game_uid": "2eb2879a2e4f3c5e5d297925283c37c9",
  "balance": "500.00",
  "home_url": "https://your-brand.example/casino"
}

Successful response


{
  "code": 0,
  "msg": "Success",
  "payload": { "game_launch_url": "https://ggr.point2.us/play?token=…" }
}

Open payload.game_launch_url directly. Game content is served through your GGR Point2 play route.

API access and callback signing are separate

API credential

Use the API key in the Authorization: Bearer header on the compatible launch endpoint. The one-time API secret remains available for the extended authentication mode.

Webhook signing secret

Used to verify callback requests sent to your wallet URL. Generate or rotate it on the Webhooks page; store it in your webhook service and compare the HMAC of the exact raw body.

Callback flow

Provider

Sends a signed game event to GGR Point2.

GGR Point2

Verifies, records and forwards the event to your saved URL.

Your wallet

Verifies the webhook signature, updates the player balance and returns code: 0.


X-Signature: 
X-Event-Id: 
X-Proxy-Timestamp: 

{
  "serial_number": "uuid-txn-id-1234",
  "currency": "USD",
  "game_uid": "2eb2879a2e4f3c5e5d297925283c37c9",
  "member_account": "player-123",
  "win_amount": "150.00",
  "bet_amount": "100.00",
  "timestamp": 1788192000,
  "game_round": "round-1234",
  "data": {}
}

Return HTTP 200 with {"code":0,"msg":"Success","balance":"550.00"}. Configure and test delivery from the Webhooks page.

Recommended rollout: create one credential, launch one player with one game ID, verify the returned play URL, then send one callback test before moving the rest of your traffic.