Sportsbook API
The Sportsbook API is a suite of RESTful and WebSocket APIs for building your own sportsbook frontend on top of the GR8 Platform. You own the interface; the platform supplies the line and odds, the player context, bet placement and settlement.
Integration in 3 steps
1. Drive your frontend from the GR8 API
GR8 API (requires sign-in) is the user-context API your application talks to: line and odds, event content, bet placement, bet history, player settings. Every request carries your brand’s API key and, for a signed-in player, their access token — so responses come back already personalized for that player and brand.
For real-time line, market and score updates, connect the DirectFeed API (requires sign-in) (SignalR over WebSockets) rather than polling the line endpoints.
2. Connect your wallet
Required as soon as you accept real bets. Betting transactions run against your wallet: the platform calls endpoints you implement to read balances and to debit and credit players.
Wallet integration is documented in its own section, because the contract is identical for iFrame and Sportsbook API clients. Start with the seamless wallet — it is the recommended model.
3. Add server-to-server calls where you need them
S2S API is the service-context API for your backend: player registration and profiles, bet history and settlement, bonuses, limits, and line data outside a single player’s session. Optional — add it when your backend needs to act without a player request behind it.
Before you start
- Architecture (requires sign-in) — how your browser app, web server, backend and wallet adapter sit around the platform, and which API each of them calls.
- Quick Start (requires sign-in) — your first authenticated request, and the shortest path to a placed bet.
- API conventions (requires sign-in) — the versioned path scheme every HTTP endpoint follows, the
Api-VersionandX-Endpoint-Versionheaders, and rate limiting.
Reference
- API Integration Recommendations (requires sign-in) — caching, polling intervals and other practices we recommend for GR8 API clients
- Market Translation (requires sign-in) — how to turn the market, outcome and period ids the line endpoints return into localized names
- Markets Description (requires sign-in) — the markets available per sport
- Changelog (requires sign-in) — latest updates, new features, and breaking changes