MangoPlay Partner Streaming API (1.0.0)

MangoPlay issues you a PartnerCode and a PartnerSecret. Send both as HTTP headers on every REST call, and in the handshake on the WebSocket.

Every failure answers the same way — 404 with {"code": 4040, "message": "Partner not found."} — whether the code is unknown, the secret is wrong, or the account is suspended. That is deliberate: a different answer per case would let anyone probe which codes exist. Our side logs the real reason, so if you are stuck, contact us and we can tell you which one it was.

Each link is signed and valid for streamTtlSec seconds (300 today). stream.expire is the exact epoch second it dies, so you can schedule a refresh instead of parsing our query string. Call /rooms again before then and swap the URL in your player. An expired link is rejected by the CDN, not renewed.

A room with no stream configured is still listed, just without the stream field — that says the room exists but has no video yet, which is a different problem from the room not being there at all.

Socket.IO, WebSocket transport only:

import { io } from 'socket.io-client'

const socket = io('wss://ws.mangoplay.com/partner', {
  transports: ['websocket'],
  auth: { partnerCode: 'YOURCODE', secret: 'your-secret' },
})

socket.on('partner_event', (e) => {
  switch (e.event) {
    case 'partner.round.opened':         /* start your countdown */ break
    case 'partner.round.betting_closed': /* close your bet UI */    break
    case 'partner.round.result':         /* show the result */      break
    case 'partner.round.cancelled':      /* withdraw the round */   break
    case 'partner.room.maintenance':     /* add or remove room */   break
  }
})

If your client cannot set handshake auth, ?partnerCode=...&secret=... on the URL works too. A bad credential fails the connection with UNAUTHORIZED — again without saying which half was wrong.

Every event is delivered under two names. Pick one; listening to both counts everything twice.

On connect you are subscribed to every room you have access to, including rooms we add later. To narrow it:

socket.emit('subscribe', { roomCodes: ['BC-A', 'HL-B'] }, (ack) => {
  // ack.rooms = the rooms you are now on
})
socket.emit('unsubscribe', { roomCodes: ['BC-A'] })
socket.emit('subscribe_all')   // back to everything you may see

Rooms you have no access to are dropped from the list silently, and the ack tells you what actually took effect. socket.emit('ping') answers pong with a timestamp if you want a liveness check of your own on top of Socket.IO's.

server_shutdown means we are restarting: reconnect rather than waiting for a timeout. Socket.IO's own reconnect handles this if you leave it enabled.

Closing bets is a time, not only an event. round.opened carries bettingEndTime, so you can count down locally from the moment the round starts. We also send round.betting_closed when that time arrives — or earlier, if the dealer closes the round early — but treat it as a convenience. If it arrives late or not at all because of a restart or a network blip, your countdown is still correct.

Events can repeat. On our side a duplicate is possible where a lost event is not, so we chose duplicates. De-duplicate on roundNo together with event.

Every bet in a MangoPlay game sits on a hole — one betting slot on the table. These are the keys your UI renders, and the same keys appear in player bet records on the operator side, so labelling them the way we do keeps the two readable together.

The tables below are generated from the live game client, so they are the holes a player can actually bet today, not every key our result engine can produce. Thai is the wording shown in our own client; English is our own client's wording too, so a player moving between your product and ours sees the same name for the same slot.

A few notes before you build from this:

• game is the value you receive in /rooms and in every event, so you can key your hole table off it directly.
• Hole keys are stable. They are what settlement is calculated from on our side, so we do not rename them; new holes are added, old ones are not repurposed.
• Some keys contain a dot — KHUD_1.1 in Roll a Dice and Belangkai. Keep them as-is; do not normalise to an underscore, or you will not match our records.
• KHUD_1 to KHUD_4 have no translation yet in either language file, so they are shown here as —. Use "ขุด 1" … "ขุด 4" until we fill them in; we will update this page when we do.
• Hilo has no HOLE_1_HIGH or HOLE_2_HIGH slot — those combinations exist in the result engine but are not offered as bets.

game = Baccarat — 10 holes

game = TigerDragon — 12 holes

game = Hilo — 36 holes

หลุมเดี่ยว · Single holes

หลุม + ต่ำ · Hole with low

หลุม + สูง · Hole with high

คู่หลุม · Pairs

สามหลุม · Triples

สูง / ต่ำ / ไฮโล · High, low, hilo

game = Sicbo — 52 holes

หลุมเดี่ยว · Single numbers

คู่ผสม · Number pairs

เด้งเจาะจง · Specific doubles

ตองเจาะจง · Specific triples

แต้มรวม · Totals

สูง / ต่ำ / คู่ / คี่ / ตอง · High, low, odd, even, any triple

game = RollADice — 42 holes

เต็ง · Single face

อาหาร · Three faces

ขุด · Khud

กั๊ก · Kuk

เลี่ยม · Liam

game = Balangkai — 42 holes

เต็ง · Single face

อาหาร · Three faces

ขุด · Khud

กั๊ก · Kuk

เลี่ยม · Liam

game = FunGrasp — 4 holes

Every event carries these three fields, so one handler can cover them all:

A new round is open and accepting bets.

{
  "event": "partner.round.opened",
  "roomCode": "BC-A",
  "at": 1793000000000,
  "roundNo": "BC-A20261030120000",
  "game": "Baccarat",
  "startTime": 1793000000000,
  "bettingEndTime": 1793000030000,
  "shoeNo": 7,
  "roundCount": 23
}

Bets are closed for this round. Sent when bettingEndTime arrives, or earlier if the dealer closes the round early — in which case it always arrives before the result.

{
  "event": "partner.round.betting_closed",
  "roomCode": "BC-A",
  "at": 1793000030300,
  "roundNo": "BC-A20261030120000",
  "game": "Baccarat"
}

The round is closed and the result is final.

{
  "event": "partner.round.result",
  "roomCode": "HL-A",
  "at": 1793000045000,
  "roundNo": "HL-A20261030120000",
  "game": "Hilo",
  "result": "3/4/5",
  "endTime": 1793000045000
}

The round was cancelled and has no result. Anything you showed for it should be withdrawn.

{
  "event": "partner.round.cancelled",
  "roomCode": "BC-A",
  "at": 1793000040000,
  "roundNo": "BC-A20261030120000",
  "game": "Baccarat",
  "reason": "Card misdeal"
}

A room entered or left maintenance. isMa: true means there is nothing to watch, so take it off your screen; false means it is back. This is the same condition that keeps a room out of /rooms, pushed to you as it changes — /rooms alone would only tell you at your next call.

{
  "event": "partner.room.maintenance",
  "roomCode": "BC-A",
  "at": 1793000100000,
  "isMa": true,
  "roomName": "Baccarat A"
}

Rooms and signed stream URLs.