Market/Bet Message Handling

To reduce message size and enhance message transfer speed, messages are transmitted in delta formats, containing only changes. Each message includes a reference to the Fixture, Market, and Bet (refer to Markets section) to which they pertain.

Example

The following is a snapshot message for 1X2 market:

<Message>
  <Header>
    <Type>3</Type>
    <MsgGuid>6fbee8ea-bb90-45fb-bb53-1abe720bf618</MsgGuid>
    <ServerTimestamp>1491131330</ServerTimestamp>
  </Header>
  <Body>
    <Events>
      <Event FixtureId="3115994">
        <Markets>
          <Market Id="1" Name="1X2">
            <Bets>
              <Bet Id="11287986013115994" Name="X" Status="1" Price="4.2" StartPrice="1.0" LastUpdate="1491097568314" ProviderBetId="0" />
              <Bet Id="11287986593115994" Name="2" Status="1" Price="4.5" StartPrice="1.0" LastUpdate="1491097568314" ProviderBetId="0" />
              <Bet Id="11287986563115994" Name="1" Status="1" Price="1.571" StartPrice="1.0" LastUpdate="1491097568314" ProviderBetId="0"/>
            </Bets>
          </Market>
        </Markets>
      </Event>
    </Events>
  </Body>

The message is linked to Fixture Id 3115994 as seen in the example above.

A delta message will be sent as follows:

<Message>
  <Header>
    <Type>3</Type>
    <MsgGuid>b6b66be0-e006-4f97-b66d-c10da8b00c99</MsgGuid>
    <ServerTimestamp>1491132216</ServerTimestamp>
  </Header>
  <Body>
    <Events>
      <Event FixtureId="3115994">
         <Markets>
          <Market Id="1" Name="1X2">
           <Bets>
               <Bet Id="11287986013115994" Name="X" Status="1" Price="5.2" StartPrice="" LastUpdate="1491097568314" ProviderBetId="0" />
            </Bets>
          </Market>
        </Markets>
      </Event>
    </Events>
  </Body>
</Message>

This message contains the ID of the Fixture as a reference, as did the previous message, but the only bet in it is the updated one. In this example, the price of the bet “X” bet was updated.

Last updated