Betting - Live statistics (coming soon)

Provides an aggregated list of stats such as player/team runs, wickets etc used to build a scorecard.

The statistics websocket contains a live team and player aggregation of key stats happening within a match. This websocket is typically for clients wanting to integrate an aggregated scorecard to facilitate live betting markets.

You should receive a new update any time a key action is completed and this websocket is crucial for powering live scores and match actions. The authentication token provided will be required to make a connection to this websocket endpoint. Once you have the API token, any further data that you send over the connection will be ignored. This endpoint sends heartbeats in-between data packets to let you know that it is still connected.

Endpoint URL

Aggregated live statistics

CONNECT wss://dde-streams.data.imgarena.com/{sport}/fixtures/{fixtureId}/statistics

Path Parameters

Name
Type
Description

sport*

String

soccer

fixtureId*

UUID

Unique id of a requested fixture.

Query Parameters

Name
Type
Description

speed

String

this can be “fast” or “normal”. Default is normal and only applicable for offline matches

startPosition

Integer

default is 0. This is how many events to skip from the beginning of the list of events. e.g. 5 would be start sending events from the 5th event received for that websocket. This is a useful feature if you want to continue without getting all the events again from the beginning when you reconnect

Headers

Name
Type
Description

Accept*

String

application/vnd.imggaming.dde.api+json;version=1

Connection

String

keep-alive

{
    The supplied authentication is invalid
}

Authentication

We don't look at the header for websockets. Instead we expect the client to push through that auth message immediately on connecting in the following format.

{"authToken": "ACCESS_TOKEN"}

Polling limits

IMG Arena monitor the incoming traffic from our customers and strive to ensure that traffic is controlled, in-keeping with our guidelines and not unnecessarily excessive. We would suggest a polling rate of 5 requests per second, whilst we strive towards implementing rate limiting.

Response Fields

seqNum integer

The sequence number

traceId uuid

Tracing Id for logs

version integer

The version number

finished boolean

Whether the match has finished or not Values are true or false

fixtureId uuid

The unique id of the match

timestamp timestamp

The timestamp of the file and it's usually the time the latest action update has happened

Aggregated player action statistics

Aggregated team sports statistics

PreviousBetting - Live actionsNextAction Types

Last updated