API documentation

Hudio exposes its provider offering behind one REST API with one seamless wallet: per-client players, idempotent credit/debit, a launch / bet / status triple per provider, and usage & GGR computed from settled bet data. The seamless surface described below is the current aggregation offering.

Provider coverage

Keys bound to a client get the seamless surface: per-client players with their own wallets, and one launch / bet / status triple per provider, all staking the player's own wallet. The platform covers live-casino studios, table-game providers and its own in-house engine. Provider availability is enabled per client at onboarding — your account manager confirms which lanes are active on your key. The full catalogue, provider by provider, is in the coverage table below and in the games browser.

Base URL & authentication

Base URL: https://hudio.live/api/v1

Every /api/v1/* call needs an API key, sent either in the x-api-key header or as Authorization: Bearer <key>. Keys are issued by the operator and shown once at creation — store yours like a password.

curl https://hudio.live/api/v1/providers -H "x-api-key: pq_live_…"
Current offering: the seamless lanes below are the live aggregation offering. Providers and surfaces outside it — the panel catalogue, the legacy gateway session surface, and providers still in integration — answer 503 {"code":"PROVIDER_NOT_AVAILABLE"} on launch and bet calls.

Endpoints

EndpointDescription
GET /api/v1/providersList the providers in the current offering (the seamless lanes below).
POST /api/v1/{provider}/sessionLegacy gateway session surface — not part of the current offering; answers 503 {"code":"PROVIDER_NOT_AVAILABLE"}.
GET /api/v1/{provider}/balance?session=Legacy gateway session surface — not part of the current offering; answers 503 {"code":"PROVIDER_NOT_AVAILABLE"}.
GET /api/v1/{provider}/history?session=Legacy gateway session surface — not part of the current offering; answers 503 {"code":"PROVIDER_NOT_AVAILABLE"}.
POST /api/v1/{provider}/betSession-shaped (gateway) bets are not part of the current offering — 503 {"code":"PROVIDER_NOT_AVAILABLE"}. Player-shaped bets on the seamless lanes below are the offered bet surface.
POST /api/v1/{provider}/cashoutLegacy gateway session surface — not part of the current offering; answers 503 {"code":"PROVIDER_NOT_AVAILABLE"}.
GET /api/v1/upstream/gamesThe panel catalogue is not part of the current offering; this call answers 503 {"code":"PROVIDER_NOT_AVAILABLE"}.
POST /api/v1/upstream/sessionThe panel catalogue is not part of the current offering; this call answers 503 {"code":"PROVIDER_NOT_AVAILABLE"}.

Own-engine games

Alongside the provider lanes, the platform runs its own game engine: 57 in-house titles in the current offering — dice, mines, crash, lotto, towers and more — served through the Turbo seamless API below and wallet-bound hosted play. In-house games stake and settle against the seamless wallet directly, with no third-party account in between, and every round is stamped with your client id for usage attribution.

Seamless wallet (per-client players)

Keys bound to a client get a seamless wallet scope: players created through this API belong to your client alone. No key can see, credit, debit or launch for another client's players — or for operator-scope players: out-of-scope player ids answer 404 {"error":"player not found","code":"PLAYER_NOT_FOUND"}, never a leak of existence. Keys bound to a reseller, or unbound keys, get 403 {"code":"CLIENT_SCOPE_REQUIRED"} on every wallet route. Money is INR, amounts are rupees with at most 2 decimals.

EndpointDescription
POST /api/v1/wallet/playersCreate a player under your client. Body: { "name": "…" } (names are globally unique). → 201 { id, name, balance: 0, currency: "INR", clientId }; duplicate name → 409 {"code":"PLAYER_EXISTS"}.
GET /api/v1/wallet/playersList only your client's players: { players: [{ id, name, balance, currency, clientId, status, createdAt }] }.
GET /api/v1/wallet/players/:id/balance→ { playerId, balance, currency }.
POST /api/v1/wallet/players/:id/creditCredit a player. Body: { "amount": 500, "ref": "your-unique-ref", "note": "…" }. Idempotent on ref: retrying the same ref returns the original result with "duplicate": true and the balance moves once. → 200 { playerId, balance, currency, amount, ref, duplicate }.
POST /api/v1/wallet/players/:id/debitDebit a player, same body and idempotency as credit. Insufficient funds → 402 {"code":"INSUFFICIENT_WALLET"} and nothing moves.
GET /api/v1/wallet/players/:id/transactions?limit=50The player's ledger entries, newest first (limit 1–200): { playerId, transactions: [{ id, ts, type, amount, balanceAfter, ref, note }] }. Types include credit, debit, win and rollback (game settlements appear here under the bet's ref).

Usage — bet turnover, GGR & your earning

GET /api/v1/usage?from=&to= reports your client's figures computed from actual bet data (settled bets only; void/pending excluded): { clientId, clientName, earningModel, ggrPercent, commissionPercent, rentAmount, rentPeriod, rentPeriods, period: { from, to }, bets, turnover, returns, ggr, clientShare, earning, basis } where turnover = sum of stakes, returns = sum of payouts and ggr = turnover − returns. clientShare (also returned as earning) is what your client earns under the earning model the operator set for it: earningModel: "ggr" → ggr × your GGR %; "commission" → turnover × your commission %; "rent" → your flat rentAmount × the number of rent periods (rentPeriod: monthly/weekly/daily) in the range — rentPeriods reports how many were charged, and an open range start counts from your client's creation date. basis is "stamped" for bets recorded with your client id at placement, "reconstructed" for older bets attributed via the player's current client binding, or "mixed" (with a basisBreakdown) when both exist. from/to are optional ISO dates. Your client portal shows the same figures.

Evolution (hosted, wallet-bound)

Evolution live-casino tables run from the platform's hosted client; the balance inside the game is the player's seamless-wallet balance. One table session serves one player at a time.

EndpointDescription
POST /api/v1/evo/launchBody: { "playerId": "…" } (your client's player). → 200 { playerId, playerName, playUrl, balance } — open playUrl in the player's browser; the launch completes when the page opens.
POST /api/v1/evo/betPlace a Golden Wealth Baccarat bet for your player. Body: { "playerId": "…", "spot": "Banker", "chip": 100 }. Supported spots: Banker, Player, Tie, PlayerPair, BankerPair (SuperSix is not currently available). Settlement is posted from the table's official result into the player's wallet transactions. If the table session is in use by another player → 409 {"code":"EVO_SEAT_BUSY"}; if a session for your player is still opening → 202 {"code":"EVO_SESSION_OPENING"}, retry shortly.
GET /api/v1/evo/status→ engine and table-session status for your client. The bound player's name is shown only when that player belongs to your client.

Settlement is asynchronous — and reconciled. Settlements land from the table's official results into the player's wallet transactions. If a result is ever revised by the provider, the wallet is corrected automatically by the exact difference, and the correction appears as an adjustment entry in the player's transactions — always reconcile from wallet transactions.

The hosted catalogue. Beyond the bet API above, the hosted client carries Evolution's full 312-table catalogue — blackjack, baccarat, roulette, game shows, sic bo, dragon tiger and more. Any table can be launched for a player (GET /evo/play?table=<catalogue id>) with the in-game balance bound to the player's wallet, and play is accounted through the same wallet ledger.

Turbo (own-engine games, wallet-bound)

Turbo games run on the platform's own engine — the platform is the house, so there is no third-party account in between. The balance inside every game is the player's seamless-wallet balance, bets settle instantly from the engine's own result, and every round is stamped with your client id for usage attribution. Same scope rules as Evolution: client-bound key required, out-of-scope players answer 404 {"code":"PLAYER_NOT_FOUND"}. The game is chosen with a body slug — one of dice, limbo, turboplinko, towers, fruittowers, stairs, turbomines, bookofmines, bubbles, fastfielder, spinstrike, wicketblast, mines.

EndpointDescription
POST /api/v1/turbo/launchBody: { "playerId": "…", "slug": "dice" } → 200 { playerId, playerName, slug, title, playUrl, balance } — open playUrl in the player's browser. Unknown slug → 404 {"code":"GAME_NOT_FOUND"} with the valid slugs listed.
POST /api/v1/turbo/betPlace a bet and play the round's steps in one call. Body: { "playerId": "…", "slug": "dice", "amount": 10, "params": { "value": 50, "action": "under" }, "ref": "your-ref" } (params are the game's own fields). → 200 { ok, betRef, callerRef, roundId, stake, payout, result, state, done, balance, round }. ref is idempotent per player: a repeat → 409 {"code":"DUPLICATE_REF"}. Insufficient funds → 402 {"code":"INSUFFICIENT_WALLET"} and nothing moves. A round left open ("done": false) continues via act/cashout below.
POST /api/v1/turbo/actOne step on an open round you own. Body: { "playerId": "…", "roundId": "…", "action": { … } } → the same round shape as bet. Rounds owned by another player answer 404 {"code":"ROUND_NOT_FOUND"}; terminal rounds 409 {"code":"ROUND_CLOSED"}.
POST /api/v1/turbo/cashoutCash out an open round. Body: { "playerId": "…", "roundId": "…" } → the same round shape; the payout credits the player's wallet immediately.
GET /api/v1/turbo/games→ { games: [{ slug, gameId, title, limits, loaded }] } — the 13 games with their bet limits.
GET /api/v1/turbo/status→ { provider: "turbo", engineReady, games: 13, slugs: [...] }.

Aura Gaming — not in the current offering

Aura Gaming is not part of the current provider offering. Calls to /api/v1/aura/* answer 503 {"error":"provider not available in the current offering","code":"PROVIDER_NOT_AVAILABLE","provider":"aura"}.

CreedRoomz — not in the current offering

CreedRoomz is not part of the current provider offering. Calls to /api/v1/creedroomz/* answer 503 {"error":"provider not available in the current offering","code":"PROVIDER_NOT_AVAILABLE","provider":"creedroomz"}.

Mac88 (API-bet, wallet-bound)

Mac88 is served through the bet API — the AGX family (40 titles) is in the current offering. Bets debit the player's seamless wallet and settle from the provider's round results. Bets are processed in turn and wait for a fresh betting round (from ~40 seconds on baccarat to a few minutes on long-cycle tables), so use long HTTP timeouts (≥ 500 s) or fire-and-poll via wallet transactions. Same scope rules as Evolution. The AGB family and 3 Card Judgement (AGX3CJ101) are not part of the current offering: launch and bet calls for them answer 503 {"code":"PROVIDER_NOT_AVAILABLE"}. Unknown AGX titles answer TITLE_UNKNOWN. The game client is view-only — the wallet binding is the bet API.

EndpointDescription
POST /api/v1/mac88/launchBody: { "playerId": "…", "gameId": "AGXBAC101" } (gameId optional — defaults to Baccarat) → 200 { provider: "mac88", playerId, playerName, balance, gameId, playUrl, walletBound: "api", viewedClientBound: false, note }. AGB-family and 3 Card Judgement gameIds → 503 {"code":"PROVIDER_NOT_AVAILABLE"}; unknown gameId → {"code":"TITLE_UNKNOWN"}.
POST /api/v1/mac88/betBody: { "playerId": "…", "gameId": "AGXBAC101", "tableId": "ATGXBAC101", "stake": 100, "runnerName": "Banker", "ref": "your-ref" } (BACK bets only; LAY → BET_TYPE_NOT_EVIDENCED). → 200 { ok: true, betRef, gameId, tableId, stake, state: "fired", roundId, price, bet }; settlement is asynchronous. Errors: 402 INSUFFICIENT_WALLET (pre-check, no record created) · 402 INSUFFICIENT_FUNDS_UPSTREAM (provider funds; debit returned, bet void) · 504 WINDOW_TIMEOUT (no fresh round in 240 s; debit returned) · 409 DUPLICATE_REF · 502 MAC88_ENGINE_UNAVAILABLE / MAC88_BET_FAILED · 503 PROVIDER_NOT_AVAILABLE (AGB family / 3 Card Judgement). (The legacy gateway session surface is not part of the current offering.)
GET /api/v1/mac88/status→ provider status: engine state and per-family availability.

Ezugi (live tables, wallet-bound)

Ezugi live roulette runs through the bet API: bets debit the player's seamless wallet and settle from the table's real results. Two tables are in scope — Automated Roulette (table 5001) and EZ Dealer Roulette (table 481000) — chosen per call with the game field ("auto" default, "dealer"); one table session serves one player at a time. On 5001, straight-up numbers and all 12 outside spots (columns, dozens, even-money) are supported; on 481000, straight-up numbers. The wider Ezugi catalogue (71 titles) is listed in the games browser.

EndpointDescription
POST /api/v1/ezugi/launchBody: { "playerId": "…", "game": "auto" } (game optional: "auto" | "dealer") → 200 { playerId, playerName, playUrl, balance, provider: "ezugi", tableId: "5001", gameType: "AutomatedRoulette" } — opens the table session for your player; the launch binds the session that makes bets work, and play is through the bet API. Table in use by another player with open bets → 409 {"code":"EZUGI_SEAT_BUSY"}; session cannot be established → 502 {"code":"EZUGI_SESSION_UNAVAILABLE"}.
POST /api/v1/ezugi/betBody: { "playerId": "…", "number": 7, "stake": 10, "ref": "your-ref", "game": "auto" } — straight-up roulette, number 0–36 (outside spots on 5001 by selectionId: 700–702 / 800–802 / 900–905), stake ₹10–5000 on straight-up, price 36. → 200 { ok: true, betRef, selection, stake, state, roundId, price: 36, payout, bet } where state is "settled" (result applied to the wallet), "void" (provider rejected; debit returned in full) or "pending" (fired, result pending — settlement lands later; poll wallet transactions). Errors: 400 INVALID_SPOT / STAKE_BELOW_MIN / STAKE_ABOVE_MAX · 402 INSUFFICIENT_WALLET (pre-check, no record created) · 409 DUPLICATE_REF / EZUGI_SEAT_BUSY · 502 EZUGI_SESSION_UNAVAILABLE.
GET /api/v1/ezugi/status→ engine and table-session status; games lists both roulette variants. The bound player's name is shown only when that player belongs to your client.

Examples

Launch a seamless game — the play URL is issued for your player and bound to their wallet; treat it as a secret.

curl -X POST https://hudio.live/api/v1/turbo/launch -H "x-api-key: YOUR_KEY" -H "content-type: application/json" -d '{"playerId":"PLAYER_ID","slug":"dice"}'

→ 200
{
  "playerId": "…", "playerName": "…", "slug": "dice", "title": "Dice",
  "playUrl": "…/oe/play/dice?player=…",
  "balance": 500
}

A provider outside the offering

curl -X POST https://hudio.live/api/v1/aura/launch -H "x-api-key: YOUR_KEY" -H "content-type: application/json" -d '{"playerId":"PLAYER_ID","provider":"live-dealer-betslip","gameId":"56967"}'

→ 503   { "error": "provider not available in the current offering", "code": "PROVIDER_NOT_AVAILABLE", "provider": "aura" }

Resellers, clients, key binding & earning models

Operators can organise API consumers into resellers and clients in the admin (Resellers / Clients tabs). A client optionally sits under one reseller, or is direct. An API key can optionally be bound to one reseller or one client when it is created; unbound keys keep working exactly as before. Usage (API-call counts) is attributed per entity in the admin Usage view by joining the request log to each key's binding.

Suspension: suspending a client rejects that client's bound keys with 403 {"error":"…","code":"ENTITY_SUSPENDED"}. Suspending a reseller does the same for reseller-bound keys and for the keys of every client under that reseller, until the entity is reactivated. Unbound keys are never affected.

Earning note: each reseller and client carries an earning model set by the operator — GGR (% of net win), commission (% of turnover) or rent (flat fee per period). Per-client turnover, returns, GGR and the clientShare earning are computed from settled bet data under that model and served at GET /api/v1/usage and in the admin usage view (basis stamped/reconstructed/mixed).

The current offering & refusals

Client portal

Each client also gets a web portal at https://hudio.live/portal: sign in with your client ID + portal password (portal credentials are issued separately by the operator — they are not your API key) to view your own players and balances, your players' wallet transactions, and your usage / GGR figures — the same ledger and bet aggregation behind GET /api/v1/usage. The portal is read-only and shows only the signed-in client's own data; a suspended client cannot sign in.

Errors

HTTPShapeMeaning
403{"error":"bound client/reseller '…' is suspended","code":"ENTITY_SUSPENDED"}The API key is bound to a suspended client or reseller (or, for a client key, its parent reseller is suspended). Reactivating the entity in the admin restores access.
401{"error":"invalid or missing API key","code":"UNAUTHORIZED"}No x-api-key / Bearer header, or the key is unknown / revoked.
400{"error":"invalid JSON body","code":"BAD_JSON"}Request body was not valid JSON. A missing required field returns 400 with "code":"BAD_REQUEST" instead.
502{"error":"gateway unreachable","code":"GATEWAY_DOWN"}The internal provider gateway is down; the platform restarts it automatically.
503{"error":"provider not available in the current offering","code":"PROVIDER_NOT_AVAILABLE"}The provider or surface is not part of the current offering (carries provider). Returned on launch/bet calls for non-offered providers, the panel catalogue (/api/v1/upstream/*) and the legacy gateway session surface.
4xx/5xx{"error":"…","code":"…"}Provider/gateway errors pass through with their message and code. A code of EVIDENCE_GAP means the requested operation is not available for that provider yet — the message names what is missing.
403{"code":"CLIENT_SCOPE_REQUIRED"}Wallet, seamless-provider and usage routes need an API key bound to a client.
404 / 403{"code":"PLAYER_NOT_FOUND"} / {"code":"PLAYER_SUSPENDED"}Seamless scope: a player outside the caller's client is indistinguishable from nonexistent (404); a suspended in-scope player is 403.
402{"code":"INSUFFICIENT_WALLET"}Wallet debit or bet stake pre-check exceeds the player's balance; nothing moves. Wallet credit/debit validation also returns 400 BAD_AMOUNT / BAD_REF; player creation returns 409 PLAYER_EXISTS.
409{"code":"DUPLICATE_REF"}The caller's bet ref was already used (all seamless providers).
409 / 202{"code":"EVO_SEAT_BUSY"} / {"code":"EVO_SESSION_OPENING"}The Evolution table session is in use by another player / still opening for yours — retry shortly.
409{"code":"EZUGI_SEAT_BUSY"}The Ezugi table session is in use by another player with open bets. EZUGI stakes outside ₹10–5,000 return 400 STAKE_BELOW_MIN / STAKE_ABOVE_MAX.
402{"code":"INSUFFICIENT_FUNDS_UPSTREAM"}Mac88: the provider declined the fired bet on its own account's funds; our debit was returned in full. Mac88 also returns 504 WINDOW_TIMEOUT, 400 TITLE_OPAQUE / TITLE_UNKNOWN / TITLE_NOT_ON_SESSION / BET_TYPE_NOT_EVIDENCED, 502 MAC88_ENGINE_UNAVAILABLE / MAC88_BET_FAILED.
400 / 404 / 409{"code":"INVALID_SPOT"} / {"code":"GAME_NOT_FOUND"} / {"code":"ROUND_NOT_FOUND"}Spot, game-slug and round validation across the seamless providers (INVALID_SPOT carries validSpots; GAME_NOT_FOUND carries validSlugs).
503{"code":"PROVIDER_NOT_READY"}A registered seamless capability is not live yet (carries provider, capability, tier).

Provider coverage

ProviderGamesCoverage
Evolution312312 live-casino tables — blackjack, baccarat, roulette, game shows and more — through the hosted client, with the in-game balance bound to your player’s wallet. Browse games →
Ezugi71Live roulette tables through the bet API, drawn from Ezugi’s 71-title live-dealer catalogue. Browse games →
Mac88 AGX40Baccarat and table-game titles through the bet API. Browse games →
Blackbuck (Savage)1Live crash betting through the hosted client and API. Browse games →
Turbo (own-engine)2424 instant games on the platform’s own engine — dice, mines, plinko, towers and more — settled instantly against your player’s wallet. Browse games →
BetGames (own-engine)1313 own-engine titles — lotto, poker and card games with published paytables. Browse games →
CrashLive (own-engine)9Crash titles on the platform’s own engine. Browse games →
Spribe (own-engine)8Own-engine titles, including Aviator-style crash, mines and plinko. Browse games →
Mac88 (own-engine)22 own-engine titles from the Mac88 family. Browse games →
RoyalAdmin (own-engine)1Roulette on the platform’s own engine. Browse games →