Settlement is a message that indicates a settlement of a specific bet/bets, what differs settlement messages from ordinary market messages are the Bet Status (3) and the "Settlement" property - Settlement Options.
XML
<Message> <Header CreationDate="2018-10-03T20:41:29.248Z"> <Type>35</Type> <MsgGuid>572b65ab-1393-41ae-a4ff-f936f7bb3036</MsgGuid> <ServerTimestamp>1538599289420</ServerTimestamp> </Header> <MessageBody> <Events> <Event FixtureId="3882981"> <Markets> <Market Id="2" Name="Under/Over"> <Bets> <Bet Id="20803443503882981" Name="Over" Line="4.0" BaseLine="4.0" Status="3" StartPrice="1.0" Price="5.0" Settlement="1" ProviderBetId="8" LastUpdate="2018-10-03T20:41:29.138Z" IsChanged="1" /> <Bet Id="2907588603882981" Name="Under" Line="4.0" BaseLine="4.0" Status="3" StartPrice="1.0" Price="1.16" Settlement="2" ProviderBetId="8" LastUpdate="2018-10-03T20:41:29.138Z" IsChanged="1" /> </Bets> </Market> </Markets> </Event> </Events> </MessageBody> </Message>
Json
{ "Message": { "Header": { "Type": "35", "MsgGuid": "572b65ab-1393-41ae-a4ff-f936f7bb3036", "ServerTimestamp": "1538599289420", "CreationDate": "2018-10-03T20:41:29.248Z" }, "MessageBody": { "Events": { "Event": { "Markets": { "Market": { "Bets": { "Bet": [ { "Id": "20803443503882981", "Name": "Over", "Line": "4.0", "BaseLine": "4.0", "Status": "3", "StartPrice": "1.0", "Price": "5.0", "Settlement": "1", "ProviderBetId": "8", "LastUpdate": "2018-10-03T20:41:29.138Z", "IsChanged": "1" }, { "Id": "2907588603882981", "Name": "Under", "Line": "4.0", "BaseLine": "4.0", "Status": "3", "StartPrice": "1.0", "Price": "1.16", "Settlement": "2", "ProviderBetId": "8", "LastUpdate": "2018-10-03T20:41:29.138Z", "IsChanged": "1" } ] }, "Id": "2", "Name": "Under/Over" } }, "FixtureId": "3882981" } } } } }
Model
Element | Data Type | Description |
---|---|---|
Market.Id | int | The unique ID of the market |
Market.Name | string | The name of the market |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article