6.0 General

As explained in Asynchronous Server Message Format, the asynchronous messages sent by MollyBet API to your software have a structure:

{
    "ts": timestamp,
    "data": [
        [ code1, payload1 ],
        [ code2, payload2 ],
        ...
    ]
}

This section explains, for each code type, the format of the received payload.

Please note that the WebSocket might send data with a code not specified here: your client should ignore any message it doesn't understand or it shouldn't process.

Available message types:

• 6.1 Connection Messages
  • 6.1.1 sync: client initialised
  • 6.1.2 response: websocket command completed
  • 6.1.3 info: stream connection information
  • 6.1.4 connection_closed: client is being disconnected
• 6.2 Event Messages
  • 6.2.1 event: event added or updated
  • 6.2.2 remove_event: event no longer exists
  • 6.2.3 event_time: current time of an in-running event
  • 6.2.4 event_score: current score of an in-running event
  • 6.2.5 event_red_cards: current red cards of an in-running event
  • 6.2.6 offer: offer added or updated
  • 6.2.7 remove_offer: offer no longer exists
  • 6.2.8 event_exchange_dark_liquidity: dark liquidity availible on each line of the event
  • 6.2.9 clear_events: remove all events and offers
• 6.3 Betslips Messages
  • 6.3.1 betslip: betslip opened or updated
  • 6.3.2 pmm: price and min/max stake returned by a bookie
  • 6.3.3 betslip_closed: betslip no longer exists
• 6.4 Orders Messages
  • 6.4.1 order: an order has been placed or updated
  • 6.4.2 bet: bet placed or updated
• 6.5 Other Messages
  • 6.5.1 balance: customer balance and open stake
  • 6.5.2 xrate: exchange rate to GBP updated