The developer API for sports betting, casino, wallets, and more.
Everything you need to build on BetEngine — 41 public endpoints across 12 product areas, an interactive playground, and copy-paste code. Sandbox keys never touch live data or money.
https://api.betengine.casino/api/external/v1
Quickstart
From zero to your first API call in four steps.
1. Create an API key
Register a free developer account and generate a sandbox key (gb_test_…). The secret is shown once.
2. Authenticate
Send the key as a Bearer token in the Authorization header on every request.
3. Call the API
Use the live Playground below to send real sandbox requests, then copy the generated code.
4. Receive webhooks
Subscribe to events and verify the signature on every delivery.
Authentication
Every request requires a Bearer token.
Pass your API key in the Authorization header. Sandbox keys are prefixed gb_test_ and production keys use gb_live_. Sandbox requests never touch live data or move real money.
curl "https://api.betengine.casino/api/external/v1/sports/events" \ -H "Authorization: Bearer gb_test_your_api_key"
Scopes
Each key is limited to the scopes you grant it. Admin scopes are never available to developers.
- Sports & Odds
read:events
Fixtures, events, sports, and leagues.
- Sports & Odds
read:odds
Markets and live/pre-match odds.
- Betting
read:bets
Bet slips, history, and settlement status.
- Betting
write:bets
Build betslips and place sportsbook bets.
- Casino
play:casino
Play provably-fair dice, crash, and mines.
- Players
read:players
Player profile, KYC status, and onboarding.
- Players
write:players
Update profile, notifications, and onboarding.
- Wallet
read:wallets
Wallet balances and transaction history.
- Bonuses
read:bonuses
Bonus status and voucher validation.
- Bonuses
write:bonuses
Claim bonuses and redeem vouchers.
- Social
read:social
Leaderboards, friends, and missions.
- Social
write:social
Add friends and progress missions.
- PvP
read:pvp
Lobbies, matches, and PvP stats.
- PvP
write:pvp
Create lobbies and matches.
- Payments
read:transactions
Deposits, withdrawals, and ledgers.
- Payments
write:transactions
Initiate deposits/withdrawals (sandbox-simulated).
- Platform
read:config
System game config, banners, domains, jackpots.
- Reporting
read:reports
Aggregated reporting data.
- Webhooks
webhooks:receive
Subscribe to event deliveries.
- Webhooks
webhooks:manage
Configure webhook endpoints.
Live Playground
Send real requests to the sandbox gateway. Paste your API key to authenticate — without one you'll see the real 401 response.
Sports & Odds
Betting
Casino
Wallet
Bonuses
Players
Social
PvP
Platform
Payments
System
Webhooks
curl -X GET "https://api.betengine.casino/api/external/v1/sports/events" \ -H "Authorization: Bearer gb_test_YOUR_API_KEY"
API Reference
41 public, non-admin endpoints. Click any endpoint to load it into the playground.
Sports & Odds
Betting
Casino
Wallet
Bonuses
Players
Social
PvP
Platform
Payments
System
Webhooks
Verifying webhook signatures
Every delivery includes an X-BetEngine-Signature header.
The header has the form t=<timestamp>,v1=<signature>. Recompute the HMAC-SHA256 of `${t}.${rawBody}` using your signing secret and compare in constant time.
import crypto from "crypto"
function verifySignature(rawBody, header, secret) {
const [t, v1] = header.split(",").map((p) => p.split("=")[1])
const expected = crypto
.createHmac("sha256", secret)
.update(`${t}.${rawBody}`)
.digest("hex")
return crypto.timingSafeEqual(Buffer.from(v1), Buffer.from(expected))
}