Betbalancer Live Odds Integration Manual

XML feed v1.00

1. Introduction

2. General Information

3. System Communication

4. General Configuration

5. XML Configuration

6. Information per Sport

7. Overview XML examples

1. Introduction

We deliver Live odds for sport events. This document describes the functionality and exchanging of messages for the Live Odds

system. The system is based on servers located in our, and clients at different bookmaker sites. The bookmaker client needs to be

implemented in accordance with this document. We will not deliver the client software to the bookmakers.

1.1 Document structure

In this chapter you can find a quick overview on how this document is structured, and a quick description for each chapter.

General information

The general information chapter provides an overview on available access methods, environments, and client system requirements.

System communication

In this chapter you will find all neccessary information regarding the communication between the our system and a client system,

exchanged in the XML format.

General configuration

In this chapter you will find a quick overview on our general configurations. These configurations are separate from the XML

configurations.

XML configuration

This chapter contains an overview on different XML configurations that are included in the feed. When we release a new feature it will

not be automatically included by default, so clients will need to activate new features before they will receive them.

Information per sport

In this chapter you will find detailed information about each individual sport we currently provide a service for. The chapter is

currently contains the following information about each sport:

Sport specific XML features

XML configurations

Match statuses

Overview XML examples

This chapter contains various types of XML examples. If the XML example(s) you are looking for are not provided in another chapter, it

is likely that they can be found in this section.

2. General Information

2. General information

We deliver the complete match administration including Betstops on dangerous situations, and Betstarts. According to the match, all

odds suggestions are updated constantly while a match is in progress. Please note that all ticket handling and automated risk

management has to be implemented on the client side.

2.1 Access Methods

XML messages describing events happening during the match are sent through a socket connection to the client application. The

system supports plain connection (no SSL). Please note that each account is only able to have 2 open connections at the same time.

2.1.1 Test environment

Clients testing their systems can connect to this server. The connection details are:

Hostname: liveoddstest.betbalancer.com

Port: 1980

2.1.2 Live environment

Connection details for the live environment are:

Hostname: liveodds.betbalancer.com

Port: 1980

2.2 Access restrictions

For security reasons we only allow connections from IP addresses that have been added to our whitelist. It is therefore necessary that

you provide us with the relevant IP addresses from which you are accessing our server before using the production server. Otherwise

your login requests will not be successful. The test server has a separate whitelist, so be sure to take note of that. Testing should be

done via the test server before going live.

There is also a limitation on how many requests you can send to the server. The limits are as follows:

1. Maximum 500 requests in a 5 minute period

2. Maximum 100 logins in a 10 minute period

3. Maximum 2000 requests in a 1 hour period

4. Maximum 800 matches in requests in a 5 minute period

5. Maximum 10.000 requests in 24 hour period

If you exceed these limits, your account will be automatically suspended. The account can be reactivated by our support department

immediately, once the spamming has been fixed. In this case you will receive automatically an email alerting you about the account

suspension.

To ensure that your connection to our server is receiving data fast enough, we have also added some security mechanisms to avoid

an XML message queue

1. Connection will be disconnected if more than 10 files in queue are older than 1 minute

2. Connection will be disconnected as soon as the queue size has exceeded 2,000 files

2.3 Requirements of client systems

We expect the client system to be able of doing the following:

Keep a clock in sync with the time from our system according to the timestamp from the XMLFeed.

Stop/cancel bets when no alive-message has been received from the system for 20 seconds.

Stop/cancel bets when a message with status=”betstop” has been received according to the time and timestamp in the

message.

Handle deactivation of matches/oddstypes/oddsfields accordingly.

Evaluation of the bet outcomes during match.

3. System Communication

3 System communication

The communication between our system and the client system is done by exchanging messages in the XML format. This chapter

provides you with information about the different XML messages sendt from our system and a client system.

3.1 XML messages sent from our system

Our system sends out different types of XML messages. The content of those messages can differ, but the root element is always the

same, BetbalancerLiveOdds:

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

current

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1260866108600

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status Keyword which describes what the String, one of the following values:

LiveOdds content of the XML message will loginok

be like. In the upcoming chapters loginfailed

the keywords and content are de- betstop

scribed in more detail. betstart

alive

clearbet

rollback

change

score

cards

error

cancelbet

undecancelbet

meta

timestamp Time from server in UTC which the Timestamp in UTC

client needs to sync to.

replytype Optional attribute. String which String, one of the following values:

identifies the type of message com- error

ing from our system. This current

attribute is included if the message register

is a reply to an error, current, un- unregister

register, register and score request scoreandcardsummary

from the client system.

3.1.1 Delta match messages

After a full match update is received, most updates will be sent real time as delta messages. In these messages only the new data is

sent, and they could be considered a 'light' version of the full match information, containing less attributes, and by default no

subelements (unless the value of that element was changed) in the <match> element. Delta messages usually contain only one

event at a time, and if the value of any of the match statistics changed, this will be included in the delta messages.

Example: If a player receives a yellow card, a delta message is generated and sent out to the client system. This message contains

both a yellow card event in the event list, and the yellow-element is included in the match summary.

XML example

<

match

betstatus

=

"

BETSTOP

"

connectionstatus

=

"

1

"

dc

=

"

1

"

feedtype

=

"

delta

"

matchid

=

"

6971324

"

>

<

yellow

t1

=

"

1

"

t2

=

"

0

"

/>

<

events

>

<

event

id

=

"

490157138

"

info

=

"

Yellow card [T1]

"

mtime

=

"

05:55

"

side

=

"

home

"

stime

=

"

1445118003431

"

type

=

"

40

"

/>

</

events

>

</

match

>

The event types used in delta updates are the same as for full match updates.

3.1.2 Incremental id

To make sure that the client system has received all messages from our system, all messages sent out have an incremental id, as

seen in the attribute msgnr. inside the match element.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1199435558847

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

msgnr

=

"

5

"

score

=

"

-:-

"

status

=

"

not_started

"

/>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstop

"

time

=

"

0

"

timestamp

=

"

1199435635925

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

6

"

score

=

"

-:-

"

status

=

"

not_started

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match msgnr

The incremental id for the

message Number. Starts on 1 for each match,

of the match. Only updated when and increments on each change.

the state of the match changes.

Alive messages, meta-

information

and login response messages will

not increment this number.

active

If this attribute has a value of 1 if

it is Integer, possible values:

in our Live Odds product

(meaning 0

we will be sending out live odds

on 1

this match). The attribute will

have

a value of 0 if it is not in our Live

Odds product, meaning we will

not

send out live odds on this match.

However, we might still send

meta

messages for this match.

3.1.3 Alive Message

Please note: To ensure that the client system has a working connection to our system, each 10 seconds an alive message gets sent.

If the client hasn’t received an alive message in 20 seconds, they shouldn’t accept any bets for any matches until the connection is

stable again. Clients should not accept bets from matches which are not included in the alive message. If the connection to our server

is lost, the client needs to stop bets on all matches until a stable connection is established again.

XML example

<

BetbalancerLiveOdds

xmlns

=

'

http://www.betbalancer.com/BetbalancerLiveOdds

'

status

=

'

alive

'

timestamp

=

'

1413791030423

'

>

<

Match

active

=

'

1

'

betstatus

=

'

started

'

gamescore

=

'

0:0

'

matchid

=

'

6263978

'

msgnr

=

'

126

'

server

=

'

1

'

score

=

'

0:0

'

setscore1

=

'

3:4

'

status

=

'

1set

'

tiebreak

=

'

false

'

/>

<

Match

active

=

'

1

'

betstatus

=

'

started

'

gamescore

=

'

0:30

'

matchid

=

'

6264696

'

msgnr

=

'

188

'

server

=

'

1

'

score

=

'

0:0

'

setscore1

=

'

5:3

'

status

=

'

1 set

'

tiebreak

=

'

false

'

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status

What kind of information

is con- String

LiveOdds tained in the message. 'alive' (for alive messages)

Match matchid The id of the match. Number

msgnr

The incremental id for the

last Number > 0

change message for the

match.

score

Current score for the

match. For String

more information see

chapter 3.1.8.

Format: '[score1 - [score2]

...'

betstatus

Current betstatus for the

match. String

For more information see

chapter

started = Match is in

betstart

3.1.10.

stopped = Match is in

betstop

active

If this attribute has a

value of 1 if it is Integer, possible values:

in our Live Odds product

(meaning 0

we will be sending out

live odds on 1

this match). The attribute

will have

a value of 0 if it is not in

our Live

Odds product, meaning

we will not

send out live odds on this

match.

However, we might still

send meta

messages for this match.

Note

Alive messages contain summarized information about the matches live odds are supplied for at the time given. Please note that

information about the odds are not included in those messages.

3.1.4 Odds

The main purpose of our system is to supply information about odds. The odds are listed per match. Each Match element contains all

markets which will be delivered for this match. Per market the odds are added in subelements called OddsField, if that market is

currently active.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

5984472

"

matchtime

=

"

38

"

msgnr

=

"

155

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners

"

id

=

"

57178832

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

7.5

"

subtype

=

"

126

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

typeid

=

"

373

"

>

2.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

typeid

=

"

374

"

>

1.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

ftr

=

"

-0.25

"

id

=

"

57178580

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1.25

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

typeid

=

"

17

"

>

2.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

18

"

>

1.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Corner Handicap

"

id

=

"

57173070

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1.5

"

subtype

=

"

123

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

active

Whether the market is currently

ac- Integer

tive for this match. If the market 1 = active

resentation which tells what kind

ois not active no odds (OddsField 0 = not active

subelements) will be present.

changed Whether the market is updated String

since last time. true = The market is updated

false = the market is not updated

combination This attribute is no longer in use, 0

and will therefore always have

the

value 0.

freetext

Optional, only included if the

mar- String

ket is a freetext market. Textual

rep-

resentation which tells what kind

of

freetext market this is.

id This is a unique identifier for this Number

particular market in this match,

and

will be used whenever this

market

are sent out. This id will be used

when this market is cleared.

specialoddsvalue This indicates the total value, String

handicap value or freetext de-

tails. Used for the following odds

types: total, handicap and free-

text3way/2way/nway

ftr Optional, only included in soc- Number

cer matches if the correspond-

ing XML configuration (see

chapter

6.19.2.8) is activated. Contains

the

handicap value for the rest of the

match.

subtype

Optional, only included if the

mar- Number

ket is a freetext market. Identi-

fier which tells what kind of

freetext

market this is.

type

Textual representation of the

mar- String.

ket type.

See the list with possible market

types

and ids below.

typeid

This is a numeric id for the

market Number

type, and will be the same for

that

See the list with possible market

types

market type in all matches. and ids below.

OddsField active

Whether this odds for this market

is Integer

still offered. 1 = active

0 = not active

type The name of the odds field. String

typeid Optional, only included if the cor- Integer

responding XML configuration

(see

chapter 5.1.1.22) is activated.

Con-

tains a numeric identifier of the

odds field.

3.1.4.1 Market types

Market Value type attribute Value typeid attribute

3-way 3w 2

Handicap hc 4

Total to 5

freetext3way ft3w 6

freetext2way ft2w 7

freetextnway ftnw 8

We constantly extend our betting offer and markets offered. If you have special requests, please forward this to our support team,

and we will collect all requests and consider them for upcoming development.

3.1.5 Odds change

When an odds change occurs, all the markets for that match will be updated and sent out. Only one match is included in a change

message.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

clock_stopped

=

"

0

"

matchid

=

"

1467300

"

matchtime

=

"

32

"

msgnr

=

"

31

"

remaining_time

=

"

8:49

"

score

=

"

13:10

"

setscores

=

"

0:0 - 5:5 - 3:5

"

status

=

"

4q

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

748814

"

specialoddsvalue

=

"

-3.5

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

748905

"

specialoddsvalue

=

"

87.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap for fourth period

"

id

=

"

748888

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

54

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian handicap for whole match,

including overtime

"

id

=

"

748867

"

specialoddsvalue

=

"

-4.5

"

subtype

=

"

38

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.8

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'change' (for odds change messages)

Odds active Whether the market is currently ac- Integer

tive for this match. If the market 1 = active

is not active no odds (OddsField 0 = not active

subelements) will be present.

changed Whether the market is updated String

since last time true = the market is updated

false = the market is not updated

OddsField active Whether this odds for this market is Integer

still offered. 1 = active

0 = not active

3.1.6 Match status

Change messages do not only get sent out when the odds for a match have changed, but also when the status of a match has

changed.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1413845886248

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

5650450

"

msgnr

=

"

5

"

score

=

"

-:-

"

status

=

"

not_started

"

>

</

Match

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1413846115107

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

5650450

"

matchtime

=

"

1

"

matchtime_extended

=

"

0:00

"

msgnr

=

"

6

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'change' (for status change mes-

sages)

Match status The status of the match. String

See full overview of match statuses

and related sports in chapter 6.

active If this attribute has a value of 1 if it is Integer, possible values:

in our Live Odds product (meaning 0

we will be sending out live odds on 1

this match). The attribute will have

a value of 0 if it is not in our Live

Odds product, meaning we will not

send out live odds on this match.

However, we might still send meta

messages for this match.

Overtime

For soccer, ice hockey, basketball, handball, rugby and futsal matches the status will change to 'ended' before it changes to 'ot'. It will

also change to 'ended' before it changes from 'ot' to 'pen'. When a match has status 'ended' you should wait until the match has been

removed from the alive message (see chapter 3.1.3) to know that the match is finished.

Note

A change message can indicate an odds change, a match status change, or both. Always make sure to check both when processing

the XML.

There are several XML configurations which will add match statuses for different sports during overtime:

Use additional match statuses for overtime - Chapter 5.1.1.14

Use additional match statuses for overtime/penalty ice hockey - Chapter 6.15.2.5

Use additional match statuses for overtime basketball - Chapter 6.5.2.2

3.1.7 Matchtime

The matchtime describes what playing minute the match is in. The matchtime is included in the following cases:

If the sport is soccer, handball or futsal and the match status is 1p, 2p, 1p_ot or 2p_ot.

If the sport is basketball and the match status is 1q, ,2q, 3q or 4q or ot.

If the sport is ice hockey and the match status is 1p, 2p, 3p or ot.

If the sport is American football and the match status is 1q, ,2q, 3q, 4q, pause1, pause2 or pause3.

If the sport is rugby and the match status is 1p, 2p, 1p_ot, 2p_ot or sd.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1413846115107

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

5650450

"

matchtime

=

"

1

"

msgnr

=

"

6

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match matchtime The playing minute of the match Number > 0

Several sports have additional matchtime related attributes. Those attributes have to be enabled in the XML configuration before they

are included in the feed:

American football: Remaining time and remaining time in period (chapter 6.1).

Basketball: Remaining time and remaining time in period (chapter 6.5).

Handball: Remaining time and remaining time in period (chapter 6.14).

Ice hockey: Match time, remaining time and remaining time in period (chapter 6.15).

Soccer: Extended matchtime (chapter 6.19).

Clock stopped information for basketball, ice hockey, handball and futsal (chapter 5.1.1.10).

3.1.8 Score information

The score of a match is always included in the XML, even if the score did not change.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1414364604992

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5867680

"

matchtime

=

"

1

"

msgnr

=

"

5

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match score Current score in the match. String

Format: '[homescore]:[awayscore]'

Before the match has started the value

will be '-:-'

setscores This will contain the scores for all String

periods/sets that have ended, over- Format: '[score1] - [score2] ...'

time (aggregated in case of multiple Example: '7:6 - 3:6'

overtimes) and penalty shootout).

Note

The setscores attribute is available for various sports, but only for tennis matches will it also include the score of the current set. For

example: '7:6 - 3:6 - 2:4'. This can be enabled for other sports too, have a look at chapter 5.1.1.18 for more information.

3.1.9 Livescore change (score/card)

Information about score changes and given cards are distributed in two different ways. First of all the updates are sent out as they

happen during the match. Additionally a full overview gets sent out at the end of the match, containing all the score and card changes.

Please note that these messages only indicate that key statistics of the match have changed, and should not be used for resulting

purpose as we have dedicated clearbet messages. For more information about bet clearing see chapter 3.1.11.

Score change

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1199435937143

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

matchtime

=

"

5

"

msgnr

=

"

29

"

score

=

"

1:0

"

status

=

"

1p

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

7966

"

player

=

"

P. Anderson

"

scoringteam

=

"

home

"

time

=

"

4

"

type

=

"

live

"

playerid

=

"

115622

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'score' (for score change messages)

Match score Current score in the match String

Format: '[homescore]:[awayscore]'

Before the match has started the value

will be '-:-'

Score away How many points the away team Integer

has.

home How many points the home team Integer

has.

id The unique identifier for this score Integer

change in this match.

canceled Whether the goal is canceled or 'True'= the goal was canceled

not. 'False'= the goal was not canceled

player The name of the player who scored String

the point. If not available the string will be empty

scoringteam What team scored the point. String

'home' = home team scored

'away' = away team scored

time Match time in minutes when the Integer

score change happened. If no time is known this is set to -1

type Type of score change String

'live' = Score during the match

playerid The id of the player. Integer

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.24.

3.1.9.1 Card change

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

current

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1260866108600

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'cards' (for card change messages)

Card canceled Whether the card is canceled or String

not. 'true' = the card was canceled

'false' = the card was not canceled

id The unique identifier for this card in Integer

this match.

player The name of the player who re- String

ceived the card. If not available the string will be empty

team What team received the card. String

'home' = home team scored

'away' = away team scored

time Match time in minutes when the Integer

score change happened. If no time is known this is set to -1

type Type of card String

Possible values:

yellow

yellowred

red

playerid The id of the player. Integer

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.24.

Note

The same card and the same score can be sent several times; this is used to update informa- tion, for example player name or time.

Always check the unique id of the score or card when processing them.

3.1.9.2 Score and card summary

At the end of the match an overview with all the score changes and given cards is sent.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1199436663643

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

78

"

score

=

"

1:2

"

status

=

"

ended

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

7966

"

player

=

"

P. Anderson

"

scoringteam

=

"

home

"

time

=

"

4

"

type

=

"

score

"

/>

<

Card

id

=

"

7967

"

player

=

"

P. Anderson

"

team

=

"

home

"

time

=

"

7

"

type

=

"

yellow

"

/>

<

Card

id

=

"

7965

"

player

=

"

A. Johnsen

"

team

=

"

away

"

time

=

"

4

"

type

=

"

yellow

"

/>

<

Score

away

=

"

1

"

home

=

"

1

"

id

=

"

7969

"

player

=

"

scoringteam

=

"

away

"

time

=

"

8

"

type

=

"

score

"

/>

<

Score

away

=

"

2

"

home

=

"

1

"

time

=

"

90

"

type

=

"

ft

"

/>

<

Score

away

=

"

2

"

home

=

"

1

"

id

=

"

7971

"

player

=

"

scoringteam

=

"

away

"

time

=

"

49

"

type

=

"

score

"

/>

<

Score

away

=

"

1

"

home

=

"

1

"

time

=

"

45

"

type

=

"

ht

"

/>

<

Card

id

=

"

7970

"

player

=

"

A. Johnsen

"

team

=

"

away

"

time

=

"

46

"

type

=

"

yellowred

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'score' (for score change overview if

match has ended)

Score type Type of score. Note that for all val- String

ues except 'score' no id attribute is Possible values:

available, as this is only summariz- 'score' = score change during match

ing the score during different mo- 'ht' = score on half time

ments of the match. 'ft' = score on full time

'ot' = score after overtime

'pen' = score after penalties

The values 'ot' and 'pen' are only in-

cluded if the corresponding XML con-

figuration (see chapter 5.1.1.25) is en-

abled.

3.1.10 Betstop and betstart

A betstop situation occurs when the betting markets are be closed. This happens when an event takes place during the match which

effects one or multiple markets. For soccer matches the following events would cause a betstop:

Goals

Red cards

Penalty

One on one situations

Free kicks within 20 meters

Match is interrupted temporarily

For other sports different events may cause a betstop.

There are also two administrative events which cause a betstop:

Loss of TV coverage

Loss of connection to the scout

The client system gets notified both when a betstop situation occurs, and once the markets are open again.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1199435558847

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

msgnr

=

"

5

"

score

=

"

-:-

"

status

=

"

not_started

"

/>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstop

"

time

=

"

0

"

timestamp

=

"

1199435635925

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

6

"

score

=

"

-:-

"

status

=

"

not_started

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'betstart' = match is in betstart

'betstop' = match is in betstop

time How many seconds before the Integer

timestamp the betstop occurred. If

the value of time is bigger than 0,

then betstop started at timestamp -

time seconds.

Match betstatus Whether the match is in betstart or String

betstop 'started' = match is in betstart

'stopped' = match is in betstop

3.1.11 Bet clearing

In case an event happens in a match which defines the outcome of a specific oddstype, our system sends out a clear- bet message.

Clearbet messages contain information about the outcome of bets, and in some cases also whether the bet was voided or not. If the

bet is (partly) voided, the voided part should be refunded to the customer.

All possible combinations of outcome and voidfactor:

outcome='0' and no voidfactor: Lose entire bet

outcome='1' and no voidfactor: Win entire bet

outcome='0' and voidfactor='1': Refund entire bet

outcome='1' and voidfactor='0.5': Refund half bet and win other half

outcome='0' and voidfactor='0.5': Refund half bet and lose other half

Please note: Evaluation of the bet outcomes is the responsibility of the Client system.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

clearbet

"

time

=

"

1

"

timestamp

=

"

1199435884237

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

1:0

"

matchid

=

"

661373

"

matchtime

=

"

4

"

msgnr

=

"

21

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13786

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

1

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

x

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

2

"

/>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

clearbet

"

time

=

"

2

"

timestamp

=

"

1266483496355

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

0:1

"

matchid

=

"

935448

"

msgnr

=

"

19

"

status

=

"

paused

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

311538

"

specialoddsvalue

=

"

1.25

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

under

"

voidfactor

=

"

0.5

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

over

"

voidfactor

=

"

0.5

"

/>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'clearbet' (in case of a clearbet mes-

sage)

time The seconds after the event was Integer

added.

Match clearedscore The score in the match when the String

bet was cleared. Format: '[homescore]:[awayscore]'

Odds id Unique identifier which corre- Integer

sponds to the odds elements in the

previously sent out odds change

messages.

OddsField outcome Whether this outcome has oc- 1 = true

curred. 0 = false

voidfactor Optional attribute. Can be avail- 1 = The whole bet is voided

able for various bet types, like 0.5 = Half of the bet is voided

asian handicap and asian total. If

the voidfactor is 0.5, the value of

outcome will indicate whether the

other half of the bet is won or lost.

3.1.12 Rollback

If our system should send out wrong information about bet clearing, a rollback message will be sent when the situation is discovered.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

rollback

"

time

=

"

17

"

timestamp

=

"

1199436168440

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

2:0

"

matchid

=

"

661373

"

matchtime

=

"

9

"

msgnr

=

"

45

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

1379

"

specialoddsvalue

=

"

1:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

1

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

x

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

2

"

/>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'rollback' (in case of a rollback mes-

sage)

time The amount of seconds which have Integer

passed since the betclearing. The

time for the original bet clearing is

timestamp - time (in seconds).

Match clearedscore The cleared score of the original String

bet clearing. Format: '[homescore]:[awayscore]'

Odds id Unique identifier which corre- Integer

sponds to the odds elements in the

previously sent out odds change

and betclear messages. This id

explains what bet the rollback is

for.

Note

The Odds element includes OddsField elements to indicate which fields were cleared in the original bet clearing. The Client system is

responsible for handling this accordingly.

3.1.13 Bet cancellation

If a bettype for a match should be canceled for any reason, a cancelbet message is sent out.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

cancelbet

"

timestamp

=

"

1199436169018

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

matchtime

=

"

9

"

msgnr

=

"

46

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13792

"

specialoddsvalue

=

"

2:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

endtime

=

"

1199436022222

"

starttime

=

"

1199435902000

"

status

=

"

cancelbet

"

timestamp

=

"

1199436037753

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

matchtime

=

"

7

"

msgnr

=

"

33

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13790

"

specialoddsvalue

=

"

1:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'cancelbet' (in case of a cancelbet

message)

starttime Optional attribute. If starttime and Timestamp in UTC

endtime are set, only bets accepted

in this interval should be canceled.

endtime Optional attribute. If starttime and Timestamp in UTC

endtime are set, only bets accepted

in this interval should be canceled.

Odds id Unique identifier which corre- Integer

sponds to the odds elements in the

previously sent out odds change

messages. All bets accepted for

these odds should be canceled

and cashed out with an odd of 1,0

(stakes returned).

3.1.14 Undo bet cancellation

When, for some reason, a bet type is canceled but it should not have been canceled, this can be undone. The status attribute will be

changed to show the following:

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

undocancelbet

"

timestamp

=

"

1199783156940

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

49

"

status

=

"

not_started

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13792

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

endtime

=

"

1414485300000

"

starttime

=

"

1414484460000

"

status

=

"

undocancelbet

"

timestamp

=

"

1414485318193

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

earlybetstatus

=

"

stopped

"

matchid

=

"

2097712

"

msgnr

=

"

24872

"

status

=

"

not_started

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Correct score flex

"

id

=

"

1887907

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

104

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'undocancelbet' (in case of an undo-

cancelbet message)

starttime Optional attribute. If starttime and Timestamp in UTC

endtime are set, only the cancella-

tion for this bet type with the same

time interval should be undone.

endtime Optional attribute. If starttime and Timestamp in UTC

endtime are set, only the cancella-

tion for this bet type with the same

time interval should be undone.

Odds id Unique identifier which corre- Integer

sponds to the odds elements

in the previously sent out odds

change messages and cancelbet

messages.

Note

Cancelbet messages either cover the whole bet type (from beginning to end) or a specific interval. When a cancelbet message has to

be undone, it’s only possible to undo the cancellation of either the whole bet type, or (one of) the intervals specified.

3.1.15 Match meta information

Match meta information messages contain the general information about a match. This message gets sent out by us on the following

occasions:

When a match becomes available;

When a match becomes unavailable;

When parameters change (e.g. start time of the match).

Additionally, match meta information messages can be requested by the client system by sending a meta request.

To make sure that the client system has the most recent match meta information, it is recommended to send meta requests

periodically, and update possible changes in the client system. More information about meta requests and a best practice can be

found in chapter 3.2.4.

Standard meta information message

The standard meta information message contains the date and time of the match, sport, category, tournament, teams and what TV-

channels this match is broadcasted.

XML example

<

BetbalancerLiveOdds

timestamp

=

"

1184145290125

"

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

>

<

Match

active

=

"

1

"

matchid

=

"

505484

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1184175000000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

17

"

>

Austria

</

Category

>

<

Tournament

id

=

"

29

"

>

Tô€€€Mobile Bundesliga

</

Tournament

>

<

HomeTeam

id

=

"

6589

"

uniqueid

=

"

2051

"

>

SK PUNTIGAMER STURM GRAZ

</

HomeTeam

>

<

AwayTeam

id

=

"

6597

"

uniqueid

=

"

2203

"

>

FK AUSTRIA MAGNA

</

AwayTeam

>

<

TvChannels

>

<

TvChannel

>

PREMIERE Austria

</

TvChannel

>

<

TvChannel

>

PREMIERE SPORT PORTAL

</

TvChannel

>

</

TvChannels

>

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status What kind of information is con- String

LiveOdds tained in the message. 'meta' (in case of a meta message)

Match active Whether the match is still active or Integer

not. Set to 0 if the match is either 0 = not active

removed, or if the client has unreg- 1 = active

istered for the match. In both cases

a Message element can be added

to the match.

matchid The id of the match for which the Long

matchinfo is sent.

status The context status of the match, i.e. String

'not_started' Examples:

not_started

in_progress

started

1set

...

MatchInfo - The element containing all the

match information

DateOfMatch- The element contains the start time Unix timestamp

of the match

Sport - The element contains a textual rep- String

resentation of the sport

id The id of the sport Integer

Category - The element contains the name of String

the category

id The id of the category Integer

Tournament - The element contains the name of String

the tournament

id The id of the tournament Integer

HomeTeam - The element contains the name of String

the home team

id The id of the home team in this Integer

tournament

uniqueid The id of the home team in all tour- Integer

naments. Optional attribute, should

only be used to identify that two

teams in different tournaments are

the same.

AwayTeam - The element contains the name of String

the away team

id The id of the away team in this tour- Integer

nament

uniqueid The id of the away team in all tour- Integer

naments. Optional attribute, should

only be used to identify that two

teams in different tournaments are

the same.

TvChannels - The element containing all the tv

channels

TvChannel - The element contains the name of String

the tv channel

Note

It is possible to include your own match id’s in the meta message. To do this you need to contact our support team, so they can set

this up. When this is done, an extra attribute named sourceid will be included in the Match element for meta messages. The value of

the attribute will be empty if we are missing your id for a particular match.

Meta information message with information about streaming

In order to get streaming information in the meta information messages the correct XML configuration needs to be enabled, see

chapter 5.1.1.6.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

Streaming

>

<

Channel

id

=

"

1

"

>

Live Channel Retail LIVE Match

</

Channel

>

<

Channel

id

=

"

2

"

>

Live Channel Retail LIVE Visualisation

</

Channel

>

<

Channel

id

=

"

3

"

>

Live Channel Online LIVE Match

</

Channel

>

<

Channel

id

=

"

4

"

>

Live Channel Online LIVE Visualisation

</

Channel

>

</

Streaming

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Streaming - The element containing all the

streaming information

Channel - The element contains the name of String

the streaming channel

id The id of the streaming channel Long

Meta information message with information about coverage

In order to get coverage information in the meta information messages the correct XML configuration needs to be enabled, see

chapter 5.1.1.7.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

CoverageInfo

>

<

Type

id

=

"

1

"

>

Extended markets

</

Type

>

</

CoverageInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

CoverageInfo - The element containing all the cov-

erage information

Type - The element contains the name of String

the coverage info type

id The id of the coverage info type Integer

Meta information message with information about the sport

In order to get extra sport information in the meta information messages the correct XML configuration needs to be enabled, see

chapter 5.1.1.5.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

PeriodLength

"

>

45

</

Info

>

<

Info

type

=

"

OvertimeLength

"

>

15

</

Info

>

</

ExtraInfo

>

<

Streaming

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

ExtraInfo - The element containing all the extra

information for the sport

Info - The element contains the value of String

the extra information type

type The id of the coverage info type String

Meta information message with competitors pr team

For Tennis doubles matches, the meta information can hold info regarding the individual players within a team. Please note that tennis

players are sent as team IDs. To activate, see XML configuration 6.22.2.5.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1489592713569

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

11257013

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1489592925481

</

DateOfMatch

>

<

Sport

id

=

"

5

"

>

Tennis

</

Sport

>

<

Category

id

=

"

6

"

>

WTA

</

Category

>

<

Tournament

id

=

"

57144

"

>

Indian Wells, USA, Doubles

</

Tournament

>

<

HomeTeam

id

=

"

7057978

"

uniqueid

=

"

138370

"

>

HRADECKA L / SINIAKOVA K

</

HomeTeam

>

<

AwayTeam

id

=

"

9547077

"

uniqueid

=

"

320177

"

>

ARRUABARRENA L / LIANG C

</

AwayTeam

>

<

HomeCompetitors

>

<

Team

id

=

"

541426

"

uniqueid

=

"

19331

"

>

HRADECKA, LUCIE

</

Team

>

<

Team

id

=

"

6226593

"

uniqueid

=

"

72376

"

>

SINIAKOVA, KATERINA

</

Team

>

</

HomeCompetitors

>

<

AwayCompetitors

>

<

Team

id

=

"

5395461

"

uniqueid

=

"

46448

"

>

ARRUABARRENA-VECINO, LARA

</

Team

>

<

Team

id

=

"

1122536

"

uniqueid

=

"

49884

"

>

LIANG, CHEN

</

Team

>

</

AwayCompetitors

>

<

TvChannels

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Home- - The element containing individual -

Competitors competitors (teams) for home team

Away- - The element containing individual -

Competitors competitors (teams) for away team

Team - The element contains the name of String

the team

id The id of the team in this tourna- Integer

ment

uniqueid The id of the team in all tourna- Integer

ments. Optional attribute, should

only be used to identify that two

teams in different tournaments are

the same.

3.1.16 Deactivation from us

Our system can, for various reasons, deactivate odds. It is possible that all odds for a match get deactivated, one entire bet type, or

just one OddsField.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

41

"

matchtime_extended

=

"

40:48

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

ftr

=

"

-1.0

"

id

=

"

52891500

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1.0

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

typeid

=

"

17

"

>

2.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

18

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

ftr

=

"

-1.25

"

id

=

"

52891512

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1.25

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

52891518

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

1.0

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

0

"

type

=

"

under

"

typeid

=

"

116

"

/>

<

OddsField

active

=

"

1

"

type

=

"

over

"

typeid

=

"

117

"

>

11.75

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match, active Whether this node is active. For ex- Integer

Odds, Odds- ample: A bet type can be active, but 1 = active

Field only 2 out of 3 OddsFields are ac- 0 = deactivated

tive. This gives the opportunity to

deactivate all odds for a match, an

entire bet type, or just one Odds-

Field for a bet type.

3.1.17 Text messages from us

Our system is able to send text messages to the operator at the Client system. The message can contain information about the match,

or extra information in relation to any betstop situation.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199783362456

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

2

"

score

=

"

-:-

"

status

=

"

not_started

"

>

<

Message

>

Game cancelled: No TV coverage

</

Message

>

</

Match

>

</

BetbalancerLiveOdds

>

3.1.18 Scout matches

In some cases the feed will include elements and attributes that are an indication that the match is offered in Live Data as well.

3.1.18.1 Match meta messages

A tv channel named 'Scout' is added to meta message for scout matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1394788377983

"

>

<

Match

active

=

"

1

"

booked

=

"

0

"

matchid

=

"

1271072

"

sourceid

=

"

status

=

"

1q

"

>

<

MatchInfo

>

<

DateOfMatch

>

1394787895000

</

DateOfMatch

>

<

Sport

id

=

"

20

"

>

Table tennis

</

Sport

>

<

Category

id

=

"

3

"

>

ATP

</

Category

>

<

Tournament

id

=

"

18953

"

>

Miami, USA

</

Tournament

>

<

HomeTeam

id

=

"

4783

"

uniqueid

=

"

1764

"

>

AIK

</

HomeTeam

>

<

AwayTeam

id

=

"

5259

"

uniqueid

=

"

1786

"

>

GAIS G

Ö

TEBORG

</

AwayTeam

>

<

TvChannels

>

<

TvChannel

>

Scout

</

TvChannel

>

</

TvChannels

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

TvChannel - The element contains the name of String

the source/tvchannel. 'Scout' if the match is a scoutmatch

3.1.18.2 Extra attribute in the root element

An attribute type with value 'scoutmatch' is added to the BetbalancerLiveOdds element.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1395839620340

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10755

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer type Optional attribute explaining what String

LiveOdds type of match it is. 'scoutmatch' if the match is also a

scoutmatch

3.1.19 Extra players during a match for certain markets

For some markets and in some sports, our system sends out information about players as individual OddsFields. However, in some

cases i.e. Where FIFA and UEFA allow 23 players per team for the world and euro cup (where domestic leagues usually only allow 18

players total), some unknown home/away players may show up having a player ID equal to -1. This is because (in the case of the

following example) some markets have more defined outcomes than allowed players.

XML example

<

BetbalancerLiveOdds

timestamp

=

"

1525711813939

"

status

=

"

change

"

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

>

<

Match

matchid

=

"

12055804

"

status

=

"

1p

"

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchtime

=

"

20

"

score

=

"

1:0

"

setscores

=

"

1:0

"

msgnr

=

"

199

"

cornershome

=

"

2

"

cornersaway

=

"

0

"

yellowcardshome

=

"

0

"

yellowcardsaway

=

"

1

"

redcardshome

=

"

0

"

redcardsaway

=

"

0

"

yellowredcardshome

=

"

0

"

yellowredcardsaway

=

"

0

"

>

<

Odds

id

=

"

360181594

"

type

=

"

ftnw

"

subtype

=

"

146

"

specialoddsvalue

=

"

-1

"

freetext

=

"

Anytime Goal

scorer

"

combination

=

"

0

"

active

=

"

1

"

changed

=

"

true

"

typeid

=

"

8

"

>

<

OddsField

type

=

"

Blanco, Ruben

"

active

=

"

0

"

typeid

=

"

450

"

playerid

=

"

180515

"

/>

<

OddsField

type

=

"

Drazic, Dejan

"

active

=

"

0

"

typeid

=

"

2438

"

playerid

=

"

363778

"

/>

<

OddsField

type

=

"

Boye, Lucas

"

active

=

"

0

"

typeid

=

"

2440

"

playerid

=

"

584066

"

/>

<

OddsField

type

=

"

player home 19

"

active

=

"

0

"

typeid

=

"

2442

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player home 20

"

active

=

"

0

"

typeid

=

"

2444

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player home 21

"

active

=

"

0

"

typeid

=

"

2446

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player home 22

"

active

=

"

0

"

typeid

=

"

2448

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player home 23

"

active

=

"

0

"

typeid

=

"

2450

"

playerid

=

"

-1

"

/>

}

<

!-

Away

players

showing

up

with

playerid

=

"

-1

"

--

>

<

OddsField

type

=

"

Bakkali, Zakaria

"

active

=

"

0

"

typeid

=

"

2452

"

playerid

=

"

285941

"

/>

<

OddsField

type

=

"

Valverde, Federico

"

active

=

"

0

"

typeid

=

"

2454

"

playerid

=

"

962433

"

/>

<

OddsField

type

=

"

player away 19

"

active

=

"

0

"

typeid

=

"

2456

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player away 20

"

active

=

"

0

"

typeid

=

"

2458

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player away 21

"

active

=

"

0

"

typeid

=

"

2460

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player away 22

"

active

=

"

0

"

typeid

=

"

2462

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

player away 23

"

active

=

"

0

"

typeid

=

"

2464

"

playerid

=

"

-1

"

/>

<

OddsField

type

=

"

Krohn Dehli, Michael

"

active

=

"

1

"

typeid

=

"

451

"

playerid

=

"

2565

"

>

14.87

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

In the above example (snippet taken from a 'Next and Anytime goal scorer' market), the highlighted players (number 19 - 23) can be

skipped as they are undefined. This is a result of the market having 46 defined outcomes, but the match only has 18 players per

team.

3.1.20 Goal and card message status in the feed

The attribute 'status' may sometimes provide information about a score or card changes in the feed. The following list is pro- vided to

clarify which sports generate the score and card messages.

Score message: American football, futsal, handball, ice hockey, rugby, soccer and aussie rules.

Card messages: Rugby, futsal, soccer, badminton, handball and table tennis.

XML example - Goal

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1395839596131

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

earlybetstatus

=

"

stopped

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10752

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

101058

"

player

=

"

scoringteam

=

"

home

"

time

=

"

1

"

type

=

"

live

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

3.2 XML Messages sent from a Client system

Client systems can request various data. This happens by sending an XML message to our System. The core of a request looks like

this:

XML example

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

/>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String, one of the following values:

Status of request is sent. In the upcom- login

ing chapters the keywords and re- current

quests are described in more detail. error

meta

gettranslation

status

change

bookmatch

scoreandcardsummary

register

unregister

bookmakerid The id of the bookmaker which is Integer

requesting the information.

3.2.1 Login

Before data can be received the client system needs to log in.

XML example

<

BookmakerStatus

type

=

"

login

"

bookmakerid

=

"

24

"

key

=

"

1

"

>

</

BookmakerStatus

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'login' (for login requests)

bookmakerid The id of the bookmaker which is Integer

trying to log in.

key The key of the bookmaker which is String

trying to log in.

3.2.2 Current

Client systems can request an overview of the status of matches they are subscribed to. This happens by sending a current request.

In this request the client system specifies what matches they want to get the status for.

XML example

<

BookmakerStatus

timestamp

=

"

0

"

bookmakerid

=

"

24

"

type

=

"

current

"

>

<

Match

matchid

=

"

661373

"

/>

</

BookmakerStatus

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'current' (for current requests)

bookmakerid The id of the bookmaker Integer

timestamp The moment for which you want UTC timestamp or 0

to retrieve the current status of the

requested match(es). Using 0 as

timestamp would normally repre-

sent the 1st of January 1970, but

for the current status request it will

automatically translate into current

time.

Match matchid The id of the match for which the Integer

current status is requested

After a current request is received our system will return the following messages:

A message containing the odds, activation of odds and match status for the match requested.

A message indicating the current bet status. This is a regular bet status message.

All bet clearing messages sent before the timestamp given are sent as they were sent originally.

All messages are separated by a newline. The replytype attribute is set to 'current' for the reply messages from current requests. The

match element will not include the msgnr attribute.

3.2.3 Error recovery

Client systems can recover messages they might have missed during downtime or disconnection by sending an error request.

However, it is strongly recommended that current requests are used instead (see chapter 3.2.2).

Current requests will not provide all the missed messages, but for each match the most recent match status and odds, a betstart or

betstop, clearbets and cancelbets are returned. This way the client system can update the matches to the correct status instantly

rather than updating each match multiple times for events which might already be outdated. Error requests can gen- erate a lot of

XML messages which the client system needs to process, which can lead to disconnection if the message queue exceeds the limits

specified in chapter 2.3.

Error requests can request missed messages as following:

One at a time, by specifying the msgnr from the missed message.

If the attribute msgnr is not added, it’s possible to request a sequence of missed messages by specifying msgfrom and msgto.

If the msgfrom and msgto attributes are not present either, the value of the last successfull received message should be passed

in the attribute timestamp to receive all the messages after that timestamp.

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

error

"

bookmakerid

=

"

24

"

msgnr

=

"

36

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

type

=

"

error

"

bookmakerid

=

"

24

"

msgfrom

=

"

12

"

msgto

=

"

15

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

timestamp

=

"

1420070400

"

type

=

"

error

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'error' (for error requests)

msgnr The id of the message which is re- Integer

quested. Optional attribute, if this is

not passed, the system will look for

the msgfrom and msgto attributes.

msgfrom The id from the first message in the Integer

sequence which is requested. Op-

tional attribute, if this is not passed,

the system will look for the times-

tamp attribute.

msgto The id from the first message in the Integer

sequence which is requested. Op-

tional attribute, if this is not passed,

the system will look for the times-

tamp attribute.

timestamp Optional. The exact same times- Unix timestamp

tamp as given in the last correct Unlike the current match status re-

message. All messages from that quest sending 0 as timestamp will

point on will be resent to the client NOT automatically translate into cur-

system. rent time.

The response to the error request will look as following: First messages sent as type='current' get listed. After that all messages sent

after timestamp for the given matches, are sent again. Alive messages are not included.

All messages are separated by a newline. The replytype attribute is set to 'error' for the reply messages from error requests. The

match element will include the msgnr attribute. If the client has missed one or several messages it can request those specific

messages by specifying the missed msgnr(s).

Note

Only matches finished the last 48 hours are available for error request. For older matches you will only receive clearbet and cancelbet

messages.

3.2.4 Meta information

The Client system can request meta-information about upcoming and current matches. It is possible to receive all matches in a certain

timespan, or to specify the matches for which the meta information is desired. The response message includes teams playing, match

date and time, TV channel names, streaming information and sport/category/tournament for the match.

Best practice

To make sure that the client system has the most recent match meta information, it is recommended to send meta requests

periodically, and update possible changes in the client system. The following guidelines apply:

Send a request once an hour to get matches for the next 24 hours;

Send a request once per day to get matches for the next week;

Send a request after the client system reconnects after a disconnection.

XML examples

<

BookmakerStatus

bookmakerid

=

"

24

"

type

=

"

meta

"

/>

<

BookmakerStatus

bookmakerid

=

"

24

"

type

=

"

meta

"

>

<

Match

matchid

=

"

588101

"

/>

<

Match

matchid

=

"

524577

"

/>

<

Match

matchid

=

"

516557

"

/>

<

Match

matchid

=

"

568263

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

bookmakerid

=

"

24

"

metafrom

=

"

1190370195000

"

metato

=

"

1190391831000

"

includeavailable

=

"

true

"

type

=

"

meta

"

/>

For a full overview of XML examples for meta requests see chapter 7.6.

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'meta' (for meta information requests)

bookmakerid The id of the bookmaker Integer

metafrom Optional. Start of the interval for UTC timestamp

matches of which the meta informa-

tion is desired. Maximum interval is

10 days.

metato Optional. End of the interval for UTC timestamp

matches of which the meta informa-

tion is desired. Maximum interval is

10 days.

includeavailable Optional. Usually the meta mes- String

sage will only include the matches 'true' = Include nonbooked matches

that are booked or included in the

purchased package. By enabling

either this attribute or the corre-

sponding XML configuration (see

chapter 5.1.1.9) the response will

also include matches that are avail-

able for booking but not booked

(yet). Enabling this attribute will

override the XML configuration, for

this request only.

The match element in the meta-

response will then include an extra

attribute booked with the value 1 if

the match is already booked, or 0 if

it is not booked yet.

Match matchid The id of the match for which the Integer

meta is requested. If no Match el-

ements were specified, all matches

which apply to the other attributes

are returned.

The match meta information which is returned after sending a meta request is described in chapter 3.1.15.

Note

If matchids are specified through match elements, only meta-information for these matches is re- turned. By default, if no matchids

are indicated and no metafrom/metato is specified, all matches started 24 hours in the past, and 7 days in the future are returned.

3.2.5 Translations

If you like to get the meta-information translated you can either select the languages you like to include in the Live Odds configuration

section, or you can specify this in the meta request.

Meta request with translations

XML example

<

BookmakerStatus

bookmakerid

=

"

24

"

languages

=

"

en,nl

"

type

=

"

meta

"

/>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'meta' (for meta information requests)

bookmakerid The id of the bookmaker Integer

languages Optional. A comma separated list String

with language codes. The trans-

lated meta-information will be in-

cluded inside an element named

Translation inside the Match ele-

ment. Languages and their lan-

guage codes can be found in the

table below.

Odds type translations

It is also possible to get translation of all the odds types that are used. This will be sent if you send a gettranslation request to the

server.

XML example

<

BookmakerStatus

bookmakerid

=

"

24

"

languages

=

"

en,nl

"

type

=

"

gettranslation

"

/>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'gettranslation' (for odds translation

requests)

bookmakerid The id of the bookmaker Integer

languages Optional. A comma separated list String

with language codes. Languages

and their language codes can be

found in the table below.

Available Languages

Language code Language

bs Bosnian

bg Bulgarian

zh Chinese (semplified)

zht Chinese (traditional)

ht Croatian

cs Czech

da Danish

nl Dutch

en English

et Estonian

fi Finnish

fr French

de German

el Greek

hu Hungarian

it Italian

ja Japanese

lv Latvian

lt Lithuanian

mk Macedonian

no Norwegian

pl Polish

pt Portuguese

ro Romanian

ru Russian

sk Slovakian

sl Slovenian

es Spanish

se Swedish

tr Turkish

sqi Albanian

aa Arabic

aze Azerbaijan

ka Georgian

heb Hebrew

id Indonesian

ko Korean

me Montenegrin

sr Serbian

srl Serbian Latin

th Thai

ukr Ukrainian

vi Vietnamese

3.2.6 Match booking

Booking of matches is usually done in the booking calendar inside in.betbalancer.com, but for convenience it is also possible to send a

match booking request in the XML feed. After this request you will receive a meta-message with the specified matches.

XML example

<

BookmakerStatus

bookmakerid

=

"

24

"

type

=

"

bookmatch

"

>

<

Match

matchid

=

"

1291016

"

/>

<

Match

matchid

=

"

1410019

"

/>

</

BookmakerStatus

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'bookmatch' (for match booking re-

quests)

bookmakerid The id of the bookmaker Integer

Match matchid The id of the match which the client Integer

system wants to book.

Note

Clients will receive a meta information message for matches which are booked through the feed, or matches which are booked in the

booking calendar while the client system is logged in to the feed. The only case where a client system will not receive a meta

information message is if the match is booked in the booking calendar at a moment where the client system is not logged in to the

feed.

3.2.7 Request score and card summary

To receive a list of all cards and scores for a match you can send a score and card summary request to the server.

XML example

<

BookmakerStatus

bookmakerid

=

"

1240

"

type

=

"

scoreandcardsummary

"

>

<

Match

matchid

=

"

1355389

"

/>

</

BookmakerStatus

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'scoreandcardsummary' (for score

and card summary requests)

bookmakerid The id of the bookmaker Integer

Match matchid The id of the match of which the Integer

client system wants to receive the

score and card summary.

The response to this request will have the replytype attribute set to scoreandcardsummary. An example of how the request and

response should look like is included in chapter 7.22.

3.2.8 Match registration

The client system will automatically receive odds for all matches that it is registered to. There is no need to register for a match

unless you have unsubscribed before.

XML examples

<

BookmakerStatus

bookmakerid

=

"

24

"

type

=

"

unregister

"

>

<

Match

matchid

=

"

661373

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

bookmakerid

=

"

24

"

type

=

"

register

"

>

<

Match

matchid

=

"

661373

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

bookmakerid

=

"

24

"

type

=

"

unregister

"

>

<

Match

matchid

=

"

661373

"

>

<

Odds

typeid

=

"

5

"

/>

<

Odds

subtype

=

"

13

"

typeid

=

"

6

"

/>

</

Match

>

</

BookmakerStatus

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- type Keyword which describes what kind String

Status of request is sent. 'register' (for match registration re-

quests)

'unregister' (for match unregistration

requests)

bookmakerid The id of the bookmaker Integer

Match matchid The id of the match of which the Integer

client system wants to register or

unregister from.

Odds subtype Identifier which tells what kind of Number

freetext market this is.

typeid This is a numeric id for the market Number

type, and will be the same for that

market type in all matches.

If the configuration option 'Enable response on register and unregister requests' (see chapter 5.1.1.3) has been activated, you will

receive a meta message for the given match. The meta message will have a replytype attribute set to 'register' or 'unregister'.

Examples of meta response messages are listed chapter 7.7.

Note

It is possible to register/unregister from specific bet types for a match by passing Odds elements. If not Odds elements are passed,

the client system will be registered/unregistered from all bet types for the specified match.

3.2.9 Wrong XML from Client system

If the client system sends a not well-formed or not valid message to our system, an error message will be returned from our system.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

error

"

timestamp

=

"

1199783362456

"

>

<

Message

>

The given xml is not well-formed:

</

Message

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status Keyword which describes what kind String

LiveOdds of message it is. 'error' (for error messages)

Message - Either 'The given xml is not well- String

formed:', or 'The given xml is not

valid:', plus the XML message that

caused the error.

4. General Configuration

4 General configuration

When new features are released they will not automatically be included in the feed. In addition to the XML config page, there is a

general configuration page. This page can be found on our BO.

4.1 Include Live Odds probabilities

Whether to add probabilities to the Live Odds xml feed or not. If this setting is not enabled, only odds values are included in the Live

Odds xml feed. If this setting is enabled, probabilities based on an odds key of 100 % (no margin) are added to the Live Odds xml

feed, in addition to the regular odds values.

XML example - setting disabled

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

10028941

"

matchtime

=

"

43

"

msgnr

=

"

53

"

score

=

"

0:1

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Exact number of goals

"

...

>

<

OddsField

active

=

"

0

"

type

=

"

0

"

typeid

=

"

418

"

/>

<

OddsField

active

=

"

0

"

type

=

"

1

"

typeid

=

"

419

"

/>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

420

"

>

4.43

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3

"

typeid

=

"

421

"

>

71.34

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4+

"

typeid

=

"

422

"

>

100.0

</

OddsField

>

</

Odds

>

</

Match

>

XML example - setting enabled

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

10028941

"

matchtime

=

"

43

"

msgnr

=

"

53

"

score

=

"

0:1

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Exact number of goals

"

...

>

<

OddsField

active

=

"

0

"

type

=

"

0

"

typeid

=

"

418

"

/>

<

OddsField

active

=

"

0

"

type

=

"

1

"

typeid

=

"

419

"

probability

=

"

0.898

"

/>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

420

"

probability

=

"

0.0966

"

>

4.43

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3

"

typeid

=

"

421

"

probability

=

"

0.0052

"

>

71.34

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4+

"

typeid

=

"

422

"

probability

=

"

2.0E-4

"

>

100.0

</

OddsField

>

</

Odds

>

</

Match

>

If the value of the probability attribute is very low, the scientific notation (for example 2.0E-4) can be used to display the number,

rather than a normal double. The probability attribute can be added to the OddsField even if the outcome is inactive (active = 0).

Note

If no probabilities are available for the current OddsField, the probability attribute will not be set, even if the option is enabled.

4.1.1 Live Odds probability precision

Number of decimals (1 - 10) for the value of the probability attribute in the Live Odds xml feed. This setting is only used if the Live

Odds probabilities setting is enabled.

5. XML Configuration

5 XML configuration

When new features are released they will not automatically be included in the feed. Clients need to enable the features on the XML

configuration page before they will start receiving them.

This also applies to activation and deactivation of markets/tournament/category/sport.

The specific code which is generating canceled goals is behaving exactly the same way as for adding a score, with the exception that

for canceled goals we set a canceled flag to "true". The difference is that with the card element we will always set the canceled flag to

either "true" or "false", but for cards it is only set if the goal is canceled.

Additionally, the new features are added to the test server a few weeks before the actual release, so they can be tested. We currently

allow the following features to be enabled/disabled:

5.1 All sports

The following chapter covers the XML configuration options which apply to all sports. For more detailed information about the XML

configurations per sport, see chapter 6.

5.1.1 General XML configuration options

5.1.1.1(ID: 4) Include response reply number for error, current and scoreandcardsummary messages

This setting will help client systems getting a clear overview of the response messages which are recieved after error, current and

scoreandcardsummary requests. It will become visible when the response starts and ends, and it will be easy to group the responses

together. Enabling this setting will add a new attribute replynr and use two new values in the status attribute.

XML example

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

error

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

935448

"

active

=

"

1

"

/>

</

BookmakerStatus

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

error

"

status

=

"

replystart

"

timestamp

=

"

1260866252519

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

current

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1260866108600

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

12

"

score

=

"

0:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

current

"

status

=

"

clearbet

"

time

=

"

517

"

timestamp

=

"

1260866108600

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

0:0

"

matchid

=

"

935448

"

matchtime

=

"

1

"

status

=

"

1p

"

>

</

Match

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

error

"

status

=

"

replyend

"

timestamp

=

"

1260866252767

"

/>

A full XML example can be found in chapter 7.2.2

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status The error/current/scoreandcard- String

LiveOdds summary response messages are replystart

surrounded by two messages with replyend

status replystart and replyend.

replynr The id of the response to the er- Integer

ror/current/scoreandcardsummary If the attribute requestnr was set

request. All messages which are in the error/current/scoreandcardsum-

a response to the error/current/s- mary request, the replynr in the re-

coreandcardsummary request do sponse message will take this value.

have the same replynr.

5.1.1.2(ID: 84) Include response reply number in meta messages

If this setting is enabled, an attribute replynr will be added to the BetbalancerLiveOdds element in match meta messages.

XML example

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

2

"

status

=

"

meta

"

timestamp

=

"

1400146666680

"

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer replynr The id of the response to the meta Integer

LiveOdds request. All messages which are If the attribute requestnr was set in the

a response to the meta request do meta request, the replynr in the re-

have the same replynr. sponse message will take this value.

Reply number specified by client

The client system can specify the reply through the request, in case you want to keep your own counter for the reply number.

XML example

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

requestnr

=

"

1234

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

1234

"

status

=

"

meta

"

timestamp

=

"

14006666680

"

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Bookmaker- requestnr The id of the meta request as spec- Integer

Status ified by the client. If this attribute is If the attribute requestnr was set in the

added to the request, the response request, the replynr in the response

will contain the replynr attribute re- will take this value.

gardless of the value of this setting.

5.1.1.3(ID: 8) Enable response on register and unregister requests

It is possible to register or unregister for a match, odds, or oddsfields through the feed. Normally our system does not send a response

to this. If this setting is enabled the client system will receive a match meta information message. The active fields will indicate the

status of the (un)registration.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

register

"

status

=

"

meta

"

timestamp

=

"

1275050982039

"

>

<

Match

active

=

"

1

"

matchid

=

"

935448

"

status

=

"

1p

"

>

<

MatchInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes

Element Attributes

Attribute Description Possible values

Betbalancer replytype The source of the message, the String

LiveOdds type of request or setting the mes- register

sage is a reply to. unregister

Match active The registration status. This at- Integer

tribute can also occur in the ele- 1 = registered

ments Odds or OddsField. 0 = unregistered / match unavailable

5.1.1.4(ID: 88) Include autotraded attribute in meta messages

If this setting is enabled, an attribute autotraded will be added to the Match element in match meta messages. The attribute will only

be added if the match is an Auto-traded Live Odds match.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

status

=

"

not_started

"

matchid

=

"

956

"

booked

=

"

1

"

autotraded

=

"

1

"

active

=

"

1

"

>

<

MatchInfo

>

<

DateOfMatch

>

1415016577000

</

DateOfMatch

>

<

Sport

id

=

"

5

"

>

Tennis

</

Sport

>

<

Category

id

=

"

3

"

>

ATP

</

Category

>

<

Tournament

id

=

"

568

"

>

Paris TMS, France

</

Tournament

>

<

HomeTeam

uniqueid

=

"

14321

"

id

=

"

11403

"

>

AGASSI, ANDRE

</

HomeTeam

>

<

AwayTeam

uniqueid

=

"

14329

"

id

=

"

11749

"

>

GAUDIO, GASTON

</

AwayTeam

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match autotraded Whether the match is Auto-traded Integer

or not 1 = Auto-traded

5.1.1.5(ID: 24) Include extra sport info in meta messages

If this setting is enabled, sport specific information (like period length, number of sets) for the match will be added to the match meta

messages.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

PeriodLength

"

>

45

</

Info

>

<

Info

type

=

"

OvertimeLength

"

>

15

</

Info

>

</

ExtraInfo

>

<

Streaming

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

The value of the attribute type for each Info element is depending on the sport of the match. See the overview of all the sports and

their info types below:

Sport Possible values type attribute

Soccer PeriodLength, OvertimeLength

Tennis NumberOfSets, AdvantageRule, MatchTieBreakSet

Basketball PeriodLength, OvertimeLength

Ice Hockey PeriodLength, OvertimeLength

Handball PeriodLength, OvertimeLength

Volleyball NumberOfSets, SetLimit, Format

Beach Volleyball NumberOfSets, SetLimit, Format

Badminton NumberOfSets, SetLimit, Format

Table Tennis NumberOfSets

American Football PeriodLength, OvertimeLength

Snooker BestOfFrames

Darts DrawPossible, BestOfXSets, BestOfXLegs

Futsal PeriodLength, OvertimeLength

Bowls BestOfSets, EndsPerSet, SetPlaythrough, EndsInTiebreak, TiebreakScoringIsEnds

Squash NumberOfGames, GameLimit, Format

Dota2 Best of maps

CS:GO Best of maps, Rounds per map, Best of rounds in OT

League of legends Best of maps

5.1.1.6(ID: 82) Include streaming info in meta messages

If this setting is enabled, streaming information for the match will be added to the match meta messages.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

Streaming

>

<

Channel

id

=

"

1

"

>

Live Channel Retail LIVE Match

</

Channel

>

<

Channel

id

=

"

2

"

>

Live Channel Retail LIVE Visualisation

</

Channel

>

<

Channel

id

=

"

3

"

>

Live Channel Online LIVE Match

</

Channel

>

<

Channel

id

=

"

4

"

>

Live Channel Online LIVE Visualisation

</

Channel

>

</

Streaming

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

The following streaming channels are available:

Channel Id Channel description

1 Live Channel Retail LIVE Match

2 Live Channel Retail LIVE Visualisation

3 Live Channel Online LIVE Match

4 Live Channel Online LIVE Visualisation

5.1.1.7(ID: 90) Include coverage info in meta messages

If this setting is enabled, coverage information for the match will be added to the match meta messages. The type of markets that are

available will depend on what type of coverage (deeper or basic) is available for the match. If the type element displays "Extended

markets" it indicates that deeper coverage is available.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

CoverageInfo

>

<

Type

id

=

"

1

"

>

Extended markets

</

Type

>

</

CoverageInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

The following coverage information types are available:

Type Id Coverage description

1 Extended markets

5.1.1.8(ID: 126) Include covered from in meta messages

Enabling this setting will add the element <CoverageInfo> to <MatchInfo>, and add <CoveredFrom> as a child. The possible values

for the <CoveredFrom>-element are either venue or tv.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

matchid

=

"

4972075

"

...

>

<

MatchInfo

>

...

<

CoverageInfo

>

...

<

CoveredFrom

>

venue

</

CoveredFrom

>

</

CoverageInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

Note

If the XML configuration in chapter 5.1.1.7 is enabled, the <CoverageInfo>-element is already added and will be reused, meaning that

the <CoveredFrom>-element will become an additional child to the already existing <CoverageInfo>-element. However, if the XML

configuration in chapter 5.1.1.7 is not enabled, enabling the current setting will add the <CoverageInfo>-element.

5.1.1.9(ID: 12) Include non-booked matches in meta messages

When a client system sends out a meta request the response messages usually includes all the booked matches. Clients who want to

include matches that are available for booking, but not booked, should enable this setting. If this setting is enabled the attribute

booked is added to the Match elements to indicate whether the match is booked or not.

XML example

<

BetbalancerLiveOdds

status

=

"

meta

"

timestamp

=

"

1184145290125

"

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

>

<

Match

active

=

"

1

"

booked

=

"

0

"

matchid

=

"

500581

"

status

=

"

not_started

"

>

<

MatchInfo

>

</

MatchInfo

>

</

Match

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

505484

"

status

=

"

not_started

"

>

<

MatchInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

A full XML example can be found in chapter 7.7.2.

XML attributes definition

Element Attributes

Attribute Description Possible values

Match booked Whether the match is booked or Integer

not. 1 = booked

0 = not booked

Note

The behaviour for this setting is the same as when the client sets includeavailable="true" in the meta request. However, if a meta

request contains this attribute it will override the value of this setting.

5.1.1.10(ID: 13) Include clock stopped information for sports that supports this

The following sports support that the clock stops during a match: basketball, ice hockey, handball, futsal. Enabling this setting will add

an attribute clock_stopped to the Match element for all those sports.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clock_stopped

=

"

1

"

matchid

=

"

6414605

"

matchtime

=

"

8

"

msgnr

=

"

37

"

score

=

"

0:0

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match clock_stopped Whether the clock is running or the Integer

clock is stopped. 1 = Clock is stopped

0 = Clock is running

5.1.1.11(ID: 14) Send irrelevant change message for changes that aren’t of interest

Sometimes changes happen which are not interesting for the client system. This could for example be bet clearing of a bet type which

the client unsubscribed from. In this situation our system sends out an odds change message, which can be quite comprehensive. If

the change which happened is not interesting for the client system it’s needless to parse the change message.

This setting allows the client system to ignore change messages which are not interesting for them. If this setting is enabled, instead

of the not interesting change message a message with status="irrelevantchange" is sent.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

irrelevantchange

"

timestamp

=

"

1287060653120

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1467300

"

msgnr

=

"

37

"

status

=

"

pause1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status The type of the message. String

LiveOdds "irrelevantchange" (for irrele-

vantchange messages)

Match msgnr The number of the message. Im- Integer

portant here is that, even though

the original change message was

not sent, the message number of

the irrelevant change message did

still increasy by 1. This ensures that

the sequence of message numbers

will remain sustained.

5.1.1.12(ID: 21) Don’t send updates for inactive bettypes except the deactivation

Change messages containing all the bet types, both active and inactive ones. Depending on what sport or match, the number of

inactive markets can increase rapidly. Enabling this setting will make sure that only active oddstypes or oddstypes which just changed

are in the change messages. Updates for inactive bet types are no longer sent out, only when they get deactivated in order to keep

the messages compact.

This setting only applies to bet types that are inactive, for example because it is no longer offered for this match. It does NOT apply to

bet types that are unregistered by the client (markets deactivated by clients). However, the odds element will still be included for

clients, but with the active attribute set to active="0", and no odds fields.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1526252416174

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

13497237

"

matchtime

=

"

43

"

msgnr

=

"

485

"

score

=

"

0:2

"

status

=

"

1p

"

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Anytime Goal scorer

"

id

=

"

963225658

"

specialoddsvalue

=

"

-1

"

subtype

=

"

146

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next Goal scorer

"

id

=

"

963246016

"

specialoddsvalue

=

"

0:2

"

subtype

=

"

147

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

5.1.1.13(ID: 22) Send bet clearings even if match is not active

If this setting is enabled, bet clearings and bet cancellations will get sent even if the match has been deactivated. Please note that

after enabling this option there might be gaps in the value of msgnr for inactive matches, as only bet clearings and bet cancellation

matches get sent out.

5.1.1.14(ID: 16) Use additional match statuses for overtime

Additional match statuses during overtime and penalty shoot-outs are available for the following sports:

American Football

Aussie Rules

Futsal

Handball

Rugby

Soccer

If this setting is enabled and the match has overtime (and possibly a penalty shoot-out) the match will get the following statuses in

the same order as specified below:

Id Status Status description Additional information

7/16 2p/4q Last normal period/quarter of the This is a regular match status which already exists. Af-

match ter this match status the overtime related match statuses

begin.

32 awaiting_ot Waiting for overtime to start Match gets this status if the match has overtime.

41 1p_ot 1st overtime period Match gets this status if the match has overtime.

33 ot_ht Pause between 1st and 2nd overtime Match gets this status if the match has overtime.

period

42 2p_ot 2nd overtime period Match gets this status if the match has overtime.

110 after_ot Match finished after overtime Match gets this status if the match has overtime.

34 awaiting_pen Wating for penalty shoot-out to start Match only gets this status if the match has a penalty

shoot-out.

50 pen penalty shoot-out Match only gets this status if the match has a penalty

shoot-out.

100 ended The match has ended This is a regular match status which already exists.

5.1.1.15(ID: 23) Use additional match statuses for walkover / retired

There are two regular match statuses, "retired" and "walkover". Enabling this setting will replace those match statuses by new ones,

specifying which player won by walkover or which player retired. The new matchstatuses are:

Id Status Status description Additional information

93 walkover1 The home team won the match by If this setting is enabled, this match status will replace the

walkover regular "walkover" match status

94 walkover2 The away team won the match by If this setting is enabled, this match status will replace the

walkover regular "walkover" match status

95 retired1 The away team won because the If this setting is enabled, this match status will replace the

home team retired regular "retired" match status.

96 retired2 The home team won because the If this setting is enabled, this match status will replace the

away team retired regular "retired" match status.

5.1.1.16(ID: 48) Use match status abandoned

By enabling this setting, the client system receives match status Abandoned if the match gets set to abandoned. If this setting is not

enabled, match status Interrupted will be used instead.

Id Status Status description Additional information

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned If this setting is enabled, this match status will replace the

"interrupted" match status on abandoned matches

5.1.1.17(ID: 11) Send manual odds changes immediately

Manual odds changes made in the configuration interface are called risk adjustments. Usually those risk adjustments will be included

in the next normal odds change message. Enabling this setting will send out a new change message immediately after the risk

adjustment was made. The message will look like a normal change message, but will additionally have the attribute replytype set to

"riskadjustment_update".

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

riskadjustment_update

"

status

=

"

change

"

timestamp

=

"

1297685983108

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

935448

"

score

=

"

-:-

"

status

=

"

not_started

"

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Betbalancer status The type of the message. String

LiveOdds "change" (for odds change messages)

replytype The source of the message, the String

type of request or setting the mes- "riskadjustment_update" (for risk ad-

sage is a reply to. justment updates)

5.1.1.18(ID: 18) Show current period score during period

The attribute setscores contains the scores of all the periods which have ended. For the following sports the current period is not

included:

American Football

Aussie Rules

Baseball

Basketball

Cricket

Futsal

Handball

Ice Hockey

Rugby

Soccer

Enabling this setting will include the score of the current period for the sports mentioned above in the setscores attribute. Other

sports, which are not mentioned in the list above, do always have the current period included in the setscores attribute.

In the following XML examples you will see a soccer match which is in the second period, and what difference this XML setting makes:

XML example - setting disabled

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1297687408708

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

935448

"

score

=

"

1:1

"

setscores

=

"

0:1

"

status

=

"

2p

"

matchtime

=

"

65

"

msgnr

=

"

26

"

/>

</

BetbalancerLiveOdds

>

XML example - setting enabled

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1297687408708

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

935448

"

score

=

"

1:1

"

setscores

=

"

0:1 - 1:0

"

status

=

"

2p

"

matchtime

=

"

65

"

msgnr

=

"

26

"

/>

</

BetbalancerLiveOdds

>

5.1.1.19(ID: 30) Split set scores

All the setscores are gathered in one attribute in the match element, setscores="X1:Y1 - X2:Y2 -...". Enabling this setting will split the

setscores in different attributes, setscore1="X1:Y1", setscore2="X2:Y2", etc.

XML example - setting disabled

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

alive

"

timestamp

=

"

1308561825332

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

gamescore

=

"

0:0

"

matchid

=

"

935457

"

msgnr

=

"

58

"

setscores

=

"

6:3 - 1:3

"

score

=

"

1:0

"

server

=

"

1

"

status

=

"

2set

"

tiebreak

=

"

false

"

/>

</

BetbalancerLiveOdds

>

XML example - setting enabled

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

alive

"

timestamp

=

"

1308561825332

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

gamescore

=

"

0:0

"

matchid

=

"

935457

"

msgnr

=

"

58

"

score

=

"

1:0

"

server

=

"

1

"

setscore1

=

"

6:3

"

setscore2

=

"

1:3

"

status

=

"

2set

"

tiebreak

=

"

false

"

/>

</

BetbalancerLiveOdds

>

5.1.1.20(ID: 44) Include suspension counters in feed

Our system counts the suspensions of both the home and away team for the following sports:

Handball

Futsal

Ice hockey

Those counters are not included in the feed by default. Enabling this setting will add two attributes to the Match element.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

6414605

"

matchtime

=

"

8

"

msgnr

=

"

37

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

suspendAway

=

"

0

"

suspendHome

=

"

0

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match suspendHome The amount of suspensions for the Number >= 0

home team.

suspendAway The amount of suspensions for the Number >= 0

away team.

5.1.1.21(ID: 29) Mark most balanced odds

If this setting is enabled, our system will mark the most balanced odds by adding an attribute mostbalanced to the Odds elements.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5984472

"

matchtime

=

"

38

"

msgnr

=

"

155

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners

"

id

=

"

57178832

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

7.5

"

subtype

=

"

126

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

typeid

=

"

373

"

>

2.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

typeid

=

"

374

"

>

1.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

ftr

=

"

-0.25

"

id

=

"

57178580

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1.25

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

typeid

=

"

17

"

>

2.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

18

"

>

1.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Corner Handicap

"

id

=

"

57173070

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1.5

"

subtype

=

"

123

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Odds mostbalanced Whether the odds are the most bal- Integer

anced odds or not. 1 = most balanced odds

0 = not most balanced odds

5.1.1.22(ID: 55) Include typeid in oddsfield tag

Enabling this setting will add an extra attribute typeid to OddsField elements.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5984472

"

matchtime

=

"

3

"

msgnr

=

"

15

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners

"

id

=

"

57178832

"

specialoddsvalue

=

"

7.5

"

subtype

=

"

126

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

typeid

=

"

373

"

>

2.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

typeid

=

"

374

"

>

1.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

ftr

=

"

-0.25

"

id

=

"

57178580

"

specialoddsvalue

=

"

-1.25

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

typeid

=

"

17

"

>

2.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

18

"

>

1.4

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

OddsField typeid Contains a numeric identifier of the Integer

odds field.

5.1.1.23(ID: 63) Include playerid in oddsfield tag

Enabling this setting will add an extra attribute playerid to OddsField elements which represent player-markets.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5984472

"

matchtime

=

"

3

"

msgnr

=

"

15

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next Goal scorer

"

id

=

"

67934496

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

147

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

playerid

=

"

2363

"

type

=

"

Hilbert, Roberto

"

typeid

=

"

469

"

>

24.0

</

OddsField

>

<

OddsField

active

=

"

1

"

playerid

=

"

11179

"

type

=

"

Spahic, Emir

"

typeid

=

"

470

"

>

47.0

</

OddsField

>

<

OddsField

active

=

"

1

"

playerid

=

"

15800

"

type

=

"

Bender, Lars

"

typeid

=

"

471

"

>

24.0

</

OddsField

>

<

OddsField

active

=

"

1

"

playerid

=

"

29791

"

type

=

"

Papadopoulos, Kyriakos

"

typeid

=

"

472

"

>

33.0

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

OddsField playerid Contains a numeric identifier of the Integer

player.

5.1.1.24(ID: 93) Include playerid in score and card event

Enabling this setting will add an extra attribute playerid to Card and Score elements.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

scoreandcardsummary

"

status

=

"

score

"

timestamp

=

"

1277801191793

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1355389

"

score

=

"

3:0

"

status

=

"

ended

"

>

<

Card

id

=

"

105609

"

player

=

"

Docherty

"

playerid

=

"

115622

"

team

=

"

home

"

time

=

"

1

"

type

=

"

red

"

/>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

105611

"

player

=

"

S.Lowry

"

playerid

=

"

77988

"

scoringteam

=

"

home

"

time

=

"

3

"

type

=

"

score

"

/>

<

Score

away

=

"

1

"

home

=

"

1

"

id

=

"

105619

"

player

=

"

R.Glendinning

"

playerid

=

"

115631

"

scoringteam

=

"

away

"

time

=

"

21

"

type

=

"

score

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Score, Card playerid Contains a numeric identifier of the Integer

player.

5.1.1.25(ID: 15) Include after overtime and after penalty score in score summary

The score and card summary contains the score on half time and score on full time in two separate Score elements. Enabling this

setting will add two more Score elements which indicate the score after overtime and the score after penalties. Each of those Score

elements gets added only if the match reaches the stage the element represents.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1423432823792

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

cornershome

=

"

6

"

cornersaway

=

"

6

"

earlybetstatus

=

"

stopped

"

matchid

=

"

6652509

"

msgnr

=

"

564

"

redcardsaway

=

"

0

"

redcardshome

=

"

0

"

score

=

"

4:5

"

setscores

=

"

0:0 -

0:0 - 0:0 - 4:5

"

status

=

"

ended

"

yellowcardsaway

=

"

0

"

yellowcardshome

=

"

4

"

yellowredcardsaway

=

"

0

"

yellowredcardshome

=

"

0

"

>

<

Score

away

=

"

3

"

home

=

"

3

"

id

=

"

8802822

"

player

=

"

Y.Toure

"

scoringteam

=

"

home

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Card

id

=

"

8802250

"

player

=

"

S.Tiene

"

team

=

"

home

"

time

=

"

57

"

type

=

"

yellow

"

/>

<

Card

id

=

"

8802568

"

player

=

"

E.Bertrand

"

team

=

"

home

"

time

=

"

105

"

type

=

"

yellow

"

/>

<

Card

id

=

"

8801682

"

player

=

"

S.Die

"

team

=

"

home

"

time

=

"

14

"

type

=

"

yellow

"

/>

<

Score

away

=

"

0

"

home

=

"

0

"

time

=

"

45

"

type

=

"

ht

"

/>

<

Score

away

=

"

4

"

home

=

"

3

"

id

=

"

8802842

"

player

=

"

J.Mensah

"

scoringteam

=

"

away

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

2

"

home

=

"

1

"

id

=

"

8802776

"

player

=

"

S.Aurier

"

scoringteam

=

"

home

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

4

"

home

=

"

4

"

id

=

"

8802854

"

player

=

"

S.Kalou

"

scoringteam

=

"

home

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

0

"

home

=

"

0

"

time

=

"

120

"

type

=

"

ot

"

/>

<

Score

away

=

"

1

"

home

=

"

0

"

id

=

"

8802732

"

player

=

"

M.Wakaso

"

scoringteam

=

"

away

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

2

"

home

=

"

2

"

id

=

"

8802792

"

player

=

"

S.Doumbia

"

scoringteam

=

"

home

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

4

"

home

=

"

2

"

id

=

"

8802842

"

player

=

"

J.Mensah

"

scoringteam

=

"

away

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

0

"

home

=

"

0

"

time

=

"

90

"

type

=

"

ft

"

/>

<

Score

away

=

"

5

"

home

=

"

4

"

id

=

"

8802868

"

player

=

"

E.Badu

"

scoringteam

=

"

away

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

2

"

home

=

"

0

"

id

=

"

8802750

"

player

=

"

J.Ayew

"

scoringteam

=

"

away

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

3

"

home

=

"

2

"

id

=

"

8802814

"

player

=

"

Dede

"

scoringteam

=

"

away

"

time

=

"

-1

"

type

=

"

score

"

/>

<

Score

away

=

"

5

"

home

=

"

4

"

time

=

"

120

"

type

=

"

pen

"

/>

<

Card

id

=

"

8802428

"

player

=

"

W.Kanon

"

team

=

"

home

"

time

=

"

87

"

type

=

"

yellow

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Score type The type of the score. The val- String. Values which get added when

ues "ot" and "pen" are only included enabling this setting:

if this setting is enabled and if the "ot" = score after overtime

match reaches those stages. "pen" = score after penalties

5.1.1.26(ID:94) Send error message on failed bookmatch requests

If this setting is enabled an error message will be sent in response when a bookmatch request is sent for a match that isn’t possible to

book, or already available.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

error

"

timestamp

=

"

1408607816955

"

>

<

Match

active

=

"

0

"

booked

=

"

0

"

matchid

=

"

1171785

"

status

=

"

not_started

"

/>

<

Message

>

Cannot book matchid: 1171785. This match is not offered within our live betting services,

only LCoO services

</

Message

>

</

BetbalancerLiveOdds

>

5.1.1.27(ID: 72) Include betstop reason

When a match is a scout match and the scout changes the match to bestop, it is possible that a reason for this betstop was included

by the scout. Clients which have this setting enabled will receive two additional attributes in the Match element, betstopreason and

betstopreasonid.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstop

"

time

=

"

0

"

timestamp

=

"

1395803868428

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

betstopreason

=

"

DANGEROUS_FREE_KICK_HOME

"

betstopreasonid

=

"

18

"

matchid

=

"

4885080

"

matchtime

=

"

55

"

msgnr

=

"

169

"

score

=

"

1:1

"

setscores

=

"

1:1

"

status

=

"

2p

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match betstopreason Contains a textual representation of String

the betstop reason. For possible values see table below.

betstopreasonid Contains a numeric identifier of the Integer

betstop reason. For possible values see table below.

Number Betstop Reason Number Betstop Reason

1 Possible goal 42 Possible Challenge [T1]

2 Possible red card 43 Possible Challenge [T2]

3 Scout lost 44 Possible Turnover

4 Possible goal [T1] 45 Unknown operator

5 Possible goal [T2] 46 Freeball

6 Possible red card [T1] 47 Deep Ball

7 Possible red card [T2] 48 Possible Run

8 Possible penalty 49 Maintenance

9 Possible penalty awarded to [T1] 50 Base Hit Deleted

10 Possible penalty awarded to [T2] 51 Match delayed

11 Connected to supervisor 52 Match postponed

12 Match ended 53 Scout disconnection tv signal

13 Gamepoint 54 Possible Penalty Offsetting

14 Tie 57 Possible fourth down attempt home

15 Possible direct foul [T1] 58 Possible fourth down attempt away

16 Possible direct foul [T2] 59 Possible onside kick home

17 Possible direct foul 60 Possible onside kick away

18 Dangerous free kick [T1] 61 Possible challenge

19 Dangerous free kick [T2] 62 Possible card

20 Dangerous goal position [T1] 63 Delayed penalty

21 Dangerous goal position [T2] 64 Shoot-out begins

22 Goal under review 65 Empty net

23 Score under review 66 Possible try home

24 Disconnection 67 Possible try away

25 Possible checkout 68 Possible drop goal home

26 Multiple suspensions 69 Possible drop goal away

27 Possible dangerous free kick 70 Possible card home

28 Possible dangerous goal position 71 Possible card away

29 Possible touch down [T1] 72 Possible penalty [T1]

30 Possible touch down [T2 ] 73 Possible penalty [T2]

31 Possible fieldgoal [T1] 74 Delayed penalty [T1]

32 Possible fieldgoal [T2] 75 Delayed penalty [T2]

33 Possible safety [T1 ] 76 Two man advantage home

34 Possible safety [T2 ] 77 Two man advantage away

35 Possible turnover [T1 ] 78 Possible field goal

36 Possible turnover [T2 ] 79 Rollback event

37 Video review 80 Possible drop kick home

38 Redzone [T1 ] 81 Possible drop kick away

39 Redzone [T2] 82 Possible drop kick

40 Possible boundary 83 Possible video assistant referee

41 Possible wicket 84 Feed interruption

5.1.1.28(ID: 102) Send empty meta response

If this setting activated a meta request will always respond with an XML message back, even if no matches are included.

5.1.1.29(ID: 20) Show period scores in all sports

If this setting is activated, for all sports the half time, full time, overtime and period scores are included in the setscores attribute.

5.1.1.30(ID: 123) Send clearbet message for any draw no bet, home no bet and away no bet market in case of a refund

When this is activated a clearbet message with refund will be sent when a draw no bet market ends in a draw, and not a cancelbet

message.

5.1.1.31(ID: 131) Include statusid attribute in Match element

The match status is sent as a string in the status attribute. In order to make it more machine-readable a statusid is included when

enabled. For a full overview of match statuses and IDs, they are found in chapter: 6

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

timestamp

=

"

1495003850487

"

status

=

"

change

"

>

<

Match

matchid

=

"

11360959

"

status

=

"

not_started

"

statusid

=

"

0

"

active

=

"

1

"

betstatus

=

"

stopped

"

clock_stopped

=

"

0

"

score

=

"

-:-

"

msgnr

=

"

1

"

/>

</

BetbalancerLiveOdds

>

6. Information per Sport

6 Information per sport

In this chapter you can find all the information you need to integrate one specific sport, gathered in one place. Each section is only

describing the sport specific options, for example XML attributes which come in addition to the regular XML attributes which can be

sent out for each sport.

The following areas are described for each sport:

Sport specific XML elements and attributes

XML configurations

Match statuses - The match status gives an indication of which context the current match is in, such as NOT_STARTED or

FIRST_PAUSE

An overview of all sports which are described in this chapter + their IDs can be found i the table below:

Sport id Sport name

16 American Football

13 Aussie Rules

31 Badminton

3 Baseball

2 Basketball

34 Beach volleyball

32 Bowls

109 Counter-Strike

21 Cricket

22 Darts

111 Dota2

29 Futsal

6 Handball

4 Ice hockey

110 League of Legends

12 Rugby

19 Snooker

1 Soccer

37 Squash

20 Table Tennis

5 Tennis

23 Volleyball

6.1 American Football

Sport specific information for American Football.

6.1.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for american football matches in addition to the standard elements

and attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413331559002

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

6139956

"

matchtime

=

"

1

"

msgnr

=

"

9

"

possession

=

"

2

"

position

=

"

70

"

remaining_time

=

"

60

"

remaining_time_in_period

=

"

15

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

try

=

"

1

"

yards

=

"

10

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match possession Which team has the ball. 1 = home team

2 = away team

0 = undefined

try Try number, it’s the current "down" A number in range [1,4]

until reaching the 10 yards if de- -1 = undefined.

fined.

yards Yards till first down. How many Number >= 0

yards down in this drive (the drive -1 = undefined.

is a series of offensive plays).

position Ball position will be sent as x yards Number in range [1,100]

to go till opponent’s end zone for -1 = undefined.

the team in possession. Please note that own x will be sent as

"100 – x" while opposite x will be sent

as "x".

remaining_time The remaining minutes of the Integer

match, without seconds.

This attribute needs to be enabled

in the XML configuration, see chap-

ter 6.1.2.2.

remaining_time_in_period The remaining minutes of the cur- Integer

rent period, without seconds.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.1.2.3.

Note

The attributes position, yards and tries are not updated during overtime. They will be set to "-1".

6.1.2 XML configuration

Sport specific XML configurations

6.1.2.1(ID: 54) Multiple bets of same type active at once for American football matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.1.2.2(ID: 49) Remaining time in American football

Enabling this setting will add the attribute remaining_time to the Match element for American football matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413331559002

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

6139956

"

matchtime

=

"

1

"

msgnr

=

"

9

"

possession

=

"

2

"

position

=

"

70

"

remaining_time

=

"

60

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

try

=

"

1

"

yards

=

"

10

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time The remaining minutes of the Integer

match, without seconds.

6.1.2.3(ID: 50) Remaining time for period in American football

Enabling this setting will add the attribute remaining_time_in_period to the Match element for American football matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413331559002

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

6139956

"

matchtime

=

"

1

"

msgnr

=

"

9

"

possession

=

"

2

"

position

=

"

70

"

remaining_time_in_period

=

"

15

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

try

=

"

1

"

yards

=

"

10

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time_in_period The remaining minutes of the cur- Integer

rent period, without seconds.

6.1.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

13 1q 1st quarter

301 pause1 2nd pause

14 2q 2nd quarter

302 pause2 2nd pause

15 3q 3rd quarter

303 pause3 3rd pause

16 4q 4th quarter

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

40 ot Overtime (in case a match goes to ex-

tra time)

110 after_ot Match finished after overtime This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.2 Aussie Rules

Sport specific information for Aussie Rules.

6.2.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for aussie rules matches in addition to the standard elements and

attributes.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

alive

"

timestamp

=

"

1486304651489

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1003188316

"

msgnr

=

"

34

"

score

=

"

1:0

"

setscores

=

"

0:0

"

status

=

"

ended

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match setscores Period_1 - Period_2 (aggregated String

score of all overtime sequences - For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

score of 7 meter shooutout)) So

maximum up to 5 scores while 3

and 4 are optional in case of over-

time and/or penalty shootout.

6.2.2 XML configuration

Sport specific XML configurations

6.2.2.1(ID: 130) Multiple bets of same type active at once for Aussie Rules matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting total, 1.5 and

3.5 would be sent as well.

6.2.2.2(ID: 133) Remaining time in Aussie rules

Enable this config to include the remaining_time attribute for the entire match in addition to the regular matchtime in aussie rules

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413331559002

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

6139956

"

matchtime

=

"

1

"

msgnr

=

"

9

"

possession

=

"

2

"

position

=

"

70

"

remaining_time

=

"

60

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

try

=

"

1

"

yards

=

"

10

"

/>

</

BetbalancerLiveOdds

>

6.2.2.3(ID: 134) Remaining time in period for Aussie rules

Enable this config to include remaining_time_in_period attribute. in addition to the normal matchtime in Aussie rules.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5876636

"

matchtime

=

"

1

"

msgnr

=

"

10

"

remaining_time_in_period

=

"

11:07

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

>

</

BetbalancerLiveOdds

>

6.2.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

13 1q 1st quarter

301 pause1 1st pause

14 2q 2nd quarter

302 pause2 2nd pause

15 3q 3rd quarter

303 pause3 3rd pause

16 4q 4th quarter

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

41 1p_ot 1st overtime period

33 ot_ht Pause between 1st and 2nd overtime This match status is not used unless the corresponding

period XML configuration is enabled. For more information, see

chapter 5.1.1.14.

42 2p_ot 2nd overtime period

110 after_ot Match finished after overtime This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

443 awaiting_sd Before sudden death

440 SD Sudden death

444 after_sd Match finished after sudden death

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.3 Badminton

Sport specific information for Badminton.

6.3.1 XML configuration

Sport specific XML configurations

6.3.1.1(ID: 100) Multiple bets of same type active at once for badminton matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.3.2 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

8 1set 1st set

301 pause1 1st pause

9 2set 2nd set

302 pause2 2nd pause

10 3set 3rd set

303 pause3 3rd pause

11 4set 4th set

304 pause4 4th pause

12 5set 5th set

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

97 defaulted1 The away team won because the

home team defaulted

98 defaulted2 The home team won because the

away team retired

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.4 Baseball

Sport specific information for Baseball.

6.4.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for baseball matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1411636139557

"

>

<

Match

active

=

"

1

"

awaybatter

=

"

4

"

balls

=

"

1

"

bases

=

"

0,0,0

"

betstatus

=

"

started

"

homebatter

=

"

1

"

matchid

=

"

5213426

"

msgnr

=

"

57

"

outs

=

"

2

"

score

=

"

0:1

"

setscores

=

"

0:1

"

status

=

"

1IT

"

strikes

=

"

1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match strikes Number of strikes for the current Number in range [0,2]

batter.

balls Number of balls for the current bat- Number in range [0,3]

ter.

outs Number of outs for the current in- Number in range [0,2]

ning.

homebatter Current batter for home team. Number in range [1,9]

awaybatter Current batter for away team. Number in range [1,9]

bases Which bases are loaded. "[1st base],[2nd base],[3rd base]". 0 =

not loaded, 1 = loaded. For example:

"0,1,1" - The first base is not loaded,

the second and third bases are loaded.

setscores Baseball: Period_1 - ... - Period_9 String

(aggregated score of all extra in- For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

nings). So maximum up to 5 scores

while 3 and 4 are optional in case of

overtime and/or penalty shootout.

6.4.2 XML configuration

Sport specific XML configurations

6.4.2.1(ID: 52) Multiple bets of same type active at once for baseball matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each

market, and only this one will be sent out to the client system. Enabling this setting will allow multiple bets of

the same type to be sent out at once, not only the most balanced ones. E.g. for the total market in soccer

the most balanced line would be 2.5. When enabling the setting, total 1.5 and 3.5 would be sent as well.

6.4.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

401 1IT 1st inning top

421 BT1B1 Break 1st top 1st bottom

402 1IB 1st inning bottom

422 BT2B1 Break 2nd top 1st bottom

403 2IT 2nd inning top

423 BT2B2 Break 2nd top 2nd bottom

404 2IB 2nd inning bottom

424 BT3B2 Break 3rd top 2nd bottom

405 3IT 3rd inning top

425 BT3B3 Break 3rd top 3rd bottom

406 3IB 3rd inning bottom

426 BT4B3 Break 4th top 3rd bottom

407 4IT 4th inning top

427 BT4B4 Break 4th top 4th bottom

408 4IB 4th inning bottom

428 BT5B4 Break 5th top 4th bottom

409 5IT 5th inning top

429 BT5B5 Break 5th top 5th bottom

410 5IB 5th inning bottom

430 BT6B5 Break 6th top 5th bottom

411 6IT 6th inning top

431 BT6B6 Break 6th top 6th bottom

412 6IB 6th inning bottom

432 BT7B6 Break 7th top 6th bottom

413 7IT 7th inning top

433 BT7B7 Break 7th top 7th bottom

414 7IB 7th inning bottom

434 BT8B7 Break 8th top 7th bottom

415 8IT 8th inning top

435 BT8B8 Break 8th top 8th bottom

416 8IB 8th inning bottom

436 BT9B8 Break 9th top 8th bottom

417 9IT 9th inning top

437 BT9B9 Break 9th top 9th bottom

418 9IB 9th inning bottom

438 BTEIB9 Break EI top 9th bottom

419 EIT Extra inning top

439 BTEIBEI Break EI top EI bottom

420 EIB Extra inning bottom

100 ended The match has ended

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned

Status controlled by XML configuration. see 5.1.1.16

6.5 Basketball

Sport specific information for Basketball.

6.5.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for basketball matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

clock_stopped

=

"

0

"

matchid

=

"

5876636

"

matchtime

=

"

1

"

msgnr

=

"

10

"

remaining_time

=

"

47:07

"

remaining_time_in_period

=

"

11:07

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time This contains remaining minutes String

and seconds in the match. Format: <minutes>:<seconds>

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.5.2.3.

remaining_time_in_period This contains remaining minutes String

and seconds in the current period. Format: <minutes>:<seconds>

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.5.2.4.

clock_stopped Whether the clock is running or the Integer

clock is stopped. 1 = Clock is stopped

This attribute needs to be enabled 0 = Clock is running

in the XML configuration, for more

information see chapter 5.1.1.10.

setscores Basketball: Period_1 - ... - Pe- String

riod_4 (aggregated score of all For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

overtime sequences) So maximum

up to 5 scores while 3 and 4 are

optional in case of overtime and/or

penalty shootout.

6.5.2 XML configuration

Sport specific XML configurations

6.5.2.1(ID: 53) Multiple bets of same type active at once for basketball matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.5.2.2(ID: 42) Use additional match statuses for overtime basketball

If this setting is enabled, the following additional match statuses will be used for overtime in basketball:

Id Status Status description Additional information

32 awaiting_ot Waiting for overtime to start Match gets this status if the match has overtime.

110 after_ot Match finished after overtime Match gets this status if the match has overtime.

6.5.2.3(ID: 10) Remaining time in basketball

Enabling this setting will add the attribute remaining_time to the Match element for basketball matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5876636

"

matchtime

=

"

1

"

msgnr

=

"

10

"

remaining_time

=

"

47:07

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time This contains remaining minutes String

and seconds in the match. Format: <minutes>:<seconds>

6.5.2.4(ID: 17) Remaining time for period in basketball

Enabling this setting will add the attribute remaining_time_in_period to the Match element for basketball matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5876636

"

matchtime

=

"

1

"

msgnr

=

"

10

"

remaining_time_in_period

=

"

11:07

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1q

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time_in_period This contains remaining minutes String

and seconds in the current period. Format: <minutes>:<seconds>

6.5.3 Match statuses

Regular matches

Id Status Status description Additional information

0 not_started Not started yet

13 1q 1st quarter

301 pause1 1st pause

14 2q 2nd quarter

302 pause2 2nd pause

15 3q 3rd quarter

303 pause3 3rd pause

16 4q 4th quarter

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14

40 ot Overtime (Used for the duration of

overtime)

110 after_ot Match finished after overtime Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

NCAA matches

Id Status Status description Additional information

0 not_started Not started yet

1 1p 1st period of the match

31 paused Match pause

2 2p 2nd period of the match

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14

40 ot Overtime (Used for the duration of

overtime)

61 delayed The match start is delayed

110 after_ot Match finished after overtime Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.6 Beach Volleyball

Sport specific information for Beach Volleyball.

6.6.1 XML configuration

Sport specific XML configurations

6.6.1.1(ID: 33) Multiple bets of same type active at once for beach volleyball matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting total 1.5 and

3.5 would be sent as well.

6.6.2 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

8 1set 1st set

301 pause1 1st pause

9 2set 2nd set

302 pause2 2nd pause

10 3set 3rd set

303 pause3 3rd pause

11 4set 4th set

304 pause4 4th pause

12 5set 5th set

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.7 Bowls

Sport specific information for Bowls.

6.7.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for bowls matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstop

"

time

=

"

0

"

timestamp

=

"

1413458626905

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

4977471

"

msgnr

=

"

5

"

score

=

"

0.0:0.0

"

setscores

=

"

0:0

"

status

=

"

1set

"

remaining_bowls_home

=

"

3

"

remaining_bowls_away

=

"

4

"

current_end

=

"

1

"

delivery

=

"

2

"

/>

</

BetbalancerLiveOdds

>

XML attributes defnition

Element Attributes

Attribute Description Possible values

Match delivery The player which will deliver the 1 = home

next bowl 2 = away

remaining_bowls_home The remaining bowls for the home Number >= 0

team.

remaining_bowls_away The remaining bowls for the away Number >= 0

team.

current_end Current end in set. Integer

6.7.2 XML configuration

Sport specific XML configurations

6.7.2.1(ID: 92) Multiple bets of same type active at once for bowls matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting total 1.5 and

3.5 would be sent as well.

6.7.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

8 1set 1st set

301 pause1 1st pause

9 2set 2nd set

302 pause2 2nd pause

10 3set 3rd set

303 pause3 3rd pause

11 4set 4th set

304 pause4 4th pause

12 5set 5th set

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

97 defaulted1 The away team won because the

home team defaulted

98 defaulted2 The home team won because the

away team retired

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.8 Counter-Strike

Sport specific information for Counter-Strike.

6.8.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for counter-strike matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

alive

"

timestamp

=

"

1456304650377

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1003188216

"

msgnr

=

"

37

"

score

=

"

1:0

"

setscores

=

"

19:15

"

status

=

"

ended

"

current_ct_team

=

"

1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match current_ct_team Which team is currently playing on 1 = home team

CT side. 2 = away team

6.8.2 XML configuration

Sport specific XML configurations

6.8.2.1(ID: 110) Multiple bets of same type active at once for Counter-Strike matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting total 1.5 and

3.5 would be sent as well.

6.8.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

141 1map 1st map

301 pause1 1st pause

142 2map 2nd map

302 pause2 2nd pause

143 3map 3rd map

303 pause3 3rd map

144 4map 4thmap

304 pause4 4th pause

145 5map 5th map

305 pause5 5th pause

146 6map 6th map

306 pause6 6th pause

147 7map 7th map

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.9 Cricket

Sport specific information for Cricket.

6.9.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for cricket matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

type

=

"

scoutmatch

"

timestamp

=

"

1413534449872

"

time

=

"

0

"

status

=

"

betstart

"

>

<

Match

dismissals_away

=

"

0

"

dismissals_home

=

"

1

"

over

=

"

2

"

innings

=

"

1

"

penalty_runs_away

=

"

0

"

penalty_runs_home

=

"

0

"

delivery

=

"

1

"

status

=

"

1i_ht

"

score

=

"

6:0

"

msgnr

=

"

17

"

matchid

=

"

1616800

"

betstatus

=

"

started

"

active

=

"

1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match dismissals_home Amount of dismissals of the home Number in range [0,10]

team in the current innings.

dismissals_away Amount of dismissals of the away Number in range [0,10]

team in the current innings.

penalty_runs_home How many penalty runs the home Number >= 0

team has.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.9.2.1.

penalty_runs_away How many penalty runs the away Number >= 0

team has.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.9.2.1.

innings What innings it is. Number in range [1,2]

Note that the second innings can also

be superover.

over What over in the innings it is. A number > 0

The first over will have value 1, please

note this is different from the Cricket

convention which would start counting

at zero.

delivery Which ball delivery in the over it is. Number in range [1,6]

6.9.2 XML configuration

Sport specific XML configurations

6.9.2.1(ID: 96) Include penalty runs in cricket

Enabling this setting will add the attributes penalty_runs_home and penalty_runs_away to the Match element for cricket matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

timestamp

=

"

1413534449872

"

time

=

"

0

"

status

=

"

betstart

"

>

<

Match

dismissals_away

=

"

0

"

dismissals_home

=

"

1

"

over

=

"

2

"

innings

=

"

1

"

penalty_runs_away

=

"

0

"

penalty_runs_home

=

"

0

"

delivery

=

"

1

"

status

=

"

1i_ht

"

score

=

"

6:0

"

msgnr

=

"

17

"

matchid

=

"

1616800

"

betstatus

=

"

started

"

active

=

"

1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match penalty_runs_home How many penalty runs the home Number >= 0

team has.

penalty_runs_away How many penalty runs the away Number >= 0

team has.

6.9.2.2(ID: 98) Multiple bets of same type active at once for Cricket matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.9.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

501 1i_ht First innings, home team

502 1i_at First innings, away team

503 2i_ht Second innings, home team

504 2i_at Second innings, away team

505 awaiting_so Awaiting super over

506 so_ht Super over, home team

507 so_at Super over, away team

508 after_so After super over

509 innings_break Innings break

510 so_break Super over break

511 lunch_break Lunch break

512 tea_break Tea break

513 stumps Stumps

100 ended The match has ended

80 interrupted The match has been interrupted

90 ended The match has ended Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.10 Darts

Sport specific information for Darts.

6.10.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for darts matches in addition to the standard elements and attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1412524848268

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

legscore

=

"

501:501

"

matchid

=

"

6198374

"

msgnr

=

"

61

"

score

=

"

0:0

"

setscores

=

"

0:3

"

status

=

"

in_progress

"

throw

=

"

1

"

visit

=

"

1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match legscore Current score in the leg. Score in range "[0-501]:[0-501]"

throw Which player got the first throw for 1 = home

the current leg. 2 = away

visit The player which is visiting the 1 = home

board. 2 = away

6.10.2 XML configuration

Sport specific XML configurations

6.10.2.1(ID: 76) Multiple bets of same type active at once for darts matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.10.2.2(ID: 104) Early bet status in darts

Enabling this setting will trigger an early betstart if a betstop has been set because a player is on possible checkout. See chapter

6.19.2.4 for more information about early betstatus.

6.10.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

21 in_progress The match is in progress

30 paused Match paused

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

97 defaulted1 The away team won because the

home team defaulted

98 defaulted2 The home team won because the

away team retired

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.11 Dota 2

Sport specific information for Dota2.

6.11.1 XML configuration

Sport specific XML configurations

6.11.1.1(ID: 112) Multiple bets of same type active at once for Dota 2 matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.11.2 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

141 1map 1st map

301 pause1 1st pause

142 2map 2nd map

302 pause2 2nd pause

143 3map 3rd map

303 pause3 3rd pause

144 4map 4th map

304 pause4 4th pause

145 5map 5th map

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.12 Field hockey

Sport specific information for Field hockey.

6.12.1 Match statuses

2 x 35 minutes including SD/PSO format

Id Status Status description Additional information

0 not_started Not started yet

6 1p 1st period of the match

31 paused Match paused

7 2p 2nd period of the match

100 ended The match has ended

443 awatingi_sd Before sudden death

440 SD Sudden death

444 after_sd Match finished after sudden death

34 awaiting_pen Waiting for penalty shoot-out to start

50 pen Penalty shoot-out

120 ended The match has ended after penalties

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

60 postponed The match has been postponed

4x 15 minutes including PSO format

Id Status Status description Additional information

0 not_started Not started yet

13 1st_quarter 1st quarter

301 1st_pause 1st pause

14 2nd_quarter 2nd quarter

302 2nd_pause 2nd pause

15 3rd_quarter 3rd quarter

303 3rd_pause 3rd pause

16 4th_quarter Waiting for penalty shoot-out to start

100 ended The match has ended

34 awaiting_pen Waiting for penalty shoot-out to start

50 pen Penalty shoot-out

120 ended The match has ended after penalties

61 delayed the match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

60 postoponed The match has been postponed

6.13 Futsal

Sport specific information for Futsal.

6.13.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for futsal matches in addition to the standard elements and attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clock_stopped

=

"

1

"

earlybetstatus

=

"

stopped

"

matchid

=

"

6414605

"

matchtime

=

"

8

"

msgnr

=

"

37

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

suspendAway

=

"

0

"

suspendHome

=

"

0

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match clock_stopped Whether the clock is running or the Integer

clock is stopped. 1 = Clock is stopped

This attribute needs to be enabled 0 = Clock is running

in the XML configuration, for more

information see chapter 5.1.1.10.

suspendHome The amount of suspensions for the Number >= 0

home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.20.

suspendAway The amount of suspensions for the Number >= 0

away team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.20.

setscores Period_1 - Period_2 (aggregated String

score of all overtime sequences For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

- score of penalty shooutout) So

maximum up to 5 scores while 3

and 4 are optional in case of over-

time and/or penalty shootout.

6.13.2 XML configuration

Sport specific XML configurations

6.13.2.1(ID:51) Multiple bets of same type active at once for futsal matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.13.2.2(ID: 58) Early bet status in futsal

Enabling this setting will trigger an early betstart if a betstop has been set because a goal was scored. See chapter 6.19.2.4 for more

information about early betstatus.

6.13.2.3(ID: 136) Add new attribute with extended matchtime info for Futsal

When this is activated a new attribute matchetime_extended will be included in the match element, showing more detailed

matchtime information.

XML examples

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777649605

"

>

<

Match

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

41

"

matchtime_extended

=

"

40:48

"

active

=

"

1

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

45

"

matchtime_extended

=

"

45:00

+02:30

"

active

=

"

1

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

6.13.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

6 1p 1st period of the match

31 paused Match pause

7 2p 2nd period of the match

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start Status controlled by XML configuration. For more informa-

ended tion, see chapter 5.1.1.14

41 1p_ot 1st overtime period

33 ot_ht Pause between 1st and 2nd overtime Status controlled by XML configuration. For more informa-

1p_ot period tion, see chapter 5.1.1.14

42 2p_ot 2nd overtime period

110 after_ot Match finished after overtime Status controlled by XML configuration. For more informa-

ended tion, see chapter 5.1.1.14

34 awaiting_pen Waiting for penalty shoot-out to start Status controlled by XML configuration. For more informa-

pen tion, see chapter 5.1.1.14

50 pen penalty shoot-out

120 ended The match has ended after penalties

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.14 Handball

Sport specific information for Handball.

6.14.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for handball matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clock_stopped

=

"

0

"

matchid

=

"

6412133

"

matchtime

=

"

2

"

msgnr

=

"

12

"

remaining_time

=

"

58:08

"

remaining_time_in_period

=

"

28:08

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

suspendAway

=

"

0

"

suspendHome

=

"

0

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match clock_stopped Whether the clock is running or the Integer

clock is stopped. 1 = Clock is stopped

This attribute needs to be enabled 0 = Clock is running

in the XML configuration, for more

information see chapter 5.1.1.10.

remaining_time This contains remaining minutes String

and seconds in the match. Format: <minutes>:<seconds>

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.14.2.2.

remaining_time_in_period This contains remaining minutes String

and seconds in the current period. Format: <minutes>:<seconds>

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.14.2.3.

suspendHome The amount of suspensions for the Number >= 0

home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.20.

suspendAway The amount of suspensions for the Number >= 0

away team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.20.

setscores Period_1 - Period_2 (aggregated String

score of all overtime sequences - For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

score of 7 meter shooutout) So

maximum up to 5 scores while 3

and 4 are optional in case of over-

time and/or penalty shootout.

6.14.2 XML configuration

Sport specific XML configurations

6.14.2.1(ID:31) Multiple bets of same type active at once for handball matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.14.2.2(ID: 27) Remaining time in handball

Enabling this setting will add the attribute remaining_time to the Match element for handball matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

6412133

"

matchtime

=

"

2

"

msgnr

=

"

12

"

remaining_time

=

"

58:08

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time This contains remaining minutes String

and seconds in the match. Format: <minutes>:<seconds>

6.14.2.3(ID: 28) Remaining time for period in handball

Enabling this setting will add the attribute remaining_time_in_period to the Match element for handball matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

6412133

"

matchtime

=

"

2

"

msgnr

=

"

12

"

remaining_time_in_period

=

"

28:08

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time_in_period This contains remaining minutes String

and seconds in the current period. Format: <minutes>:<seconds>

6.14.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

6 1p 1st period of the match

31 paused Match pause

7 2p 2nd period of the match

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14.

40 ot Overtime (in case a match goes to ex-

tra time)

41 1p_ot 1st overtime period

33 ot_ht Pause between 1st and 2nd overtime Status controlled by XML configuration. For more informa-

period tion, see chapter 5.1.1.14.

42 2p_ot 2nd overtime period

110 after_ot Match finished after overtime Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14.

34 awaiting_pen Waiting for penalty shoot-out to start Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.14.

50 pen penalty shoot-out

120 ended The match has ended after penalties

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.15 Ice Hockey

Sport specific information for Ice Hockey.

6.15.1 Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for ice hockey matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

clock_stopped

=

"

0

"

earlybetstatus

=

"

stopped

"

matchid

=

"

5603964

"

matchtime

=

"

3

"

msgnr

=

"

12

"

remaining_time

=

"

57:59

"

remaining_time_in_period

=

"

17:59

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

suspendAway

=

"

0

"

suspendHome

=

"

0

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match clock_stopped Whether the clock is running or the Integer

clock is stopped. 1 = Clock is stopped

This attribute needs to be enabled 0 = Clock is running

in the XML configuration, for more

information see chapter 5.1.1.10.

matchtime The playing minute of the match. Number > 0

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.15.2.1.

remaining_time This contains remaining minutes String

and seconds in the match. Format: <minutes>:<seconds>

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.15.2.2.

remaining_time_in_period This contains remaining minutes String

and seconds in the current period. Format: <minutes>:<seconds>

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.15.2.3.

suspendHome The amount of suspensions for the Number >= 0

home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.20.

suspendAway The amount of suspensions for the Number >= 0

away team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 5.1.1.20.

setscores Period_1 - Period_2 - Period_3 - String

OT (aggregated in case of multi- For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

ple overtimes) - PEN_Shootout. So

maximum up to 5 scores while 3

and 4 are optional in case of over-

time and/or penalty shootout.

6.15.2 XML configuration

Sport specific XML configurations

6.15.2.1(ID: 3) Include match time for ice hockey

Enabling this setting will add the attribute matchtime to the Match element for ice hockey matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5603964

"

msgnr

=

"

12

"

matchtime

=

"

3

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

XML atributes definition

Element Attributes

Attribute Description Possible values

Match matchtime The playing minute of the match. Integer

6.15.2.2(ID: 25) Remaining time in ice hockey

Enabling this setting will add the attribute remaining_time to the Match element for ice hockey matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5603964

"

matchtime

=

"

3

"

msgnr

=

"

12

"

remaining_time

=

"

57:59

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time This contains remaining minutes String

and seconds in the match. Format: <minutes>:<seconds>

6.15.2.3(ID: 26) Remaining time for period in Ice Hockey

Enabling this setting will add the attribute remaining_time_in_period to the Match element for ice hockey matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5603964

"

matchtime

=

"

3

"

msgnr

=

"

12

"

remaining_time_in_period

=

"

17:59

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match remaining_time_in_period This contains remaining minutes String

and seconds in the current period. Format: <minutes>:<seconds>

6.15.2.4(ID: 19) Show different pause match status in ice hockey

When an ice hockey match enters a break the match gets the status paused. the second break. Enabling this setting will replace the

match status paused statuses:

This will not tell the client whether it’s the first or for ice hockey matches with the following match

Id Status Status description Additional information

301 pause1 The first pause This match status replaces the regular pause match sta-

tus.

302 pause2 The second pause This match status replaces the regular pause match sta-

tus.

6.15.2.5(ID: 40) Use additional match statuses for overtime/penalty ice hockey

Enabling this setting will add the following match statuses to ice hockey matches, if the match reaches those stages:

Id Status Status description Additional information

32 awaiting_ot Waiting for overtime to start

110 after_ot Match finished after overtime

34 awaiting_pen Wating for penalty shoot-out to start

6.15.2.6(ID: 7) Multiple bets of same type active at once for ice hockey matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.15.2.7(ID: 60) Early bet status in ice hockey

Enabling this setting will trigger an early betstart if a betstop has been set because a goal was scored. See chapter 6.19.2.4 for more

information about early betstatus.

6.15.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

1 1p 1st period

2 2p 2nd period

3 3p 3rd period

301 paused 1st Pause Status controlled by XML configuration. For more informa-

pause1 tion, see chapter 6.15.2.4

302 paused 2nd Pause Status controlled by XML configuration. For more informa-

pause2 tion, see chapter 6.15.2.4

32 awaiting_ot Waiting for overtime to start Status controlled by XML configuration. For more informa-

ot tion, see chapter 5.1.1.14

40 ot Overtime (Used for the duration of

overtime)

110 after_ot Match finished after overtime Status controlled by XML configuration. For more informa-

ended tion, see chapter 5.1.1.14

34 awaiting_pen Waiting for penalty shoot-out to start Status controlled by XML configuration. For more informa-

pen tion, see chapter 5.1.1.14

50 pen penalty shoot-out

100 ended The match has ended

120 ended The match has ended after penalties

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.16 League Of Legends

Sport specific information for League of Legends.

6.16.1 XML configuration

Sport specific XML configurations

6.16.1.1(ID: 116) Multiple bets of same type active at once for League Of Legends matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.16.2 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

141 1map 1st map

301 paused 1st pause

142 2map 2nd map

302 paused 2nd pause

143 3map 3rd map

303 paused 3rd pause

144 4map 4th map

304 paused 4th pause

145 5map 5th map

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.17 Rugby

Sport specific information for Rugby.

6.17.1 Sport specific XML elements and attributes

This section explains what elements, sub-elements and attributes one can expect for rugby matches in addition to the standard

elements and attributes.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

alive

"

timestamp

=

"

1456304650377

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1003188216

"

msgnr

=

"

37

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

ended

"

/>

</

BetbalancerLiveOdds

>

XML attributes definitions

Element Attributes

Attribute Description Possible values

Match setscores Period_1 - Period_2 (aggregated String

score of all overtime and sudden For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

death sequences - score of drop

kick competition) So maximum up

to 5 scores while 3 and 4 are op-

tional in case of overtime and/or

penalty shootout.

6.17.2 XML configuration

Sport specific XML configurations

6.17.2.1(ID: 74) Multiple bets of same type active at once for rugby matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.17.2.2(ID: 135) Add new attribute with extended matchtime info for Rugby

When this is activated, a new attribute matchetime_extended will be included in the match element, showing more detailed

matchtime information.

XML examples

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777649605

"

>

<

Match

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

41

"

matchtime_extended

=

"

40:48

"

active

=

"

1

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

45

"

matchtime_extended

=

"

45:00

+02:30

"

active

=

"

1

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

6.17.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

6 1p 1st period of the match

31 paused Match pause

7 2p 2nd period of the match

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

40 ot Overtime (in case a match goes to ex-

tra time)

41 1p_ot 1st overtime period

33 ot_ht Pause between 1st and 2nd overtime This match status is not used unless the corresponding

period XML configuration is enabled. For more information, see

chapter 5.1.1.14.

42 2p_ot 2nd overtime period

110 after_ot Match finished after overtime This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

34 awaiting_pen Wating for penalty shoot-out to start This match status is not used unless the corresponding

XML configuration is enabled. For more information, see

chapter 5.1.1.14.

50 pen Penalty shoot-out

120 ended The match has ended after penalties

443 awaiting_sd Before sudden death

440 SD Sudden death

444 after_sd After sudden death

60 postponed The match has been postponed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.18 Snooker

Sport specific information for Snooker.

6.18.1 Sport specific XML elements and attributes

This section explains what elements, sub-elements and attributes one can expect for snooker matches in addition to the stan- dard

elements and attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1414574453652

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

2097712

"

msgnr

=

"

5

"

remaining_reds

=

"

15

"

score

=

"

0:0

"

setscore1

=

"

0:0

"

status

=

"

in_progress

"

visit

=

"

1

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match visit Which player is currently visiting. 1 = home team

2 = away team

0 = undefined

remaining_reds Number of remaining red balls. Integer

6.18.2 XML configuration

Sport specific XML configurations

6.18.2.1(ID: 78) Multiple bets of same type active at once for snooker matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.18.2.2(ID: 127) Include snooker markets for frames which might not be played

If set, then markets for frames which may not be played will be included in the feed, example frame 6 when matchscore is 4:0 in best

of 9.

6.18.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

21 in_progress The match is in progress

30 paused Match paused

445 session_break Session break

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

97 defaulted1 The away team won because the

home team defaulted

98 defaulted2 The home team won because the

away team retired

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.19 Soccer

Sport specific information for Soccer.

6.19.1 Sport specific XML elements and attributes

This section explains what elements, sub-elements and attributes one can expect for soccer matches in addition to the standard

elements and attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

5650450

"

matchtime

=

"

1

"

matchtime_extended

=

"

0:00

"

msgnr

=

"

6

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

cornersaway

=

"

2

"

cornershome

=

"

5

"

redcardsaway

=

"

0

"

redcardshome

=

"

0

"

yellowcardsaway

=

"

1

"

yellowcardshome

=

"

0

"

yellowredcardsaway

=

"

0

"

yellowredcardshome

=

"

0

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match matchtime_extended This will also display the injury time. String

This attribute needs to be enabled Example: "45:00 +02:30"

in the XML configuration, for more

information see chapter 6.19.2.3.

cornersaway The amount of corners for the away Integer

team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

cornershome The amount of corners for the Integer

home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

redcardsaway The amount of red cards for the Integer

away team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

redcardshome The amount of red cards for the Integer

home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

yellowcardsaway The amount of yellow cards for the Integer

away team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

yellowcardshome The amount of yellow cards for the Integer

home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

yellowredcardsaway The amount of yellow-red cards for Integer

the away team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

yellowredcardshome The amount of yellow-red cards for Integer

the home team.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.19.2.2.

setscores Period_1 - Period_2 (aggregated String

score of all overtime sequences - For example: "1:0 - 1:0 - 0:0 - 0:0 - 0:1"

score of penalty meter shooutout)

So maximum up to 5 scores while 3

and 4 are optional in case of over-

time and/or penalty shootout.

6.19.2 XML configuration

Sport specific XML configurations

6.19.2.1(ID: 5) Multiple bets of same type active at once for soccer matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting total 1.5 and

3.5 would be sent as well.

6.19.2.2(ID: 34) Include corner and card counts

Enabling this setting will include corner and card counters for all deeper coverage soccer matches. The different counters will be

added as attributes to the Match element.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5650450

"

matchtime

=

"

1

"

msgnr

=

"

6

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

cornersaway

=

"

2

"

cornershome

=

"

5

"

redcardsaway

=

"

0

"

redcardshome

=

"

0

"

yellowcardsaway

=

"

1

"

yellowcardshome

=

"

0

"

yellowredcardsaway

=

"

0

"

yellowredcardshome

=

"

0

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match cornersaway The amount of corners for the away Integer

team.

cornershome The amount of corners for the Integer

home team.

redcardsaway The amount of red cards for the Integer

away team.

redcardshome The amount of red cards for the Integer

home team.

yellowcardsaway The amount of yellow cards for the Integer

away team.

yellowcardshome The amount of yellow cards for the Integer

home team.

yellowredcardsaway The amount of yellow-red cards for Integer

the away team.

yellowredcardshome The amount of yellow-red cards for Integer

the home team.

6.19.2.3(ID: 64) Add new attribute with extended matchtime info for soccer

Enabling this setting will add the attribute matchtime_extended to the Match element for soccer matches.

XML examples

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777649605

"

>

<

Match

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

41

"

matchtime_extended

=

"

40:48

"

active

=

"

1

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

betstatus

=

"

started

"

matchid

=

"

4761252

"

matchtime

=

"

45

"

matchtime_extended

=

"

45:00 +02:30

"

active

=

"

1

"

msgnr

=

"

88

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Odds matchtime_extended An extended format of the match String

time. If the match is in injury time Format: "mm:ss" or "mm:ss +mm:ss"

this gets included as well.

6.19.2.4(ID: 35) Early betstart in soccer after a goal has been scored and confirmed

Right before one of the teams scores a goal, the match status will be set to betstop. Normally, the match will be on betstop until the

match continues, which is after the next kick off.

As bookmakers have different requirements in terms of reoffering markets after goals, we allows clients to enable early betstart.

Enabling this setting will send information related to early betstart in addition to the normal betstart information. This

information gets passed through an attribute earlybetstatus in the Match element, in addition to the regular betstatus attribute.

The behaviour of early betstart is quite similar to the normal betstart, but instead of waiting until the next kick off, early betstart

already starts right after the goal was confirmed.

Figure 9: Flowchart describing the different states of the betstatus and earlybetstart element

If one or both of the betstatus and earlybetstatus are set to "started" the match can be treated as betstart. It is up to the book- maker

to decide whether to receive the new prices right after the score change or after the match continues.

XML example - During the match

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1395839620340

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10755

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

XML example - Goal

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1395839596131

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

earlybetstatus

=

"

stopped

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10752

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

101058

"

player

=

"

scoringteam

=

"

home

"

time

=

"

1

"

type

=

"

live

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

XML example - Goal confirmed (early betstart)

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1395839596201

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

earlybetstatus

=

"

started

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10753

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

XML example - Kick off (normal betstart)

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1395839620294

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

started

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10754

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

betstatus Whether the match is in betstart or String

betstop "started" = betstart

value of this attribute is only set to "stopped" = betstop

"started" if an early betstart is actu-

earlybetstatus Whether the match is in early bet- String

start or early betstop. Note that the "started" = early betstart

6.19.2.5(ID: 68) Include early bet status in soccer when there is a possible dangerous free kick situation

Enabling this setting will trigger an early betstart if a betstop has been set because of a dangerous free kick situation. See chapter

6.19.2.4 for more information about early betstatus.

6.19.2.6(ID: 57) Offer soccer half-time markets until the end of 1st half

Usually the halftime bets are deactivated after minute 43. Enabling this setting will continue sending bets to the client system until 1

minute prior the end of injury time of the first half. Note that outcomes representing no further goals (e.g. Next goal first half "None")

will be inactive during injury time.

6.19.2.7(ID: 56) Offer odds after minute 90 for basic coverage scout soccer matches

Usually all the bets are deactivated after minute 90. Enabling this setting will continue sending bets to the client system until 1 minute

prior the end of injury time. Note that outcomes representing no further goals (e.g. Next goal "None") will be inactive during injury

time.

6.19.2.8(ID: 61) Include Asian Handicap spread for the rest for all Asian Handicap markets

Enabling this setting will add an extra attribute ftr to the Odds elements. This attribute contains the handicap value for the rest of the

match (but not odds values for the rest of the match). This is in addition to the special odds value which reflects the handicap value

for the whole match.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

5984472

"

matchtime

=

"

3

"

msgnr

=

"

15

"

score

=

"

1:0

"

setscores

=

"

1:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

ftr

=

"

-0.25

"

id

=

"

57178580

"

specialoddsvalue

=

"

-1.25

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

typeid

=

"

17

"

>

2.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

typeid

=

"

18

"

>

1.4

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Odds ftr The handicap value for the rest of Number

the match

6.19.2.9(ID: 119) Early betstatus during in-game penalties for soccer

If enabled the earlybetstatus attribute will be set to "started" once a penalty is confirmed until the player is about to take the penalty.

Note that early betstart attribute will not be set to ended in case of a red card. This configuration needs to be enabled in order to offer

the market "Will the Xth penalty be scored". See chapter 6.19.2.4 for more information about early betstatus.

6.19.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

6 1p 1st period of the match

31 paused Match pause

7 2p 2nd period of the match

100 ended The match has ended

32 awaiting_ot Waiting for overtime to start Status controlled by XML configuration. For more informa-

ended tion, see chapter 5.1.1.14

41 1p_ot 1st overtime period

33 ot_ht Pause between 1st and 2nd overtime Status controlled by XML configuration. For more informa-

1p_ot period tion, see chapter 5.1.1.14

42 2p_ot 2nd overtime period

110 after_ot Match finished after overtime Status controlled by XML configuration. For more informa-

ended tion, see chapter 5.1.1.14

34 awaiting_pen Waiting for penalty shoot-out to start Status controlled by XML configuration. For more informa-

pen tion, see chapter 5.1.1.14

50 pen penalty shoot-out

120 ended The match has ended after penalties

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.20 Squash

Sport specific information for Squash.

6.20.1 XML configuration

Sport specific XML configurations

6.20.1.1(ID: 114) Multiple bets of same type active at once for squash matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.20.2 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

151 1g 1st game

301 pause1 1st pause

152 2g 2nd game

302 pause2 2nd pause

153 3g 3rd game

303 pause3 3rd pause

154 4g 4th game

304 pause4 4th pause

155 5g 5th game

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

97 defaulted1 The away team won because the

home team defaulted

98 defaulted2 The home team won because the

away team retired

200 injury_break A break due to injury.

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.21 Table tennis

Sport specific information for Table tennis.

6.21.1 Sport specific XML elements and attributes

This section explains what elements, sub-elements and attributes one can expect for table tennis matches in addition to the standard

elements and attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1414658826975

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

expedite

=

"

0

"

matchid

=

"

2097712

"

msgnr

=

"

3

"

server

=

"

1

"

score

=

"

0:0

"

setscore1

=

"

0:0

"

status

=

"

1set

"

/>

</

BetbalancerLiveOdds

>

XML attributes definitions

Element Attributes

Attribute Description Possible values

Match expedite Whether the expedite system is in 1 = expedite system enabled

operation or not. 0 = expedite system disabled

server Which player has the serve at that 1 = player one

moment. This is an optional at- 2 = player two.

tribute and will be set once the first

server is known.

6.21.2 XML configuration

Sport specific XML configurations

6.21.2.1(ID: 80) Multiple bets of same type active at once for table tennis matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.21.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

8 1set 1st set

301 pause1 1st pause

9 2set 2nd set

302 pause2 2nd pause

10 3set 3rd set

303 pause3 3rd pause

11 4set 4th set

304 pause4 4th pause

12 5set 5th set

305 pause5 5th pause

441 6set 6th set

306 pause6 6th pause

443 7set 7th set

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

97 defaulted1 The away team won because the

home team defaulted

98 defaulted2 The home team won because the

away team retired

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.22 Tennis

Sport specific information for Tennis.

6.22.1 Sport specific XML elements and attributes

This section elements, sub-elements and attributes one can expect for tennis matches in addition to the standard elements and

attributes.

XML example message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413357074374

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

gamescore

=

"

0:0

"

matchid

=

"

6243888

"

msgnr

=

"

13

"

server

=

"

1

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1set

"

tiebreak

=

"

false

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match server Which player has the serve at that 1 = player one

moment. This is an optional at- 2 = player two.

tribute and will be set once the first

server is known.

gamescore The point score in the current String

game. If one player has advantage Example: "15:40"

the score will be 50:40 or 40:50.

This attribute is also used for the

tiebreak score when the game is in

a tiebreak.

This attribute needs to be enabled

in the XML configuration, for more

information see chapter 6.22.2.3.

tiebreak Whether a match is in a tiebreak. Set to "true" if the match is in a

This attribute needs to be enabled tiebreak.

in the XML configuration, for more

information see chapter 6.22.2.2.

6.22.2 XML configuration

Sport specific XML configurations

6.22.2.1(ID: 6) Multiple bets of same type active at once for tennis matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.22.2.2(ID: 2) Include tennis tie-break status

Enabling this setting will add an attribute tiebreak to the Match element for tennis matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413357074374

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

6243888

"

msgnr

=

"

13

"

server

=

"

1

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1set

"

tiebreak

=

"

false

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match tiebreak Whether a match is in a tiebreak. String

"true" = Match is in tiebreak

"false" = Match is not in tiebreak

6.22.2.3(ID: 1) Include tennis point by point score

Enabling this setting will add an attribute gamescore to the Match element for tennis matches.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1413357074374

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

6243888

"

msgnr

=

"

13

"

server

=

"

1

"

gamescore

=

"

0:0

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1set

"

/>

</

BetbalancerLiveOdds

>

XML attributes definition

Element Attributes

Attribute Description Possible values

Match gamescore The point score in the current String

game. If one player has advantage Example: "15:40"

the score will be 50:40 or 40:50.

This attribute is also used for the

tiebreak score when the game is in

a tiebreak.

6.22.2.4(ID: 108) Include tennis markets for games which might not be played

Enabling this setting will include markets for games which will not be played (e.g. the 7th game if the setscore is already 5:0) in the

feed.

6.22.2.5(ID: 128) Include competitors pr team in meta messages

If enabled, meta messages for Tennis doubles matches will include additional information about individual players.

XML example

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1489592713569

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

11257013

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1489592925481

</

DateOfMatch

>

<

Sport

id

=

"

5

"

>

Tennis

</

Sport

>

<

Category

id

=

"

6

"

>

WTA

</

Category

>

<

Tournament

id

=

"

57144

"

>

Indian Wells, USA, Doubles

</

Tournament

>

<

HomeTeam

id

=

"

7057978

"

uniqueid

=

"

138370

"

>

HRADECKA L / SINIAKOVA K

</

HomeTeam

>

<

AwayTeam

id

=

"

9547077

"

uniqueid

=

"

320177

"

>

ARRUABARRENA L / LIANG C

</

AwayTeam

>

<

HomeCompetitors

>

<

Team

id

=

"

541426

"

uniqueid

=

"

19331

"

>

HRADECKA, LUCIE

</

Team

>

<

Team

id

=

"

6226593

"

uniqueid

=

"

72376

"

>

SINIAKOVA, KATERINA

</

Team

>

</

HomeCompetitors

>

<

AwayCompetitors

>

<

Team

id

=

"

5395461

"

uniqueid

=

"

46448

"

>

ARRUABARRENA-VECINO, LARA

</

Team

>

<

Team

id

=

"

1122536

"

uniqueid

=

"

49884

"

>

LIANG, CHEN

</

Team

>

</

AwayCompetitors

>

<

TvChannels

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

6.22.3 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

8 1set 1st set

9 2set 2nd set

10 3set 3rd set

11 4set 4th set

12 5set 5th set

100 ended The match has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

6.23 Volleyball

Sport specific information for Volleyball.

6.23.1 XML configuration

Sport specific XML configurations

6.23.1.1(ID: 32) Multiple bets of same type active at once for volleyball matches

The Live Odds system selects the most balanced bet (line, spread, etc) out of all available ones for each market, and only this one will

be sent out to the client system. Enabling this setting will allow multiple bets of the same type to be sent out at once, not only the

most balanced ones. E.g. for the total market in soccer the most balanced line would be 2.5. When enabling the setting, total 1.5 and

3.5 would be sent as well.

6.23.2 Match statuses

Id Status Status description Additional information

0 not_started Not started yet

8 1set 1st set

301 pause1 1st pause

9 2set 2nd set

302 pause2 2nd pause

10 3set 3rd set

303 pause3 3rd pause

11 4set 4th set

304 pause4 4th pause

12 5set 5th set

305 pause5 5th pause

441 6set 6th set

306 pause6 6th pause

442 7set 7th set

100 ended The match has ended

37 awaiting_gset Waiting for the golden set

17 gset Used if there is a golden set

130 after_gset Golden set has ended

93 walkover The home team won the match by Status controlled by XML configuration. For more informa-

walkover1 walkover tion, see chapter 5.1.1.15

94 walkover The away team won the match by Status controlled by XML configuration. For more informa-

walkover2 walkover tion, see chapter 5.1.1.15

95 retired The away team won because the Status controlled by XML configuration. For more informa-

retired1 home team retired tion, see chapter 5.1.1.15

96 retired The home team won because the Status controlled by XML configuration. For more informa-

retired2 away team retired tion, see chapter 5.1.1.15

61 delayed The match start is delayed

80 interrupted The match has been interrupted

90 abandoned The match has been abandoned Status controlled by XML configuration. For more informa-

tion, see chapter 5.1.1.16

7. Overview XML examples

7 Overview XML examples

The following section of the documentation lists all the most important XML examples for the Live odds product.

7.1 Login

All XML examples for Login

7.1.1 Request

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

login

"

bookmakerid

=

"

24

"

key

=

"

1

"

>

</

BookmakerStatus

>

7.1.2 Response

<

BetbalancerLiveOdds

status

=

"

loginok

"

timestamp

=

"

1184145289891

"

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

/>

7.2 Error and current

All XML examples for Error and current

7.2.1 Request

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

error

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

error

"

bookmakerid

=

"

24

"

msgnr

=

"

36

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

error

"

bookmakerid

=

"

24

"

msgfrom

=

"

12

"

msgto

=

"

15

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

<

BookmakerStatus

timestamp

=

"

0

"

type

=

"

current

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.2.2 Response

7.2.2.1 Error response

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

error

"

status

=

"

replystart

"

timestamp

=

"

1260866252519

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

current

"

status

=

"

change

"

timestamp

=

"

1260866108600

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

12

"

score

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

247507

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.1

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

13.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

8.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

247512

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.04

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

8.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

247510

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.1

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

7.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

17.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247508

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

2.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

247509

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247511

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.1

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.5

</

OddsField

>

</

Odds

>

</

Match

>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

current

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1260866108600

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

12

"

score

=

"

0:0

"

status

=

"

1p

"

/>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

current

"

status

=

"

clearbet

"

time

=

"

517

"

timestamp

=

"

1260866108600

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

0:0

"

matchid

=

"

935448

"

matchtime

=

"

1

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

247509

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

1

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

2

"

/>

</

Odds

>

</

Match

>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

error

"

status

=

"

change

"

timestamp

=

"

1260866162214

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

12

"

msgnr

=

"

18

"

score

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

247507

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

12.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

7.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

247512

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.04

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

8.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

247510

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247508

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

2.3

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

247509

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247511

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.5

</

OddsField

>

</

Odds

>

</

Match

>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

error

"

status

=

"

change

"

timestamp

=

"

1260866222211

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

12

"

msgnr

=

"

19

"

score

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

247507

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

12.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

7.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

247512

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.04

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

8.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

247510

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247508

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

2.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

247509

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247511

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.25

</

OddsField

>

</

Odds

>

</

Match

>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

3

"

replytype

=

"

error

"

status

=

"

replyend

"

timestamp

=

"

1260866252767

"

/>

7.2.2.2 Current response

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

4

"

replytype

=

"

current

"

status

=

"

replystart

"

timestamp

=

"

1260866431047

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

4

"

replytype

=

"

current

"

status

=

"

change

"

timestamp

=

"

1260866431052

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

15

"

score

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

247507

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

12.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

7.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

247512

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.04

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

8.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

247510

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247508

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

2.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

247509

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

247511

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.12

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

16.0

</

OddsField

>

</

Odds

>

</

Match

>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

4

"

replytype

=

"

current

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1260866431052

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

15

"

score

=

"

0:0

"

status

=

"

1p

"

/>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

4

"

replytype

=

"

current

"

status

=

"

clearbet

"

time

=

"

840

"

timestamp

=

"

1260866431052

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

0:0

"

matchid

=

"

935448

"

matchtime

=

"

1

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

247509

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

1

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

2

"

/>

</

Odds

>

</

Match

>

<

BetbalancerLiveOdds

>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

4

"

replytype

=

"

current

"

status

=

"

replyend

"

timestamp

=

"

1260866431106

"

/>

7.3 Register and unregistered for a match

All XML examples for registered and unregistered matches.

7.3.1 Request

Different Request XML examples.

7.3.1.1 Register request

Listing 1: Register

<

BookmakerStatus

timestamp

=

"

1193658786746

"

type

=

"

register

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.3.1.2 Unregister request

Listing 2: Unregister

<

BookmakerStatus

timestamp

=

"

1193658786746

"

type

=

"

unregister

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.3.2 Response

All response related XML examples.

7.3.2.1 Register response

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

register

"

status

=

"

meta

"

timestamp

=

"

1275050982039

"

>

<

Match

active

=

"

1

"

matchid

=

"

935448

"

status

=

"

1p

"

>

<

MatchInfo

>

<

DateOfMatch

>

1275051158000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

94

"

>

Norway Amateur

</

Category

>

<

Tournament

id

=

"

5956

"

>

4 Division, Trondelag avd 04

</

Tournament

>

<

HomeTeam

id

=

"

773839

"

>

TVEDESTRAND

</

HomeTeam

>

<

AwayTeam

id

=

"

1013871

"

>

NAMDALSEID

</

AwayTeam

>

<

TvChannels

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.4 Score and card summary

All Score and card summary XML examples.

7.4.1 Request

<

BookmakerStatus

type

=

"

scoreandcardsummary

"

timestamp

=

"

0

"

bookmakerid

=

"

1240

"

>

<

Match

matchid

=

"

1355389

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.4.2 Response

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

1

"

replytype

=

"

scoreandcardsummary

"

status

=

"

score

"

timestamp

=

"

1277801191793

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1355389

"

score

=

"

3:0

"

status

=

"

ended

"

>

<

Card

id

=

"

111556

"

player

=

"

Ramires

"

team

=

"

home

"

time

=

"

70

"

type

=

"

yellow

"

/>

<

Score

away

=

"

0

"

home

=

"

3

"

id

=

"

111554

"

player

=

"

scoringteam

=

"

home

"

time

=

"

59

"

type

=

"

score

"

/>

<

Card

id

=

"

111555

"

player

=

"

Fuentes, Ismael

"

team

=

"

away

"

time

=

"

67

"

type

=

"

yellow

"

/>

<

Score

away

=

"

0

"

home

=

"

2

"

time

=

"

45

"

type

=

"

ht

"

/>

<

Score

away

=

"

0

"

home

=

"

3

"

time

=

"

90

"

type

=

"

ft

"

/>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

111551

"

player

=

"

scoringteam

=

"

home

"

time

=

"

35

"

type

=

"

score

"

/>

<

Score

away

=

"

0

"

home

=

"

2

"

id

=

"

111552

"

player

=

"

scoringteam

=

"

home

"

time

=

"

38

"

type

=

"

score

"

/>

<

Card

id

=

"

111557

"

player

=

"

Millar, Rodrigo

"

team

=

"

away

"

time

=

"

79

"

type

=

"

yellow

"

/>

<

Card

id

=

"

111550

"

player

=

"

Kaka

"

team

=

"

home

"

time

=

"

29

"

type

=

"

yellow

"

/>

<

Card

id

=

"

111553

"

player

=

"

Vidal, Arturo

"

team

=

"

away

"

time

=

"

46

"

type

=

"

yellow

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.4.3 Response with Player ID XML configuration enabled

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

1

"

replytype

=

"

scoreandcardsummary

"

status

=

"

score

"

timestamp

=

"

1277801191793

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

1355389

"

score

=

"

3:0

"

status

=

"

ended

"

>

<

Card

id

=

"

105609

"

player

=

"

Docherty

"

playerid

=

"

115622

"

team

=

"

home

"

time

=

"

1

"

type

=

"

red

"

/>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

105611

"

player

=

"

S.Lowry

"

playerid

=

"

77988

"

scoringteam

=

"

home

"

time

=

"

3

"

type

=

"

score

"

/>

<

Score

away

=

"

1

"

home

=

"

1

"

id

=

"

105619

"

player

=

"

R.Glendinning

"

playerid

=

"

115631

"

scoringteam

=

"

away

"

time

=

"

21

"

type

=

"

score

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.5 Register and unregister for a bet type in match

All XML examples for register and unregister for a bet type in match.

7.5.1 Register

Listing 3: Register

<

BookmakerStatus

timestamp

=

"

1193658786746

"

type

=

"

register

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

>

<

Odds

active

=

"

1

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

1

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BookmakerStatus

>

7.5.2 Unregister

Listing 4: Unregister

<

BookmakerStatus

timestamp

=

"

1193658786746

"

type

=

"

unregister

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

661373

"

active

=

"

1

"

>

<

Odds

active

=

"

1

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

1

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BookmakerStatus

>

7.6 Meta requests

XML examples for meta requests.

7.6.1 All matches the next 7 days

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

/>

7.6.2 Meta for one match

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

568263

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.6.3 Meta for several matches

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

588101

"

active

=

"

1

"

/>

<

Match

matchid

=

"

524577

"

active

=

"

1

"

/>

<

Match

matchid

=

"

516557

"

active

=

"

1

"

/>

<

Match

matchid

=

"

568263

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.6.4 Meta for matches in an interval

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

metafrom

=

"

1190370195000

"

metato

=

"

1190391831000

"

/>

7.6.5 Meta with specified languages

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

1246

"

languages

=

"

en,nl

"

/>

7.6.6 Meta with include available matches

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

includeavailable

=

"

true

"

/>

7.7 Meta response

<

BetbalancerLiveOdds

status

=

"

meta

"

timestamp

=

"

1184145290125

"

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

>

<

Match

active

=

"

1

"

matchid

=

"

500581

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1184175000000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

17

"

>

Austria

</

Category

>

<

Tournament

id

=

"

29

"

>

T-Mobile Bundesliga

</

Tournament

>

<

HomeTeam

id

=

"

6589

"

uniqueid

=

"

2051

"

>

SK PUNTIGAMER STURM GRAZ

</

HomeTeam

>

<

AwayTeam

id

=

"

6597

"

uniqueid

=

"

2203

"

>

FK AUSTRIA MAGNA

</

AwayTeam

>

<

TvChannels

>

<

TvChannel

>

PREMIERE Austria

</

TvChannel

>

<

TvChannel

>

PREMIERE SPORT PORTAL

</

TvChannel

>

</

TvChannels

>

<

Streaming

>

<

Channel

id

=

"

1

"

>

Live Channel

</

Channel

>

</

Streaming

>

</

MatchInfo

>

</

Match

>

<

Match

active

=

"

1

"

matchid

=

"

505484

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1184324400000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

393

"

>

International Clubs

</

Category

>

<

Tournament

id

=

"

6342

"

>

Peace Cup Group B

</

Tournament

>

<

HomeTeam

id

=

"

121685

"

uniqueid

=

"

28

"

>

READING FC

</

HomeTeam

>

<

AwayTeam

id

=

"

122958

"

uniqueid

=

"

3211

"

>

RIVER PLATE

</

AwayTeam

>

<

TvChannels

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.7.1 Meta response with translation

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1394788377983

"

>

<

Match

active

=

"

1

"

booked

=

"

0

"

matchid

=

"

1271072

"

sourceid

=

"

status

=

"

1q

"

>

<

MatchInfo

>

<

DateOfMatch

>

1394787895000

</

DateOfMatch

>

<

Sport

id

=

"

20

"

>

Table tennis

</

Sport

>

<

Category

id

=

"

3

"

>

ATP

</

Category

>

<

Tournament

id

=

"

18953

"

>

Miami, USA

</

Tournament

>

<

HomeTeam

id

=

"

4783

"

uniqueid

=

"

1764

"

>

AIK

</

HomeTeam

>

<

AwayTeam

id

=

"

5259

"

uniqueid

=

"

1786

"

>

GAIS G

Ö

TEBORG

</

AwayTeam

>

<

TvChannels

>

<

TvChannel

>

Scout

</

TvChannel

>

</

TvChannels

>

<

ExtraInfo

>

<

Info

type

=

"

NumberOfSets

"

>

7

</

Info

>

</

ExtraInfo

>

<

Streaming

/>

</

MatchInfo

>

<

Translation

>

<

Sport

id

=

"

20

"

>

<

Name

lang

=

"

en

"

>

Table tennis

</

Name

>

<

Name

lang

=

"

nl

"

>

Tafel Tennis

</

Name

>

</

Sport

>

<

Category

id

=

"

3

"

>

<

Name

lang

=

"

en

"

>

ATP

</

Name

>

<

Name

lang

=

"

nl

"

>

ATP

</

Name

>

</

Category

>

<

Tournament

id

=

"

18953

"

>

<

Name

lang

=

"

en

"

>

Miami, USA

</

Name

>

<

Name

lang

=

"

nl

"

>

Miami, USA

</

Name

>

</

Tournament

>

<

HomeTeam

id

=

"

4783

"

uniqueid

=

"

1764

"

>

<

Name

lang

=

"

en

"

>

AIK Stockholm

</

Name

>

<

Name

lang

=

"

nl

"

>

AIK Stockholm

</

Name

>

</

HomeTeam

>

<

AwayTeam

id

=

"

5259

"

uniqueid

=

"

1786

"

>

<

Name

lang

=

"

en

"

>

GAIS

</

Name

>

<

Name

lang

=

"

nl

"

>

GAIS

</

Name

>

</

AwayTeam

>

</

Translation

>

</

Match

>

</

BetbalancerLiveOdds

>

7.7.2 Meta response with not booked matches

<

BetbalancerLiveOdds

status

=

"

meta

"

timestamp

=

"

1184145290125

"

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

>

<

Match

active

=

"

1

"

booked

=

"

0

"

matchid

=

"

500581

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1184175000000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

17

"

>

Austria

</

Category

>

<

Tournament

id

=

"

29

"

>

T-Mobile Bundesliga

</

Tournament

>

<

HomeTeam

id

=

"

6589

"

uniqueid

=

"

2051

"

>

SK PUNTIGAMER STURM GRAZ

</

HomeTeam

>

<

AwayTeam

id

=

"

6597

"

uniqueid

=

"

2203

"

>

FK AUSTRIA MAGNA

</

AwayTeam

>

<

TvChannels

>

<

TvChannel

>

PREMIERE Austria

</

TvChannel

>

<

TvChannel

>

PREMIERE SPORT PORTAL

</

TvChannel

>

</

TvChannels

>

</

MatchInfo

>

</

Match

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

505484

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1184324400000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

393

"

>

International Clubs

</

Category

>

<

Tournament

id

=

"

6342

"

>

Peace Cup Group B

</

Tournament

>

<

HomeTeam

id

=

"

121685

"

uniqueid

=

"

28

"

>

READING FC

</

HomeTeam

>

<

AwayTeam

id

=

"

122958

"

uniqueid

=

"

3211

"

>

RIVER PLATE

</

AwayTeam

>

<

TvChannels

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.7.3 Meta response with coverage information

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

PeriodLength

"

>

45

</

Info

>

<

Info

type

=

"

OvertimeLength

"

>

15

</

Info

>

</

ExtraInfo

>

<

Streaming

/>

<

CoverageInfo

>

<

Type

id

=

"

1

"

>

Extended markets

</

Type

>

</

CoverageInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.7.4 Meta response with extrainfo

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

PeriodLength

"

>

45

</

Info

>

<

Info

type

=

"

OvertimeLength

"

>

15

</

Info

>

</

ExtraInfo

>

<

Streaming

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.7.5 Meta response for Auto-traded Live Odds match

<

Match

status

=

"

not_started

"

matchid

=

"

956

"

booked

=

"

1

"

autotraded

=

"

1

"

active

=

"

1

"

>

<

MatchInfo

>

<

DateOfMatch

>

1415016577000

</

DateOfMatch

>

<

Sport

id

=

"

5

"

>

Tennis

</

Sport

>

<

Category

id

=

"

3

"

>

ATP

</

Category

>

<

Tournament

id

=

"

568

"

>

Paris TMS, France

</

Tournament

>

<

HomeTeam

uniqueid

=

"

14321

"

id

=

"

11403

"

>

AGASSI, ANDRE

</

HomeTeam

>

<

AwayTeam

uniqueid

=

"

14329

"

id

=

"

11749

"

>

GAUDIO, GASTON

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

NumberOfSets

"

>

5

</

Info

>

<

Info

type

=

"

AdvantageRule

"

>

yes

</

Info

>

<

Info

type

=

"

MatchTieBreakSet

"

>

no

</

Info

>

</

ExtraInfo

>

<

Streaming

/>

<

CoverageInfo

/>

</

MatchInfo

>

<

Translation

>

<

Sport

id

=

"

5

"

>

<

Name

lang

=

"

en

"

>

Tennis

</

Name

>

</

Sport

>

<

Category

id

=

"

3

"

>

<

Name

lang

=

"

en

"

>

ATP

</

Name

>

</

Category

>

<

Tournament

id

=

"

568

"

>

<

Name

lang

=

"

en

"

>

Paris TMS, France

</

Name

>

</

Tournament

>

<

HomeTeam

uniqueid

=

"

14321

"

id

=

"

11403

"

>

<

Name

lang

=

"

en

"

>

Agassi, Andre

</

Name

>

</

HomeTeam

>

<

AwayTeam

uniqueid

=

"

14329

"

id

=

"

11749

"

>

<

Name

lang

=

"

en

"

>

Gaudio, Gaston

</

Name

>

</

AwayTeam

>

</

Translation

>

</

Match

>

7.7.6 Meta response with streaming information

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1405677142338

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

4972075

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

CoverageInfo

/>

<

DateOfMatch

>

1405677600000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

5

"

>

Norway

</

Category

>

<

Tournament

id

=

"

5

"

>

Eliteserien

</

Tournament

>

<

HomeTeam

id

=

"

5020

"

uniqueid

=

"

1161

"

>

ROSENBORG BK

</

HomeTeam

>

<

AwayTeam

id

=

"

5293699

"

uniqueid

=

"

678

"

>

H

Ø

NEFOSS BK

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

PeriodLength

"

>

45

</

Info

>

<

Info

type

=

"

OvertimeLength

"

>

15

</

Info

>

</

ExtraInfo

>

<

Streaming

>

<

Channel

id

=

"

1

"

>

Live Channel Retail LIVE Match

</

Channel

>

<

Channel

id

=

"

2

"

>

Live Channel Retail LIVE Visualisation

</

Channel

>

<

Channel

id

=

"

3

"

>

Live Channel Online LIVE Match

</

Channel

>

<

Channel

id

=

"

4

"

>

Live Channel Online LIVE Visualisation

</

Channel

>

</

Streaming

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.7.7 Meta response for Tennis doubles match

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1489592713569

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

11257013

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1489592925481

</

DateOfMatch

>

<

Sport

id

=

"

5

"

>

Tennis

</

Sport

>

<

Category

id

=

"

6

"

>

WTA

</

Category

>

<

Tournament

id

=

"

57144

"

>

Indian Wells, USA, Doubles

</

Tournament

>

<

HomeTeam

id

=

"

7057978

"

uniqueid

=

"

138370

"

>

HRADECKA L / SINIAKOVA K

</

HomeTeam

>

<

AwayTeam

id

=

"

9547077

"

uniqueid

=

"

320177

"

>

ARRUABARRENA L / LIANG C

</

AwayTeam

>

<

HomeCompetitors

>

<

Team

id

=

"

541426

"

uniqueid

=

"

19331

"

>

HRADECKA, LUCIE

</

Team

>

<

Team

id

=

"

6226593

"

uniqueid

=

"

72376

"

>

SINIAKOVA, KATERINA

</

Team

>

</

HomeCompetitors

>

<

AwayCompetitors

>

<

Team

id

=

"

5395461

"

uniqueid

=

"

46448

"

>

ARRUABARRENA-VECINO, LARA

</

Team

>

<

Team

id

=

"

1122536

"

uniqueid

=

"

49884

"

>

LIANG, CHEN

</

Team

>

</

AwayCompetitors

>

<

TvChannels

/>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.8 Match booking request

<

BookmakerStatus

type

=

"

bookmatch

"

timestamp

=

"

0

"

bookmakerid

=

"

24

"

>

<

Match

matchid

=

"

1291016

"

active

=

"

1

"

/>

<

Match

matchid

=

"

1410019

"

active

=

"

1

"

/>

</

BookmakerStatus

>

7.9 Oddstype translation

All XML examples for oddstype translations.

7.9.1 Request

<

BookmakerStatus

type

=

"

gettranslation

"

bookmakerid

=

"

24

"

/>

<

BookmakerStatus

type

=

"

gettranslation

"

bookmakerid

=

"

24

"

languages

=

"

en,de,it

"

/>

7.9.2 Response

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

translation

"

timestamp

=

"

1268294133126

"

>

<

OddsType

type

=

"

3w

"

typeid

=

"

2

"

>

<

Name

lang

=

"

fi

"

>

1-X-2

</

Name

>

<

Name

lang

=

"

en

"

>

3w

</

Name

>

<

Name

lang

=

"

ru

"

>

3

è

ñ

õ

î

ä

à

</

Name

>

<

OddsField

type

=

"

1

"

>

<

Name

lang

=

"

fi

"

>

1

</

Name

>

<

Name

lang

=

"

en

"

>

1

</

Name

>

<

Name

lang

=

"

ru

"

>

1

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

x

"

>

<

Name

lang

=

"

fi

"

>

X

</

Name

>

<

Name

lang

=

"

en

"

>

x

</

Name

>

<

Name

lang

=

"

ru

"

>

Õ

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

2

"

>

<

Name

lang

=

"

fi

"

>

2

</

Name

>

<

Name

lang

=

"

en

"

>

2

</

Name

>

<

Name

lang

=

"

ru

"

>

2

</

Name

>

</

OddsField

>

</

OddsType

>

<

OddsType

type

=

"

hc

"

typeid

=

"

4

"

>

<

Name

lang

=

"

fi

"

>

Taaoitus

</

Name

>

<

Name

lang

=

"

en

"

>

hc

</

Name

>

<

Name

lang

=

"

ru

"

>

Ã

à

í

ä

è

ê

à

ï

</

Name

>

<

OddsField

type

=

"

1

"

>

<

Name

lang

=

"

fi

"

>

1

</

Name

>

<

Name

lang

=

"

en

"

>

1

</

Name

>

<

Name

lang

=

"

ru

"

>

1

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

x

"

>

<

Name

lang

=

"

fi

"

>

X

</

Name

>

<

Name

lang

=

"

en

"

>

x

</

Name

>

<

Name

lang

=

"

ru

"

>

Õ

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

2

"

>

<

Name

lang

=

"

fi

"

>

2

</

Name

>

<

Name

lang

=

"

en

"

>

2

</

Name

>

<

Name

lang

=

"

ru

"

>

2

</

Name

>

</

OddsField

>

</

OddsType

>

<

OddsType

type

=

"

to

"

typeid

=

"

5

"

>

<

Name

lang

=

"

fi

"

>

Yhteens

ä

</

Name

>

<

Name

lang

=

"

en

"

>

to

</

Name

>

<

Name

lang

=

"

ru

"

>

Ò

î

ò

à

ë

</

Name

>

<

OddsField

type

=

"

o

"

>

<

Name

lang

=

"

fi

"

>

o

</

Name

>

<

Name

lang

=

"

en

"

>

o

</

Name

>

<

Name

lang

=

"

ru

"

>

Á

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

u

"

>

<

Name

lang

=

"

fi

"

>

u

</

Name

>

<

Name

lang

=

"

en

"

>

u

</

Name

>

<

Name

lang

=

"

ru

"

>

Ì

</

Name

>

</

OddsField

>

</

OddsType

>

<

OddsType

freetext

=

"

Who wins the rest of the match?

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

Name

lang

=

"

fi

"

>

Kumpi voittaa loppuosan pelist

ä

?

</

Name

>

<

Name

lang

=

"

en

"

>

Who wins the rest of the match?

</

Name

>

<

Name

lang

=

"

ru

"

>

Ê

ò

î

â

û

è

ã

ð

à

å

ò

î

ñ

ò

à

ò

î

ê

ì

à

ò

oe

à

?

</

Name

>

<

OddsField

type

=

"

1

"

>

<

Name

lang

=

"

fi

"

>

1

</

Name

>

<

Name

lang

=

"

en

"

>

1

</

Name

>

<

Name

lang

=

"

ru

"

>

1

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

x

"

>

<

Name

lang

=

"

fi

"

>

X

</

Name

>

<

Name

lang

=

"

en

"

>

x

</

Name

>

<

Name

lang

=

"

ru

"

>

Õ

</

Name

>

</

OddsField

>

<

OddsField

type

=

"

2

"

>

<

Name

lang

=

"

fi

"

>

2

</

Name

>

<

Name

lang

=

"

en

"

>

2

</

Name

>

<

Name

lang

=

"

ru

"

>

2

</

Name

>

</

OddsField

>

</

OddsType

>

</

BetbalancerLiveOdds

>

7.10

7.11 Bet Start

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1199435558847

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

msgnr

=

"

5

"

score

=

"

-:-

"

status

=

"

not_started

"

/>

</

BetbalancerLiveOdds

>

7.12 Bet Stop

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstop

"

time

=

"

0

"

timestamp

=

"

1199435635925

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

6

"

score

=

"

-:-

"

status

=

"

not_started

"

/>

</

BetbalancerLiveOdds

>

7.12.1 Bet Stop reason

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstop

"

time

=

"

0

"

timestamp

=

"

1395803868428

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

betstopreason

=

"

DANGEROUS_FREE_KICK_HOME

"

betstopreasonid

=

"

18

"

cornersaway

=

"

2

"

cornershome

=

"

5

"

earlybetstatus

=

"

stopped

"

matchid

=

"

4885080

"

matchtime

=

"

55

"

matchtime_extended

=

"

54:11

"

msgnr

=

"

169

"

redcardsaway

=

"

0

"

redcardshome

=

"

0

"

score

=

"

1:1

"

setscores

=

"

1:1 - 0:0

"

status

=

"

2p

"

yellowcardsaway

=

"

1

"

yellowcardshome

=

"

0

"

yellowredcardsaway

=

"

0

"

yellowredcardshome

=

"

0

"

/>

</

BetbalancerLiveOdds

>

7.13 Early betstatus

This section shows how the attributes "betstatus" and "earlybetstatus" act if the configuration in chapter 6.19.2.4 is enabled.

7.13.1 Goal

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1395839596131

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

earlybetstatus

=

"

stopped

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10752

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

101058

"

player

=

"

scoringteam

=

"

home

"

time

=

"

1

"

type

=

"

live

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.13.2 Goal confirmed

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1395839596201

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

earlybetstatus

=

"

started

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10753

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

7.13.3 Kick off

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

betstart

"

time

=

"

0

"

timestamp

=

"

1395839620294

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

started

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10754

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

7.13.4 End of current cycle, beginning of new cycle

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1395839620340

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

earlybetstatus

=

"

stopped

"

matchid

=

"

1271072

"

matchtime

=

"

1

"

msgnr

=

"

10755

"

score

=

"

1:0

"

setscore1

=

"

1:0

"

status

=

"

1p

"

/>

</

BetbalancerLiveOdds

>

7.14 Odds change

Due to XML formatting the attribute type in the OddsField element may contain entity codes like < and > rather than the

actual characters < and >.

7.14.1 Soccer

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1267780727451

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

19

"

msgnr

=

"

17

"

score

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

325849

"

specialoddsvalue

=

"

0.75

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

325862

"

specialoddsvalue

=

"

2.0

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

325848

"

specialoddsvalue

=

"

2.75

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

325847

"

specialoddsvalue

=

"

2:0

"

type

=

"

hc

"

typeid

=

"

4

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

6.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

325860

"

specialoddsvalue

=

"

1.25

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - 3way

"

id

=

"

325846

"

specialoddsvalue

=

"

-1

"

subtype

=

"

22

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

8.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Odd/Even

"

id

=

"

325858

"

specialoddsvalue

=

"

-1

"

subtype

=

"

31

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

odd

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

even

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

325836

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

3.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

325850

"

specialoddsvalue

=

"

1.25

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

325851

"

specialoddsvalue

=

"

1:0

"

type

=

"

hc

"

typeid

=

"

4

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Goals home team

"

id

=

"

325857

"

specialoddsvalue

=

"

-1

"

subtype

=

"

28

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

1.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

9.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3+

"

>

25.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

325866

"

specialoddsvalue

=

"

1.75

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

325842

"

specialoddsvalue

=

"

1.0

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.95

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Goals away team

"

id

=

"

325854

"

specialoddsvalue

=

"

-1

"

subtype

=

"

32

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

4.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3+

"

>

4.6

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Goal/No goal

"

id

=

"

325855

"

specialoddsvalue

=

"

-1

"

subtype

=

"

30

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

goal

"

>

2.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

nogoal

"

>

1.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

325864

"

specialoddsvalue

=

"

1.0

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

3.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

325841

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

6.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.1

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Who wins the rest?

"

id

=

"

325853

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

20

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

8.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Double chance (1X - 12 - X2)

"

id

=

"

325845

"

specialoddsvalue

=

"

-1

"

subtype

=

"

27

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

1X

"

>

2.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

12

"

>

1.35

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

X2

"

>

1.12

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

325865

"

specialoddsvalue

=

"

3.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

325852

"

specialoddsvalue

=

"

1.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

2.3

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

325839

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

7.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Correct score

"

id

=

"

325856

"

specialoddsvalue

=

"

-1

"

subtype

=

"

26

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0:0

"

>

6.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:0

"

>

14.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:0

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:0

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:1

"

>

4.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:1

"

>

7.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:1

"

>

29.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:1

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:2

"

>

5.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:2

"

>

8.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:2

"

>

31.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:2

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:3

"

>

11.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:3

"

>

17.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:3

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:3

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

other

"

>

11.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

325859

"

specialoddsvalue

=

"

1.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

325868

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

325837

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

2.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

1.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

325843

"

specialoddsvalue

=

"

2.25

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.15

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

325844

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

325838

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

id

=

"

325861

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

325867

"

specialoddsvalue

=

"

0.75

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.1

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

325840

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

7.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

id

=

"

325863

"

specialoddsvalue

=

"

0.25

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.8

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.14.2 Tennis

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199777659034

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

666759

"

msgnr

=

"

73

"

score

=

"

0:1

"

setscores

=

"

1:6 -

2:1

"

status

=

"

2set

"

server

=

"

1

"

tiebreak

=

"

false

"

gamescore

=

"

15:30

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Which player will win the set?

"

id

=

"

14088

"

specialoddsvalue

=

"

2

"

subtype

=

"

11

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

5.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.1

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win the set?

"

id

=

"

14083

"

specialoddsvalue

=

"

1

"

subtype

=

"

11

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win games x and y of

set n?

"

id

=

"

14087

"

specialoddsvalue

=

"

2-1and2

"

subtype

=

"

12

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win games 1 and 2 of

set 1?

"

id

=

"

14084

"

specialoddsvalue

=

"

1-1and2

"

subtype

=

"

12

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win the match?

"

id

=

"

14082

"

specialoddsvalue

=

"

-1

"

subtype

=

"

10

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

5.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.1

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win games 3 and 4 of

set 1?

"

id

=

"

14085

"

specialoddsvalue

=

"

1-3and4

"

subtype

=

"

12

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win games 3 and 4 of

set 2?

"

id

=

"

14089

"

specialoddsvalue

=

"

2-3and4

"

subtype

=

"

12

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

99.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.18

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which player will win games 5 and 6 of

set 1?

"

id

=

"

14086

"

specialoddsvalue

=

"

1-5and6

"

subtype

=

"

12

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Final Result (in sets - best of 3)

"

id

=

"

14090

"

specialoddsvalue

=

"

-1

"

subtype

=

"

18

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

2:0

"

>

6.50

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:1

"

>

6.00

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:2

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:2

"

>

4.00

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.14.3 Ice Hockey

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1207727348919

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

743520

"

msgnr

=

"

54

"

score

=

"

2:1

"

setscores

=

"

1:0 -

1:1

"

status

=

"

3p

"

matchtime

=

"

43

"

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

26715

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who wins the period?

"

id

=

"

26716

"

specialoddsvalue

=

"

1

"

subtype

=

"

17

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who wins the period?

"

id

=

"

26722

"

specialoddsvalue

=

"

2

"

subtype

=

"

17

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who wins the period?

"

id

=

"

26769

"

specialoddsvalue

=

"

3

"

subtype

=

"

17

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

26717

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

7.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

26718

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.08

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

5.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

26770

"

specialoddsvalue

=

"

3.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.06

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

6.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

26719

"

specialoddsvalue

=

"

1:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

26721

"

specialoddsvalue

=

"

2:1

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.1

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

26720

"

specialoddsvalue

=

"

2:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.14.4 Basketball

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1287056116518

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

clock_stopped

=

"

0

"

matchid

=

"

1467300

"

matchtime

=

"

32

"

msgnr

=

"

31

"

remaining_time

=

"

8:49

"

score

=

"

13:10

"

setscores

=

"

0:0 - 5:5 - 3:5

"

status

=

"

4q

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

748814

"

specialoddsvalue

=

"

-3.5

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

748905

"

specialoddsvalue

=

"

87.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap for fourth period

"

id

=

"

748888

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

54

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Odd/Even for first half

"

id

=

"

748823

"

specialoddsvalue

=

"

-1

"

subtype

=

"

62

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

748810

"

specialoddsvalue

=

"

149.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

748864

"

specialoddsvalue

=

"

-4.5

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap for third period

"

id

=

"

748885

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

51

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet for first period

"

id

=

"

748804

"

specialoddsvalue

=

"

-1

"

subtype

=

"

41

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

id

=

"

748833

"

specialoddsvalue

=

"

-0.5

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian handicap for whole match,

including overtime

"

id

=

"

748867

"

specialoddsvalue

=

"

-4.5

"

subtype

=

"

38

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total for fourth period

"

id

=

"

748908

"

specialoddsvalue

=

"

67.5

"

subtype

=

"

53

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Odd/Even for fourth period

"

id

=

"

748887

"

specialoddsvalue

=

"

-1

"

subtype

=

"

60

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

odd

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

even

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team wins race to X points

"

id

=

"

748815

"

specialoddsvalue

=

"

40

"

subtype

=

"

66

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.55

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw no Bet for fourth period

"

id

=

"

748889

"

specialoddsvalue

=

"

-1

"

subtype

=

"

52

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.3

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.14.5 Handball

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1294145922310

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clock_stopped

=

"

0

"

matchid

=

"

1533390

"

matchtime

=

"

20

"

msgnr

=

"

32

"

score

=

"

2:3

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Odd/Even for first half

"

id

=

"

991423

"

specialoddsvalue

=

"

-1

"

subtype

=

"

62

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

odd

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

even

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

991476

"

specialoddsvalue

=

"

1:0

"

type

=

"

hc

"

typeid

=

"

4

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

10.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

991441

"

specialoddsvalue

=

"

19.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Handicap for first half

"

id

=

"

991478

"

specialoddsvalue

=

"

1:0

"

subtype

=

"

101

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

991452

"

specialoddsvalue

=

"

43.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team wins race to X points

"

id

=

"

991417

"

specialoddsvalue

=

"

15.0

"

subtype

=

"

66

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who scores Xth point

"

id

=

"

991471

"

specialoddsvalue

=

"

10.0

"

subtype

=

"

64

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.85

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Winning margins, handball

"

id

=

"

991431

"

specialoddsvalue

=

"

-1

"

subtype

=

"

82

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

HT > 10

"

>

35.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

HT 6-10

"

>

7.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

HT 1-5

"

>

2.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

Draw

"

>

6.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

AT 1-5

"

>

3.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

AT 6-10

"

>

11.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

AT > 10

"

>

35.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

991450

"

specialoddsvalue

=

"

15.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

991472

"

specialoddsvalue

=

"

44.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

991477

"

specialoddsvalue

=

"

-0.5

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

id

=

"

991479

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

991412

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.35

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.15 Bet clearing

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

clearbet

"

time

=

"

1

"

timestamp

=

"

1199435884237

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

1:0

"

matchid

=

"

661373

"

matchtime

=

"

4

"

msgnr

=

"

21

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13786

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

1

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

x

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

2

"

/>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.15.1 Bet clearing with voidfactor

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

clearbet

"

time

=

"

2

"

timestamp

=

"

1266483496355

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

0:1

"

matchid

=

"

935448

"

msgnr

=

"

19

"

status

=

"

paused

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

311538

"

specialoddsvalue

=

"

1.25

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

under

"

voidfactor

=

"

0.5

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

over

"

voidfactor

=

"

0.5

"

/>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.16 Rollback of bet clearing

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

rollback

"

time

=

"

17

"

timestamp

=

"

1199436168440

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clearedscore

=

"

2:0

"

matchid

=

"

661373

"

matchtime

=

"

9

"

msgnr

=

"

45

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13790

"

specialoddsvalue

=

"

1:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

outcome

=

"

1

"

type

=

"

1

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

x

"

/>

<

OddsField

active

=

"

1

"

outcome

=

"

0

"

type

=

"

2

"

/>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.17 Cancellation of bet

XML examples when cancellation of bets occur.

7.17.1 Entire bet type canceled

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

cancelbet

"

timestamp

=

"

1199436169018

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

matchtime

=

"

9

"

msgnr

=

"

46

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13792

"

specialoddsvalue

=

"

2:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.17.2 Bet type cancelled for a period:

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

endtime

=

"

1199436022222

"

starttime

=

"

1199435902000

"

status

=

"

cancelbet

"

timestamp

=

"

1199436037753

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

matchtime

=

"

7

"

msgnr

=

"

33

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13790

"

specialoddsvalue

=

"

1:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.18 Undo cancellation of bet

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

undocancelbet

"

timestamp

=

"

1199783156940

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

49

"

status

=

"

not_started

"

>

<

Odds

active

=

"

1

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

13792

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.19 Message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1199783362456

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

2

"

score

=

"

-:-

"

status

=

"

not_started

"

>

<

Message

>

Game cancelled: No TV coverage

</

Message

>

</

Match

>

</

BetbalancerLiveOdds

>

7.19.1 Failed bookmatch request

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

error

"

timestamp

=

"

1408607816955

"

>

<

Match

active

=

"

0

"

booked

=

"

0

"

matchid

=

"

1171785

"

status

=

"

not_started

"

/>

<

Message

>

Cannot book matchid: 1171785. This match is not offered within our live betting services,

only LCoO services

</

Message

>

</

BetbalancerLiveOdds

>

7.20 Score change

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1199435937143

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

matchtime

=

"

5

"

msgnr

=

"

29

"

score

=

"

1:0

"

status

=

"

1p

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

7966

"

player

=

"

P. Anderson

"

scoringteam

=

"

home

"

time

=

"

4

"

type

=

"

live

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.21 Card given

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

cards

"

timestamp

=

"

1199436094472

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

661373

"

matchtime

=

"

8

"

msgnr

=

"

37

"

score

=

"

1:0

"

status

=

"

1p

"

>

<

Card

canceled

=

"

false

"

id

=

"

7967

"

player

=

"

P. Anderson

"

team

=

"

home

"

time

=

"

7

"

type

=

"

yellow

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.22 Score and card summary

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

score

"

timestamp

=

"

1199436663643

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

661373

"

msgnr

=

"

78

"

score

=

"

1:2

"

status

=

"

ended

"

>

<

Score

away

=

"

0

"

home

=

"

1

"

id

=

"

7966

"

player

=

"

P. Anderson

"

scoringteam

=

"

home

"

time

=

"

4

"

type

=

"

score

"

/>

<

Card

id

=

"

7967

"

player

=

"

P. Anderson

"

team

=

"

home

"

time

=

"

7

"

type

=

"

yellow

"

/>

<

Card

id

=

"

7965

"

player

=

"

A. Johnsen

"

team

=

"

away

"

time

=

"

4

"

type

=

"

yellow

"

/>

<

Score

away

=

"

1

"

home

=

"

1

"

id

=

"

7969

"

player

=

"

scoringteam

=

"

away

"

time

=

"

8

"

type

=

"

score

"

/>

<

Score

away

=

"

2

"

home

=

"

1

"

time

=

"

90

"

type

=

"

ft

"

/>

<

Score

away

=

"

2

"

home

=

"

1

"

id

=

"

7971

"

player

=

"

scoringteam

=

"

away

"

time

=

"

49

"

type

=

"

score

"

/>

<

Score

away

=

"

1

"

home

=

"

1

"

time

=

"

45

"

type

=

"

ht

"

/>

<

Card

id

=

"

7970

"

player

=

"

A. Johnsen

"

team

=

"

away

"

time

=

"

46

"

type

=

"

yellowred

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.23 Meta response with scout match

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1246446136921

"

>

<

Match

active

=

"

1

"

matchid

=

"

1072283

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1246983300000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

393

"

>

International Clubs

</

Category

>

<

Tournament

id

=

"

86

"

>

Club Friendly Games

</

Tournament

>

<

HomeTeam

id

=

"

556074

"

uniqueid

=

"

2458

"

>

FC WINTERTHUR

</

HomeTeam

>

<

AwayTeam

id

=

"

223569

"

uniqueid

=

"

2450

"

>

FC Z

Ü

RICH

</

AwayTeam

>

<

TvChannels

>

<

TvChannel

>

Scout

</

TvChannel

>

</

TvChannels

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.24 Odds change for scout match

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1246369631140

"

type

=

"

scoutmatch

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

1068869

"

msgnr

=

"

3

"

score

=

"

-:-

"

status

=

"

not_started

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

145191

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

9.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.7

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

145192

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

1.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Halftime - Who wins the rest?

"

id

=

"

146867

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

20

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.95

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

145194

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

146868

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

145193

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

145195

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.25

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.25 Irrelevant change message

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

irrelevantchange

"

timestamp

=

"

1287060653120

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

clock_stopped

=

"

0

"

matchid

=

"

1467300

"

msgnr

=

"

37

"

status

=

"

pause1

"

/>

</

BetbalancerLiveOdds

>

7.26 Riskadjustment notification

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replytype

=

"

riskadjustment_update

"

status

=

"

change

"

timestamp

=

"

1297685983108

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

935448

"

score

=

"

-:-

"

status

=

"

not_started

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

1001305

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

1001310

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.18

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.3

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Double chance (1X - 12 - X2)

"

id

=

"

1001311

"

specialoddsvalue

=

"

-1

"

subtype

=

"

27

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

1X

"

>

1.14

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

12

"

>

1.14

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

X2

"

>

2.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

1001308

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.6

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1001306

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

1001307

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1001309

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.6

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.27 Meta with extra sports information

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

meta

"

timestamp

=

"

1297842037407

"

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

935457

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1297840550000

</

DateOfMatch

>

<

Sport

id

=

"

5

"

>

Tennis

</

Sport

>

<

Category

id

=

"

3

"

>

ATP

</

Category

>

<

Tournament

id

=

"

7434

"

>

Medibank International, Sydney, Australia

</

Tournament

>

<

HomeTeam

id

=

"

225371

"

uniqueid

=

"

14645

"

>

GUCCIONE, CHRIS

</

HomeTeam

>

<

AwayTeam

id

=

"

11763

"

uniqueid

=

"

14362

"

>

MARTIN, ALBERTO

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

NumberOfSets

"

>

5

</

Info

>

</

ExtraInfo

>

</

MatchInfo

>

</

Match

>

<

Match

active

=

"

1

"

booked

=

"

1

"

matchid

=

"

935448

"

status

=

"

not_started

"

>

<

MatchInfo

>

<

DateOfMatch

>

1297840550000

</

DateOfMatch

>

<

Sport

id

=

"

1

"

>

Soccer

</

Sport

>

<

Category

id

=

"

94

"

>

Norway Amateur

</

Category

>

<

Tournament

id

=

"

5956

"

>

4 Division, Tr

ø

ndelag avd 04

</

Tournament

>

<

HomeTeam

id

=

"

773839

"

>

TVEDESTRAND

</

HomeTeam

>

<

AwayTeam

id

=

"

1013871

"

>

NAMDALSEID

</

AwayTeam

>

<

TvChannels

/>

<

ExtraInfo

>

<

Info

type

=

"

PeriodLength

"

>

45

</

Info

>

<

Info

type

=

"

OvertimeLength

"

>

15

</

Info

>

</

ExtraInfo

>

</

MatchInfo

>

</

Match

>

</

BetbalancerLiveOdds

>

7.28 Soccer match with setscores attribute

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1297687408708

"

>

<

Match

active

=

"

1

"

betstatus

=

"

stopped

"

matchid

=

"

935448

"

matchtime

=

"

65

"

msgnr

=

"

26

"

score

=

"

1:1

"

setscores

=

"

0:1 - 1:0

"

status

=

"

2p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

1001315

"

specialoddsvalue

=

"

1:1

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

6.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

1001310

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Double chance (1X - 12 - X2)

"

id

=

"

1001311

"

specialoddsvalue

=

"

-1

"

subtype

=

"

27

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

1X

"

>

1.07

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

12

"

>

1.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

X2

"

>

1.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1001309

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

6.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

1001314

"

specialoddsvalue

=

"

1:1

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.1

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

5.5

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.29 Odds change message with mostbalanced attribute

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1306135766774

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

matchid

=

"

935448

"

matchtime

=

"

11

"

msgnr

=

"

4

"

score

=

"

0:0

"

setscores

=

"

0:0

"

status

=

"

1p

"

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1458699

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

2.75

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.1

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1458703

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

2.0

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

1458684

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

10.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

1458689

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.6

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1458702

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

3.0

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Double chance (1X - 12 - X2)

"

id

=

"

1458698

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

27

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

1X

"

>

1.16

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

12

"

>

1.35

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

X2

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1458701

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

3.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

3.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

1.3

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1458700

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

1.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

1458687

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1458685

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1458697

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.25

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

1458686

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

true

"

combination

=

"

0

"

id

=

"

1458688

"

mostbalanced

=

"

1

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.95

</

OddsField

>

</

Odds

>

</

Match

>

</

BetbalancerLiveOdds

>

7.30 Message with splitted setscore attribute

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

alive

"

timestamp

=

"

1308561825332

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

gamescore

=

"

0:0

"

matchid

=

"

935457

"

msgnr

=

"

58

"

score

=

"

1:0

"

server

=

"

1

"

setscore1

=

"

6:3

"

setscore2

=

"

1:3

"

status

=

"

2set

"

tiebreak

=

"

false

"

/>

</

BetbalancerLiveOdds

>

7.31 Message with corner and card counters, and new corner and booking

markets

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

status

=

"

change

"

timestamp

=

"

1316688635427

"

>

<

Match

active

=

"

1

"

betstatus

=

"

started

"

cornersaway

=

"

0

"

cornershome

=

"

0

"

matchid

=

"

935448

"

matchtime

=

"

1

"

msgnr

=

"

7

"

redcardsaway

=

"

0

"

redcardshome

=

"

0

"

score

=

"

0:0

"

setscore1

=

"

0:0

"

status

=

"

1p

"

yellowcardsaway

=

"

0

"

yellowcardshome

=

"

0

"

yellowredcardsaway

=

"

0

"

yellowredcardshome

=

"

0

"

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Bookings

"

id

=

"

1478750

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

2.5

"

subtype

=

"

167

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

3.3

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Corner Handicap

"

id

=

"

1478699

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1.5

"

subtype

=

"

123

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners (aggregated)

"

id

=

"

1478755

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

127

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Corners

"

id

=

"

1478772

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

2.5

"

subtype

=

"

128

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1478756

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

2.0

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.55

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1478709

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

2.75

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Bookings Hometeam

"

id

=

"

1478704

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

171

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.7

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners awayteam

"

id

=

"

1478739

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

3.5

"

subtype

=

"

133

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

id

=

"

1478767

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-0.5

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.55

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Corners hometeam

"

id

=

"

1478774

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.5

"

subtype

=

"

136

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - 3way

"

id

=

"

1478708

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

22

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

5.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Corner Handicap

"

id

=

"

1478721

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

123

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total Bookings

"

id

=

"

1478724

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

3.5

"

subtype

=

"

153

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

3.1

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Odd/Even

"

id

=

"

1478742

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

31

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

odd

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

even

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Bookings

"

id

=

"

1478727

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

167

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

4.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.16

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Correct score flex

"

id

=

"

1478752

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

104

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0:0

"

>

10.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:0

"

>

7.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:0

"

>

7.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:0

"

>

14.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4:0

"

>

30.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

5:0

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

6:0

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:1

"

>

14.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:1

"

>

9.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:1

"

>

9.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:1

"

>

15.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4:1

"

>

38.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

5:1

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:2

"

>

26.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:2

"

>

19.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:2

"

>

25.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:2

"

>

40.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4:2

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:3

"

>

90.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:3

"

>

53.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:3

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:3

"

>

157.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:4

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:4

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:4

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:5

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:5

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:6

"

>

70.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Matchbet and Totals

"

id

=

"

1478762

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.5

"

subtype

=

"

183

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

home and under

"

>

3.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

draw and under

"

>

4.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

away and under

"

>

9.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

home and over

"

>

2.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

draw and over

"

>

23.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

away and over

"

>

9.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total Booking Points (aggregated)

"

id

=

"

1478747

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

165

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0-30

"

>

3.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

31-45

"

>

4.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

46-60

"

>

3.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

61-75

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

76+

"

>

8.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Next goal

"

id

=

"

1478689

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

13

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

10.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.85

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Sending off?

"

id

=

"

1478720

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

157

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

yes

"

>

3.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

no

"

>

1.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Corners Odd/Even

"

id

=

"

1478764

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

139

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

1478712

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

1.25

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Cornerbet

"

id

=

"

1478770

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

121

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Bookings (exactly)

"

id

=

"

1478705

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

169

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

4.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3

"

>

6.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4

"

>

13.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

5

"

>

39.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

6+

"

>

98.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478715

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

1:0

"

type

=

"

hc

"

typeid

=

"

4

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.18

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

10.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners

"

id

=

"

1478775

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

9.5

"

subtype

=

"

126

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Exact number of goals

"

id

=

"

1478753

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

141

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

2.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3

"

>

10.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4+

"

>

26.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Corners

"

id

=

"

1478738

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

4.5

"

subtype

=

"

128

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian handicap first half

"

id

=

"

1478710

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-0.25

"

subtype

=

"

36

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Goals home team

"

id

=

"

1478736

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

28

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

4.55

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

3.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.35

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3+

"

>

3.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Goals away team

"

id

=

"

1478734

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

32

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

2.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

5.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3+

"

>

13.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Corners

"

id

=

"

1478746

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

3.5

"

subtype

=

"

128

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Goal/No goal

"

id

=

"

1478735

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

30

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

goal

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

nogoal

"

>

1.6

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Next goal

"

id

=

"

1478706

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

107

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Cornerbet

"

id

=

"

1478765

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

120

"

type

=

"

ft3w

"

typeid

=

"

6

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners

"

id

=

"

1478758

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

8.5

"

subtype

=

"

126

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Exact number of goals

"

id

=

"

1478766

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

140

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

10.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

4.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.65

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3

"

>

4.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4

"

>

6.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

5

"

>

12.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

6+

"

>

18.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Booking Points

(aggregated)

"

id

=

"

1478711

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

177

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0-10

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

11-25

"

>

3.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

26-40

"

>

4.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

41+

"

>

16.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Corners Odd/Even

"

id

=

"

1478729

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

138

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Corner Handicap

"

id

=

"

1478757

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1.5

"

subtype

=

"

122

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total hometeam

"

id

=

"

1478703

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

1.5

"

subtype

=

"

142

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Bookings Awayteam

"

id

=

"

1478744

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

173

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.55

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total Booking Points

"

id

=

"

1478759

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

45.5

"

subtype

=

"

163

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

1478745

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1.0

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total first half

"

id

=

"

1478768

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

1.0

"

subtype

=

"

35

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.85

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.75

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

When will next goal be scored

"

id

=

"

1478714

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

118

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

min 01-15

"

>

3.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

min 16-30

"

>

3.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

min 31-45

"

>

5.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

min 46-60

"

>

8.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

min 61-75

"

>

12.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

min 76-90

"

>

18.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

no goal

"

>

10.5

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Corners awayteam

"

id

=

"

1478740

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

131

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total Bookings (excactly)

"

id

=

"

1478730

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

155

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

<4

"

>

3.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

4

"

>

4.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

5

"

>

4.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

6

"

>

6.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

7

"

>

9.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

8

"

>

15.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

9

"

>

32.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

10

"

>

72.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

11

"

>

183.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

12+

"

>

346.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Draw No Bet

"

id

=

"

1478694

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

16

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

3.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Who wins the rest?

"

id

=

"

1478733

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

20

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.2

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

2.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

5.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Corners (aggregated)

"

id

=

"

1478751

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

129

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478741

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

3.5

"

type

=

"

to

"

typeid

=

"

5

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total Bookings

"

id

=

"

1478737

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

5.5

"

subtype

=

"

153

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478716

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

1.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

3.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Double chance (1X - 12 - X2)

"

id

=

"

1478701

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

27

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

1X

"

>

1.18

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

12

"

>

1.18

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

X2

"

>

2.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Highest Scoring Half

"

id

=

"

1478773

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

119

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

first half

"

>

3.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

second half

"

>

2.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

equals

"

>

3.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Bookings Hometeam

"

id

=

"

1478695

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.5

"

subtype

=

"

159

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

2.25

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Goals awayteam

"

id

=

"

1478769

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

145

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

1.35

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

3.3

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

14.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3+

"

>

108.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Corners awayteam

"

id

=

"

1478754

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

1.5

"

subtype

=

"

137

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

1478743

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

1.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.4

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.6

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Corners hometeam

"

id

=

"

1478726

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

130

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Who wins the rest of the match?

"

id

=

"

1478692

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

4

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Bookings

"

id

=

"

1478749

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

1.5

"

subtype

=

"

167

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Correct score

"

id

=

"

1478731

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

26

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0:0

"

>

10.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:0

"

>

7.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:0

"

>

7.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:0

"

>

14.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:1

"

>

14.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:1

"

>

9.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:1

"

>

9.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:1

"

>

15.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:2

"

>

26.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:2

"

>

19.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:2

"

>

25.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:2

"

>

40.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:3

"

>

90.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:3

"

>

53.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:3

"

>

70.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:3

"

>

157.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

other

"

>

8.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Corners awayteam

"

id

=

"

1478698

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

135

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Corner Handicap

"

id

=

"

1478718

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-2.5

"

subtype

=

"

122

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478690

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.5

"

type

=

"

to

"

typeid

=

"

5

"

>

<

OddsField

active

=

"

1

"

type

=

"

o

"

>

1.9

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

u

"

>

1.7

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian total

"

id

=

"

1478700

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.25

"

subtype

=

"

33

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.15

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners hometeam

"

id

=

"

1478763

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

5.5

"

subtype

=

"

132

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total Bookings

"

id

=

"

1478760

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

4.5

"

subtype

=

"

153

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

1478725

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-0.5

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478719

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:1

"

type

=

"

hc

"

typeid

=

"

4

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

2.2

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Total Booking Points

"

id

=

"

1478761

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

15.5

"

subtype

=

"

175

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Halftime - Total

"

id

=

"

1478697

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

21

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.35

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Which team has kick off?

"

id

=

"

1478691

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-1

"

subtype

=

"

2

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Asian Handicap

"

id

=

"

1478771

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-0.75

"

subtype

=

"

34

"

type

=

"

ft2w

"

typeid

=

"

7

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.9

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Correct score first half flex

"

id

=

"

1478702

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0:0

"

subtype

=

"

29

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0:0

"

>

2.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:0

"

>

3.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:0

"

>

9.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3:0

"

>

39.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:1

"

>

7.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:1

"

>

9.25

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2:1

"

>

24.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:2

"

>

36.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1:2

"

>

44.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

0:3

"

>

296.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Bookingbet

"

id

=

"

1478748

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

149

"

type

=

"

ft3w

"

typeid

=

"

6

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.7

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.95

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478693

"

mostbalanced

=

"

1

"

type

=

"

3w

"

typeid

=

"

2

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

1.6

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

3.95

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

4.45

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Corners hometeam

"

id

=

"

1478707

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

134

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Bookings Awayteam

"

id

=

"

1478728

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

2.5

"

subtype

=

"

161

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

1.8

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.8

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

Total awayteam

"

id

=

"

1478696

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

0.5

"

subtype

=

"

143

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

under

"

>

2.05

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

over

"

>

1.65

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Corner Handicap

"

id

=

"

1478722

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

-0.5

"

subtype

=

"

122

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

id

=

"

1478732

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

0:2

"

type

=

"

hc

"

typeid

=

"

4

"

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

5.75

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

x

"

>

4.45

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

1.4

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

1st Half - Corner Handicap

"

id

=

"

1478723

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-0.5

"

subtype

=

"

123

"

type

=

"

ft2w

"

typeid

=

"

7

"

/>

<

Odds

active

=

"

1

"

changed

=

"

false

"

combination

=

"

0

"

freetext

=

"

1st Half - Goals hometeam

"

id

=

"

1478713

"

mostbalanced

=

"

1

"

specialoddsvalue

=

"

-1

"

subtype

=

"

144

"

type

=

"

ftnw

"

typeid

=

"

8

"

>

<

OddsField

active

=

"

1

"

type

=

"

0

"

>

2.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

1

"

>

2.5

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

2

"

>

6.0

</

OddsField

>

<

OddsField

active

=

"

1

"

type

=

"

3+

"

>

21.0

</

OddsField

>

</

Odds

>

<

Odds

active

=

"

0

"

changed

=

"

true

"

combination

=

"

0

"

freetext

=

"

Total Corners

"

id

=

"

1478717

"

mostbalanced

=

"

0

"

specialoddsvalue

=

"

7.5

"

subtype

=

"

126

"

type

=

"

ftnw

"

typeid

=

"

8

"

/>

</

Match

>

</

BetbalancerLiveOdds

>

7.32 Message with "Include response reply number in meta" active

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

requestnr

=

"

1234

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

1234

"

status

=

"

meta

"

timestamp

=

"

1400144969386

"

>

<

BookmakerStatus

type

=

"

meta

"

bookmakerid

=

"

24

"

/>

<

BetbalancerLiveOdds

xmlns

=

"

http://www.betbalancer.com/BetbalancerLiveOdds

"

replynr

=

"

2

"

status

=

"

meta

"

timestamp

=

"

1400146666680

"

>

Betbalancer Pre-Match Odds Integration Manual

Page

1 Introduction 1

1.1 Data Format 1

1.2 Access Methods 1

1.3 Complete File Check 1

1.4 Information about the XML feed 1

2 Starting Up the Service 2

2.1 Startup 2

3 Fixtures XML Feed 2

3.0.1 The Text element’s language attribute 2

3.1 Match Specification 3

3.1.1 Introduction 3

3.1.2 Details 5

3.1.3 Results 7

4 Outright Specification 10

4.1 Important considerations when using outrights 11

5 XML Element List 12

6 Appendix 17

6.1 Date Format 17

6.2 Language Specifiers 17

6.3 Odds types 17

6.3.1 Side bets Overview 17

6.4 Player 18

1

Introduction

Data Format

Data exports from Betbalancer come in XML format (extensible markup language). The purpose of the XML format is to describe sport

fixtures with odds, results and comments in a structured and consistent way to ease the process of importing the data into clients’ systems.

An important feature of the export is the exposure of the internal Betbalancer IDs allowing for synchronization between Betbalancer and

clients. The following sections in this document describe the XML format in detail. Note: All examples in this documentation use arbitrary

element and attribute values.

Access Methods

Betbalancer tries to be flexible and we do support several methods of data transfer:

Protocol

Description

HTTP

We support pull method using HTTP. This means that data can be collected from the queue using the supplied URL.

Complete File Check

If you are uncertain about whether you have received a full XML datafile, a simple initial check is to just look for the end tag:

</BetbalancerBetData>. This is the last data that is written to the file, so its presence should indicate that the whole file was received.

Information about the XML feed

The number of files sent each day and file size are dependent on the following factors:

• Active services ("Fixtures", "Fixtures & Results" or "Fixtures & Results & Odds suggestions")

• Number of Sports/Categories/Tournaments enabled in the configuration

• Number of languages activated

• Number of odds types activated

• General configuration of the XML feed

• Number of active tournaments (Time of year)

The highest possible number of files that can be sent in a day is 4320 (one every 20 seconds). The file size can vary from <1kB up to around

700kB on rare occasions.

Configuration

Sports Fixtures

It is possible to configure which sports, categories and tournaments you want to receive in this feed. You can do so from backoffice into the

prematch -> Market Settings Menu.

2

Starting Up the Service

Startup

Fixtures are normally sent out some days in advance. There are some exceptions to this for example for some special events and outrights

(such as the FIFA World Cup) we will send fixtures more than 30 days in advance. There are also instances where we have to send fixtures

less than 30 days in advance due to cup competition draws, no confirmed fixture details etc.

To start up and populate your db, please chech the API PDF where you can find some useful API to start get the needed data like the list of

sport, categories, tournaments team ids..

Fixtures XML Feed

Internally, the matches in Betbalancer are organized into a hierarchy of Sports, Categories and Tournaments. All Matches belong to a

tournament, which in turn belong in a category, which in turn belong to a sport. In addition to matches, we have Outrights, which fit in at

the category level. The structure of the XML file reflects this hierarchy:

Listing 11: Structure overview

<Sport>

Fixture data,

Odds data, Results,

comments

</Outright>

<Match>

Fixture data,

Odds data,

Results,

Comments,

Goals,

Cards,

Etc

</Match>

</Tournament>

</Category>

</Sport>

</Sports>

</BetbalancerBetData>

Each of the sport, category, tournament and match levels in the hierarchy are described using a Texts element, containing a textual

description of the element in all supported languages.

The Text element’s language attribute

For each Text element in the Texts block, the attribute Language specifies in which language the contained text is. If no Language attribute

is given, the language defaults to BET where team names are given by internal standards. For a full list see the Language Specifiers section.

An example of textual description in a Sport element with the Language attribute set:

Listing 12: Sport w/languages

<Value>Soccer</Value>

</Text>

<Value>Soccer</Value>

</Text>

3

<Value>Fussball</Value>

</Text>

<Value>Football</Value>

</Text>

<Value>Calcio</Value>

</Text>

</Texts> <Category>

...

</Category> </Sport>

A Sport element sample in which the Language attribute is omitted:

Listing 13: Sport no languages

<Text>

<Value>Soccer</Value>

</Text>

</Texts> <Category>

...

</Category> </Sport>

Match Specification

Introduction

• Fixture

• Information

• MatchOdds

• Result

• BetResult

• Cancelled Markets

• Goals

• Cards

4

A sample Match element:

Listing 14: Match Element

<Texts>

</Text>

</Texts>

<Texts>

<Value>FC SLOVACKO</Value>

</Text> </Texts>

</Competitors> <DateInfo>

</DateInfo>

</StatusInfo>

</HasStatistics>

</NeutralGround>

</Fixture>

</Bet>

</MatchOdds>

</ScoreInfo> <Comment>

<Texts>

<Text><Value>1:0(62.)Luis Fabiano</Value></Text>

</Texts>

</Comment> </Result>

<Goals>

</Goals>

<Cards>

</Card>

</Cards>

</Match>

Note, that in this case, no language was specified for the team names. In such cases, the language defaults to "BET", implicitly. The two

teams are designated as home and away team by the Type attribute of the Text element. In addition, they will be given a context-sensitive

team ID (valid within a certain tournament or cup). ID is an internal Betbalancer ids used to identify teams.

The DateInfo element contains info about match start date:

5

Listing 15: Date Info

</DateInfo>

Details

This section takes a closer look at all the various elements and attributes contained within the Match element. Overall structure of a Match:

Listing 18: Details

Match BetbalancerMatchID=*

−Fixture

−Competitors

−Texts

−Text Type=1,2 ID=* SUPERID=* Language=en,fr,..

−DateInfo

−MatchDate

−Value (Date)

−Statusinfo

−Off (0 or 1)

−NeutralGround

−Value (0 or 1)

−MatchOdds

−Bet Oddstype="01","02",..,"284","285"

−Odds OutCome="1","X",..,"Yes","No"

SpecialBetValue="1:0","0−1",..,"2,5","1,5"

−Result

−ScoreInfo

−Score Type="FT","HT",..,"Set4","Set5"

−Comment −Texts

−Text

−Value (Text)

−Goals

−Goal ID=* ScoringTeam="1","2" Team1="*" Team2="*" Time="*"

−Player ID=* Name=text

−Cards

CardID=* Time=* Type="Red", "Yellow", "YellowRed"

−"Player ID=* Name=text

−BetResult

−W OddsType="01","02",...,"284","285" OutCome="1","X",..,"Yes","No"

SpecialBetValue="1:0","0−1",..,"2,5","1,5"

Status="L","W"

VoidFactor="0.5","1.0" ,...

6

Fixture

• Competitors

• Home team is indicated with a Type="1" Away team is indicated with a Type="2".

Team ids are indicated with ID.

• DateInfo The date and time of the game

• StatusInfo If the match is called off before starting time, the Off element residing here will have the value "1". In such case match

needs to be removed from offer.

MatchOdds

can describe the following odds types, depending on the OddsType attribute:

• HandicapOdds

• Correct score odds

• 3-way odds (1,X,2)

• 2-way odds (1,2)

• Totals

If the odds are removed, the outcome will be -1 for the removed odds and value OFF.

3-way (1x2) odds are defined like this:

Listing 19: Odds

</Bet>

Correct score odds are defined like this:

Listing 20: Correct score odds

</Bet>

OutCome is the correct score with corresponding odds.

7

Handicap (with draw) odds are defined like this:

Listing 21: Odds

</Bet>

The handicap is defined in the SpecialBetValue attribute. A handicap of "1:0" means that you must add 1 goal to the final number of goals

of the home team before deciding who won the match.

OutCome = "{$competitor1} ({hcp})" indicates a home victory after the handicap is applied on the final result. OutCome = "draw ({hcp})" indicates

a draw after the handicap is applied OutCome = "{$competitor2} ({hcp})" indicates an away victory after the handicap is applied., OutCome="-

1" and value OFF indicates that this market is not available anymore and it must be closed and not offered.

Total odds are defined like this:

Listing 22: Total Odds

</Bet>

OutCome = "Over {total}" means that the total score of the match is more than the supplied value. OutCome = "Under {total}" means the

opposite – the total is less than the supplied value.

Results

Score element has a Type attribute which can be:

• FT = Full time result

This is sent for all sports and indicates the result after normal time.

This is also referred to as "Regular time"

• HT = Half time result

• OT = Overtime result

Can be sent for most sports.

Overtime should not be confused with "Injury time" or "Added time".

8

• AP = Result after penalties

This is a feature primarily used for Soccer and Ice Hockey but it can also be sent for other sports.

• WO = Walkover

Gives the teamID of the winning team/competitor.

It is used when a player cannot play or complete a match. The opponent will then proceed to the next round.

If a player retires we will set WO status for the opponent.

• C = Cancelled game

Indicates the match did not finish (it was not played or it was interrupted).

• MapX = The result of the Map.

This is only used for ESports

Soccer, Handball, Rugby, Futsal, Bandy and Field Hockey

• HT

Ice Hockey, Floorball and Beach Soccer

• 1P = 1st period result

• 2P = 2nd period result

• 3P = 3rd period result

Football, Basketball, Aussie Rules, Water Polo, Speedway and Motor Sport

• 1Q = 1st quarter result

• 2Q = 2nd quarter result

• 3Q = 3rd quarter result

• 4Q = 4th quarter result

Tennis, Beach Volleyball, Volleyball, Table Tennis and Badminton

• Set1 = 1st set result

• Set2 = 2nd set result

• Set3 = 3rd set result

• Set4 = 4th set result

• Set5 = 5th set result

• WO = Walkover

NeutralGround: Optional, contains the following field:

• Value: "0" or "1". If set to "1" this match is played on neutral ground.

9

Cancelled Markets

It might happen that an individual market that was available with odds now needs to be canceled by our team. This will be communicated

with a "C" to indicate market canceled for the particular oddstype it refers to. An example is included below. This will be included in the

Odds and Probabilities once the market has been canceled and will be sent as canceled again in the BetResult once that is sent for the

match.

<Bet OddsType="51"><Odds OutCome="C">Market canceled</Odds></Bet>

Goals

The node includes a number of Goal nodes which hold information of the goal scorers. Attributes of the Goal node:

• Id: unique id of the live event

• ScoringTeam "1" = Home team - "2 " = Away team

• Team1: Current result for home team, at goal time

• Team2: Current result for away team, at goal time

• Time: Match time of goal, in format "MM", e.g. 20

Each goal node has one Player node with these attributes:

• Id: player unique id.

• Name: Name of the scoring player.

Example of the Goals node:

Listing 26: Example of Goals

<Goals>

</Goal>

</Goal>

</Goal>

</Goals>

Cards

The node includes a number of Card nodes, which hold information of cards given in the match. Attributes of the

Card node:

• Id: unique id

• Time Match time of the card, in format "MM:SS", e.g. 20:00

• Type Yellow, Red or YellowRed.

10

Each Card node has one Player node, with the same specification as the Goals node above.

Example of the Cards node:

Listing 27: Cards Node

</Card>

</Card> </Cards>

Outright Specification

The basic structure of an Outright is similar to that of a Match. The following example shows an outright with fixture and odds information

and no results. In addition, the SUPERID attribute is used:

Listing 28: Outright

<Value>France</Value>

</Texts>

<Value>France Ligue 1 2011/12 −" Outright Winner</Value>

</Text></Texts>

</EventName>

</EventInfo>

<Value>Girondins Bordeaux</Value> </Text>

</Texts> <Texts>

<Value>Olympique Marseille</Value>

</Text> </Texts>

</Competitors>

</Fixture>

</OutrightOdds>

</OutrightResult> </Outright>

Notable differences between Match and Outright:

• An Outright may have a rather large Competitors element (and a correspondingly large OutrightOdds element).

• The Fixture information for name and place is not given by Text Elements. It is separated into EventDate and EventName.

• The odds are listed in a slightly different fashion as well. Instead of a MatchOdds element we now have an OutrightOdds element

directly containing the Odds elements.

11

• The ID attribute given in each Odds element correspond to an ID in a Text element describing a competitor in the outright so a

possible outcome. Please note that these IDs are different than the ones used for matches (for example Match Italy team ID: 24494,

the same ID for outrights outcome corresponds to Detroit Tigers)

In order to find the odds for a given competitor the IDs must be linked. You can see an example about how it works in the specific

PDF.

Outright Dates

In the XML for outrights there are 3 dates we send:

• </EventStart> is the day the tournament begins. In the below example 16th August is the date the first fixture was played.

• </EventDate> is the day the outright market will next close and betting will be stopped from this date. This is usually the date of the

next fixture in the tournament. The outright will then re-open once all checks are done and a new future EventDate will be added.

• </EventEndDate> is the end of the tournament.

Example:

Listing 29: Outright Dates

</EventInfo>

Results

The result of the outright above, if it hasn’t been cancelled, would contain the ID of the winning outcome:

Important considerations when using outrights

In some outrights the number of competitors with associated odds reduce over time. The first time the outright is exported it might contain

many competitors but as time passes, it may turn out that it is impossible for some competitors to win the outright. In these cases those

competitors are removed from the export. Examples of this kind of pruning are found in the outright for Bundesliga in German soccer. As

time progresses the chances of a bottom team winning completely vanishes so the team is removed from the outright.

However, there might be other reasons for removing a competitor from an outright. The client should be careful to review the XML data

and update the local system – removing competitors there as well, if needed. If, for instance, a competitor is dropped because the odds

data is considered untrustworthy, it would not be wise of the client to keep the competitor listed with the old odds.

XML Element List

12

The following is a list of all elements and their attributes in the XML format along with a short description.

Element

Attribute

Description

BetbalancerBetData

(none available)

Top-level document containing all other elements in

XML.

Timestamp

CreatedTime

TimeZone

Timestamp of when the XML was generated, in the

clients timezone. See the section Date Format for a

description of the date format.

Sports

(none available)

Grouping element that contains every individual

Sport element.

Sport

Describes a sport. Contains a Texts element with a

textual description of the sport and any number of

Category elements.

BetbalancerSportId

Internal Betbalancer ID for this sport.

Category

Describes a sport. Contains a Texts element with a

textual description of the sport and any number of

Category elements.

BetbalancerCategoryId

Internal Betbalancer ID for this category.

Tournament

Describes a tournament. Contains a Texts element

with a textual description of the tournament and any

number of Match elements.

BetbalancerTournamentId

Internal Betbalancer ID for this tournament.

Match

Container element for all match related information.

BetbalancerMatchId MonitoringMatchID

Internal Betbalancer ID for this match. The MatchId

used in Betbalancer Monitoring interface.

Fixture

(none available)

Meta information for a Match or Outright containing

information about where/when/who for the event.

SportID

(none available)

ChannelName

(none available)

Name of channel.

StartDate

(none available)

The date and time of broadcast. See the section Date

Format for a description of the date format.

The date and time of broadcast. See the section Date

Format for a description of the date format.

Competitors

(none available)

Container element for texts that describe the

competitors. For a normal soccer match this means

that we will find two teams inside this element. For

an outright there are probably more.

DateInfo

(none available)

Container element for specifying time data.

MatchDate

(none available)

Contains a date. See the section Date Format for a

description of the date format.

13

StatusInfo

(none available)

Container element for all elements describing the state

of a match.

Off

(none available)

Match state description. If ’1’, the match will not be

played. In other words, this pertains to an event in the

future.

Canceled

(none available)

Match state description. If ’1’, the match was cancelled.

In other words, this pertains to an event in the past.

MatchOdds

(none available)

Container element for match bet information (outrights

use their own bet information container called

OutrightOdds).

Bet

Description of a single bet.

OddsType

A numerical identifier format of what type of bet we are

describing.

Odds

Element to hold single oddslines.

OutCome

Identifies what outcome the Odds element is

describing. For a three way bet, this may be ’1’, ’X’, or

’2’. For an outright winner, where every outcome

specified is the odds for the given competitor to win,

no value is supplied for the OutCome attribute.

Individual Oddstypes can be canceled and will appear

with OutCome = "C" for that particular OddsType with

reason being "Market canceled".

SpecialBetValue

Holds extra odds information for odds that require

some context (e.g. handicap bets – for which the

SpecialBetValue could be ’1:0’, ’0:1’, ... ).

OutComeId

Numerical value for the specified outcome.

TeamId

Numerical value for the team.

PlayerId

Numerical value for the player.

Result

Container element for all result information including

comments on the match.

ID

Only appears when used in an outright. If the outright

has been cancelled the value of ID is "C", otherwise it is

the ID of a competitor. The place the competitor

finished is found in a Value element inside the Result

element.

BetResult

Container element for bet clearing.

W

Winnerodds element.

Oddstype

The Odds type which are being cleared.

14

Outcome

The Outcome of the specific Odds type. Individual

Oddstypes can be canceled and will appear with

OutCome = "C" for that particular OddsType with

reason being "Market canceled".

SpecialBetValue

Holds extra odds information for odds that require

some context (e.g. handicap bets – for which the

SpecialBetValue could be ’1:0’, ’0:1’, ... ).

OutComeId

Numerical value for the specified outcome.

TeamId

Numerical value for the team.

PlayerId

Numerical value for the player.

ScoreInfo

(none available)

Container element for all match results (scores).

Score

Describes one result score. A match may have several

scores identified by their type.

Type

Identifies what kind of score we are specifying. For a

soccer match typical values are ’FT’ (full time) and ’HT’

(half time).

Comment

(none available)

Container element for comments. Individual comments

are given in Text elements.

Texts

(none available)

Container element for individual Text elements.

Text

Element specifying textual information. This is used in

many places in this XML format. It is mostly used to put

names on sports, categories, tournaments and teams.

Language

identifies the language used. This could for example be

’BET’ (Internal standard), ’en’ (English), ’de’ (German),

’it’ (Italian) or ’fr’ (French) or any of the identifiers noted

in the Language Specifiers section. If this attribute is not

specified the language defaults to ’BET’.

ID

An identifier for the text. Typically utilized when

describing team names in a Competitors element. In

which case the ID is the internal Betbalancer ID for the

team described.

TeamId

A version of ID, but this time guaranteed to refer to a

team.

Type

A type identifier for the text. When using Text elements

to describe teams in a Competitors element this

attribute is used to define the type of the team (i.e. if it

is a home team or an away team).

SUPERID

Uniquely identifies a team independent of context using

an internal Betbalancer ID.

15

Outright

Describes an outright. Unlike matches, outrights are

specified on the category level not the tournament level

of the hierarchy.

BetbalancerOutrightId

Internal Betbalancer ID for this outright.

EventInfo

Container element used in the fixture part of an

outright. Contains meta information about the outright

such as EventDate and EventName.

EventDate

(none available)

Contains a date. See the section Date Format for a

description of the date format.

EventName

(none available)

A text string naming the outright (e.g. "Belgian Grand

Prix – Pole Position").

OutrightOdds

Container element for outright bet information

(matches use their own bet information container

called MatchOdds).

OddsType

A numerical identifier for what type of outright odds we

are describing

Value

(none available)

A general container for "some value". The semantics of

this element are completely bound to the surrounding

element. For example, the contents of Text elements

are specified using Value elements.

NeutralGround

(none available)

Container element for neutral ground information.

SuperTournament

Name

Textual name of the super tournament.

SuperID

Integer value with the id of this super tournament.

Goals

Container element for goals.

Goal

Id

Unique id of the live event.

ScoringTeam

1 = Home team, 2 = Away team.

Team1

Result for home team, at goal time.

Team2

Result for away team, at goal time.

Time

Match time of goal in format "MM", e.g. 20.

Player

Id

Name

Name of the scoring player. If the goal was a penalty, a

(pen) will be added after the team name. If it was an

own goal, (og) will be added.

Cards

Container element for cards.

Card

Id

Time

16

Appendix

Date Format

The date format used in the two date elements (EventDate for outrights and MatchDate for matches) is composed of two sections, date

and time, which are separated by the letter "T". The date section is in the format "YYYY-M-D", and the time section is in the format

"HH:MM:SS.fff". Date string terminate with letter "Z" as per standard. Note that leading zeros are used in the time and date sections.

Type

17

As an example of a date in this format, the following element describes that a match takes place five minutes past six in the afternoon on

the 26th of January 2019: <MatchDate>2019-01-26T18:05:00.000Z</MatchDate> Dates in the XML export are supplied in UTC.

Language Specifiers

BET

Standard

en

English

lv

Latvian

es

Spanish

sqi

Albanian

et

Estonian

lt

Lithuanian

se

Swedish

aa

Arabic

fi

Finnish

mk

Macedonian

th

Thai

aze

Azerbaijan

fr

French

me

Montenegrin

tr

Turkish

bs

Bosnian

ka

Georgian

no

Norweigian

ukr

Ukranian

br

Brasil.portouguese

de

German

pl

Polish

vi

Vietnamese

bg

Bulgarian

el

Greek

pt

Portuguese

zh

Chinese simplified

heb

Hebrew

ro

Romanian

zht

Chinese trad.

hu

Hungarian

ru

Russian

hr

Croatian

id

Indonesian

sr

Serbian

cs

Czech

it

Italian

srl

Serbian Latin

da

Danish

ja

Japanese

sk

Slovakian

nl

Dutch

ko

Korean

sl

Slovenian

Odds types

Side bets Overview

For all bet types where the Outcome description includes the text, (x) most competitive lines will be used" we display a list of the most likely

"Special Bet Values". Values other than the listed examples are possible.

Side bets Soccer

Side Bets for Soccer are grouped within the following categories:

• Regular Match Odds

• Asian Markets

• Markets related to Bookings

• Markets related to Corners

• Goalscorer related markets

18

Regular Match Odds

General definitions: Odds related to the general match flow and result.

Asian Markets

General definitions: Odds related to the general match flow and result.

Asian Handicap: The SpecialBetValue is adjusted depending on how big the favourite of the match is. Asian Totals: The SpecialBetValue is

adjusted depending on the expected total number of points in the match.

When betting Asian handicap markets, bettors don’t necessarily "win 100%" or "lose 100%". "Half wins" and "half loses" are both possible

outcomes when betting quarter-handicaps (handicap +/- 0.25 and +/- 0.75). "Stake returned" is also a possible outcome for integer-

handicaps (handicap +0). The logic of Asian handicap betting is well described on the internet and can be found also at

http://en.wikipedia.org/wiki/Asian_handicap .

We do use:

Status="W" VoidFactor="0,5". . . for "half won" bets.

Status="L" VoidFactor="0,5" . . . for "half lost" bets. VoidFactor="1,0" . . .

for "stake returned" bets.

Markets related to Bookings

General definitions for booking related markets:

Bookings:

Yellow Card = 1 Booking

Red Card = 2 Bookings

Yellow + Yellow Cards leading to a Red Card = 3 Bookings

Booking points: Yellow

Card = 10 points Red

Card = 25 points.

Yellow + Yellow Cards leading to a Red Card = 35 Booking points

Player Markets

“At Least” condition

Some of our Player Markets are settled using the “At Least” condition. Please be aware that this is a different outcome description than any

other markets we currently offer and is not the same as an over/under oddstype.

For example, a bet on Tom Brady to have at least 305 passing yards in a game.

If Brady has 305 yards or more, the bet is a winner.

If Brady has 304 yards or less, the bet is a loser.

Note that the SpecialBetValue will vary for each oddstype depending on the player and the match.

Resulting of Player Markets

Resulting of Player Markets will be sent within the BetResult.

A "W" element is sent for winning bets.

VoidFactor="1.0" is sent for "Void" bets.

Nothing is sent for losing bets.

In the below example these are winning bets because the player in question, Dwyane Wade, did have at least 3, 4, 5 and 6 (SpecialBetValues)

Assists (OddsType 596) in the game.

19

Figure 7: Player Markets Resulting

Note that all results are sent once the final stats are available after a game. There are no result updates sent if the league changes the

stat for a player after review.

Voiding and Resulting for Player Markets

Nr

Sport and Condition

Rules

1

All sports

POSTPONED OR CANCELLED

Bets on players/teams where game is marked as postponed or

cancelled in game state before the scheduled start time shall be

left with pending status and resulted if the game starts within

72 hours of the original (global game time) scheduled start time.

If game does not start within 72 hours, bets shall be Auto

Voided.

2

All sports

CHANGE OF VENUE

All bets created prior to the venue change shall be Auto

Voided.

3

All sports

DELAYED

If the match does not start at the scheduled time, all related

player bets shall still be available for auto verification, unless the

game starts > 72 hours after original scheduled time (see Rule

1).

4

All sports

ABANDONED OR SUSPENDED

If the match starts but is abandoned or suspended at any time

before the match reaches a natural end and the match does not

resume within 5 hours, then all bets on that player shall be Auto

Voided.

5

All sports

PLAYER NONPARTICIPATION

If any player selected for any bet type does not participate in

game then all bets on that player shall be Auto Voided.

6

Soccer only

PLAYER NONSTART

If any player selected for any bet type does not start the game

then all bets on that player shall be Auto Voided.

7

All sports

OVERTIME

Overtime is included for bet resulting. Penalty shootouts are not

included.