Beach Soccer

Sport specific information for beach soccer

Match statuses for beach soccer

ID
Match Status
Description
Additional information

0

NOT_STARTED

Not started yet

-

1

FIRST_PERIOD

1st period

-

301

FIRST_PAUSE

First intermission

-

2

SECOND_PERIOD

2nd period

-

302

SECOND_PAUSE

Second intermission

-

3

THIRD_PERIOD

3rd period

-

100

ENDED

Match has ended

-

32

AWAITING_OT

Waiting for overtime to start

-

40

OVERTIME

Overtime (in case the match goes to extra time)

-

110

AFTER_OT

Match finished after overtime

-

34

AWAITING_PENALTIES

Waiting for penalty shoot-out to start

-

50

PENALTY_SHOOTING

Penalty shoot-out

-

120

AFTER_PENALTIES

Match finished after penalty shoot-out

-

80

INTERRUPTED

The match has been interrupted

-

90

ABANDONED

The match has been abandoned

-

Events in beach soccer

ID
Event
Description
Coverage
extrainfo

1010

Betstart

Shows that betting markets can be activated. Betstart is not only a pre match event but is also used during the match.

iScout (BC)

-

1011

Betstop

Beststop status is used to indicate that betting market shall be closed. Common reasons are: Score under review, Scout lost connection.

iScout (BC)

-

1012

Kickoff team

Which team will have the kick off in the match.

1013

Matchstatus

Sent when the status of the match changes.

iScout (BC)

See table above for match statuses

1015

Free comment

Used for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..

iScout (BC)

-

1024

Match about to start

Match about to start status appears shortly before serving team takes the first serve.

iScout (BC)

-

1031

Ball in play

Ball in play status is used when service has been taken and ball is in play.

iScout (BC)

-

1035

Timeout

Timeout status is given whenever a team calls a timeout. Each team is entitled to a max. of 1 timeouts each set.

iScout (BC)

-

1036

Time start /stop

Triggered when the clock is started or stopped.

iScout (BC)

  • description: time started or stopped

  • values:

    • 0 = time stopped

    • 1 = time started

1039

Manual time adjustment

Manual adjustment of time

iScout (BC)

  • description: Number of seconds adjusted.

  • values: a positive or a negative integer

1044

Deleted event alert

Manual removal of an event (e.g. last point).

iScout (BC)

Id of event that was deleted.

1046

Score change

Information about the match score updated point by point.

iScout (BC)

soccer point type. Possible values:

  • 0 = Standard

  • 1 = Ace

  • 2 = Service error

1047

Timeout over

Timeout over status is given when timeout is over.

iScout (BC)

-

1102

Coverage status

Sent when the coverage status for the match changes.

iScout (BC)

Possible values:

  • 0 = Covered

  • 1 = Coverage abandoned

  • 2 = Match will not be covered

110

Ball possession

Possession change to the given team.

iScout (BC)

30

Goal

Sent when the goal is confirmed.

iScout (BC)

  • extrainfo

    • description: goal type

    • values:

      • 0 = Unknown

      • -100 = Shot

      • -200 = Free kick

      • -300 = After corner

      • 1 = Penalty

      • 2 = Own goal

      • 3 = Header

      • 4 = Fast break

      • 5 = Breakthrough

      • 6 = Direct free throw

      • 7 = even strength

      • 8 = Power play

      • 9 = Short handed

      • 10 = Pivot

      • 11 = Empty net

1018

Possible goal

Possible goal.

iScout (BC)

1019

Canceled goal

Canceled goal.

iScout (BC)

extrainfo

  • description: reason

  • values:

    • 0 = unknown

    • 1 = off side

    • 2 = foul

    • 3 = incorrect entry

    • 4 = out of bounds

    • 5 = play stopped

1015

Free comment

Used for any kind of additional information during the match. Example: "Match interrupted due to flood light break down", etc..

iScout (BC)

50

Red card

Used when the red card is confirmed.

iScout (BC)

45

Yellow/Red card

Used when it is confirmed the player has been sent off due to two yellow cards.

iScout (BC)

1040

Possible red card

Used when there is a strong possibility of a red card. Entries are assigned to teams. Note that the possible red card could also be a possible yellow/red card

iScout (BC)

1041

Canceled red card

Used when possible red card is not being con- firmed. Note that the cancelled red card could also be a cancelled yellow/red card.

iScout (BC)

1059

Direct foul

Sent when a direct foul happens. Leads to a direct free kick for the opposing team.

iScout (BC)

1060

Direct free kick

Direct free kick

iScout (BC)

161

Penalty awarded

Used when the penalty shot is confirmed.

iScout (BC)

40

Yellow card

Used when the yellow card is confirmed.

iScout (BC)

666

Penalty missed

Used when the penalty shot is missed.

iScout (BC)

1042

Possible penalty

Used when there is a strong possibility of a penalty shot.

iScout (BC)

1043

Canceled penalty

Used when a possible penalty is not confirmed.

iScout (BC)

1035

Timeout

A team calls a timeout. Entries can be assigned to teams, but neutral timeouts are possible too.

iScout (BC)

1047

Timeout over

The timeout is over

iScout (BC)

1050

Possible empty net situation

Triggered when one of the teams pulls out the goal keeper

iScout (BC)

1051

Empty net situation

Triggered when an empty net situation is confirmed.

iScout (BC)

1052

Empty net situation over

Triggered when the empty net situation is resolved and goal keeper is back.

iScout (BC)

1053

Empty net situation canceled

Triggered when an empty net situation is not confirmed.

iScout (BC)

1044

Deleted event alert

Manual removal of an event.

iScout (BC)

154

Corner

Used when the corner is confirmed

iScout (BC)

1017

Canceled corner

Used when possible corner is not confirmed

iScout (BC)

1016

Possible corner

Happens at the exact moment there is a corner. Entries are assigned to teams

iScout (BC)

43

Suspension

Triggered whenever a player is sent off due to a foul.

iScout (BC)

  • extrainfo

    • description: Number of minutes

    • values:

      • 2

      • 4

1049

Suspension over

Triggered when suspended player returns.

iScout (BC)

1104

Penalty shootout starting team

Information about which team is going to begin with the shootout.

iScout (BC)

1064

Play resumes after goal

Used when the play resumes after a goal, by a kick off.

iScout (BC)

1416

Possible suspension

Possible suspension

iScout (BC)

1418

Suspension not confirmed

Sent when possible suspension is not confirmed

iScout (BC)

158

Injury

Injured player

iScout (BC)

155

Shot on target

A shot on target.

iScout (BC)

15

Temporary interruption

The match has been temporarily interrupted.

iScout (BC)

156

Shot off target

Shot off target

iScout (BC)

16

Game On

Sent after temporary interruption

iScout (BC)

152

Throw In / Kick In

iScout (BC)

172

Shot blocked

Happens whenever the shot is blocked. Entries are assigned to teams.

iScout (BC)

1084

Possible Yellow card

Possible yellow card

iScout (BC)

1085

Yellow Card cancelled

Possible yellow card canceled

iScout (BC)

Sport specific XML elements and attributes

This section explains what elements / attributes one can expect for beach soccer matches in addition to the standard elements and attributes, and what the meaning of those elements and attributes is.

Attributes in <match>-element

XML example

<match t1namenatural="AL Hamidi" t2namenatural="Dibba Al-Hisn" t2name="DIBBA AL-HISN" t2id="29646829" t1name="AL HAMIDI" t1id="29646835" t1abbr="HAM" t2abbr="DIB" start="1734348600000" matchid="56379963" feedtype="full" extrainfo="0" betstatus="BETSTOP" connectionstatus="0" device="4" coveredfrom="venue" timerunning="0" st1id="1206761" st2id="1206755" matchtime="00:00" sportid="60" stime="1734518264702">

XML elements and attributes definition

Element
Attributes
Description
Possible values

Match

extrainfo

Integer specifying special information for the match.

Integer. Possible values: 0 - 3 x 12 min

Elements in <match> element

XML example

<status start="1734351900220" name="ENDED" id="100"/>
<score type="current" t1="3" t2="2"/>
<score type="period3" t1="1" t2="0"/>
<score type="period2" t1="1" t2="0"/>
<score type="period1" t1="1" t2="2"/>
<red t2="0" t1="0"/>
<yellow t2="0" t1="1"/>
<shotsontarget t2="7" t1="10"/>
<shotsofftarget t2="10" t1="12"/>
<shotsblocked t2="3" t1="6"/>
<fouls t2="1" t1="0"/>
<directfreekicks t2="0" t1="0"/>
<corners t2="9" t1="5"/>
<penalties t2="0" t1="1"/>
<kickoffteam team="1"/>
<throwins t2="17" t1="14"/>

XML elements and attributes definition

Element
Attributes
Description
Possible values

score

Multiple occurrences possible, each occurrence describes the amount of points for the specified period in the match. This element always gets included in full feed, and in the delta feed for the following events:

soccer full score (1046)

t1

Amount of goals home team.

Integer

t2

Amount of goals away team.

type

For what period in the match the points were scored.

String

red

t1

Amount of red cards home team.

Integer

t2

Amount of red cards away team.

Integer

yellow

t1

Amount of yellow cards home team.

Integer

t2

Amount of yellow cards away team.

Integer

shotsontarget

t1

Amount of shots on target home team.

Integer

t2

Amount of shots on target away team.

Integer

shotsofftarget

t1

Amount of shots off target home team.

Integer

t2

Amount of shots off target away team.

Integer

shotsblocked

t1

Amount of shots blocked home team.

Integer

t2

Amount of shots blcoked away team.

Integer

fouls

t1

Amount of fouls home team.

Integer

t2

Amount of fouls away team.

Integer

directfreekicks

t1

Amount of direct free kicks home team.

Integer

t2

Amount of direct free kicks away team.

Integer

corners

t1

Amount of corners home team.

Integer

t2

Amount of corners away team.

Integer

kickoffteam team

team

Team that started the game

Integer (1,2 - Home /away)

penalties

t1

Amount of penalties home team.

Integer

t2

Amount of penalties away team.

Integer

throwins

t1

Amount of throw-ins home team.

Integer

t2

Amount of throw-ins away team.

Integer

Attributes in <event> element

XML example

<match matchid="9574475" ... >
<events>
<event type="40" stime="1734351176629" side="home" mtime="28:02" info="Yellow card [T1]" id="4941641059" uuid="3ff8559a-41a3-49ab-92ec-2b1e8f838b96" matchscore="2:2" remainingtimeperiod="07:58" periodnumber="3" matchstatus="THIRD_PERIOD"/>
</events>
</match>

XML attributes definition

Element
Attributes
Description
Possible values

event

extrainfo

Attribute containing additional information about the event.

Long

side

Team: home/away

String

matchscore

Score at the time of the event

String

remainingtimeperiod

Remaining time in the current period

String MM:SS

Last updated

Was this helpful?