SDK Real-Time Callback Events

Updated on November 4, 2025

The SDK automatically sends real-time JSON responses to your application whenever important changes happen across events or markets. These responses are not requests, but push-style event notifications. These will be sent as POST method to your receiver system.

Use them to:

  • Update live odds
  • Handle market status
  • Score card update (html)
  • Track active/inactive event states

This section documents each callback format with:

  • Sample Payload
  • Glossary of keys
  • Recommended Usage

Callback: Event or Market Active / Inactive

This callback is triggered when an event or market becomes active or inactive. Common use cases include enabling/disabling UI components or odds tracking.

Sample Payload

Event Callback

{
“event”: {
“eid”: 34267069,
“si”: 4,
}
}

Market Callback

{
  "market": {
    "mid": "mid",
    "eid": 34267069,
    "si": 1
  }
}

Note : Only the above response will be send respectively to identify the event or market which is updated. No Additional keys will be provided.

Scorecard Callback

{
  "score": [
    {
      "data": "HTML DOCUMENT",
      "eid": 34267069
    }
  ]
}

Connection Callback

Received when the SDK successfully connects or disconnects from the platform.

  • connect: true indicates a successful connection.
  • connect: false indicates a disconnection.
{
  "connect": true
}

OR

{

  "connect": true

}

Glossary of Keys

KeyTypeDescription
eventObjectContains details about a specific event
marketObjectContains details about a specific market
scoreArrayArray of scorecard objects (used for live score HTML injection)
eidIntegerEvent ID – uniquely identifies a sports event
siIntegerSport ID – indicates which sport the event/market belongs to
midStringMarket ID – uniquely identifies a betting market
dataStringContains HTML markup for the scorecard (used for frontend rendering)