Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This type of message is sent when changes are made in the event e.g. stats were edited/corrected or event start date was changed etc.

...

etc.

Message example:

Code Block
languagejson
{
  "id": 412288068,
  "ls_id": 5684905,
  "uuid": "5bf31c86-594d-4e48-b9e0-e4485f52e3c7",
  "type": "event",
  "source": 1148,
  "ut": 1611574231,
  "data": {
    "event": {
      "id": 3755129,
      "action": "update",
      "start_date": "2021-01-02 17:30",
      "ft_only": "no",
      "coverage_type": "from_tv",
      "status_id": 33,
      "status_name":"1st half",
      "sport_id": 5,
      "sport_name":"Soccer",
      "day": 17,
      "neutral_venue": "no",
      "item_status": "active",
      "clock_time": 1,
      "clock_status": "running",
      "area_id": 70,
      "area_name": "Spain"
      "competition_id": 1507,
      "competition_name":"LaLiga Santander",
      "season_id": 46446,
      "stage_id": 108896,
      "stage_name": "Regular season",
      "group_id": null,
      "tour_id": null,
      "tour_name": null,
      "gender": "male",
      "bet_status": "suspended",
      "bet_cards": "suspended",
      "bet_corners": "suspended",
      "relation_status": "not_started",
      "status_type": "live",
      "name": "Getafe CF - Real Valladolid",
      "round_id": 17,
      "round_name": "Round 17",
      "scoutsfeed": "yes",
      "latency": "3-6s",
      "event_stats_lvl": "gold",
      "event_stats_lvl_live": "gold",
      "event_stats_lvl_after": "gold",
      "verified_result": "no",
      "is_coverage_limited": "no",
      "played_time": null,
      "details": [
        {
          "id": 8,
          "value": null
        },
        {
          "id": 19,
          "value": "2021-01-25 11:30:29"
        },
        {
          "id": 227,
          "value": null
        }
      ],
      "participants": [
        {
          "id": 136929,
          "counter": 1,
          "name": "Getafe Club de Futbol, S.A.D.",
          "short_name": "Getafe CF",
          "acronym": "GET",
          "area_id": 70,
          "area_name": "Spain",
          "area_code": "ESP",
          "ut": 1602906642,
          "type": "team",
          "stats": [
            {
              "id": 8,
              "value": 0
            },
            
            {
              "id": 716,
              "value": null
            },
            {
              "id": 777,
              "value": 0
            }
          ],
          "results": [
            {
              "id": 2,
              "value": 0
            },
            {
              "id": 412,
              "value": 0
            }
          ],
          "subparticipants": []
        },
        {
          "id": 136935,
          "counter": 2,
          "name": "Real Valladolid Club de Futbol, S.A.D.",
          "short_name": "Real Valladolid",
          "acronym": "VAL",
          "area_id": 70,
          "area_name": "Spain",
          "area_code": "ESP",
          "ut": 1477213104,
          "type": "team",
          "stats": [
            {
              "id": 8,
              "value": 0
            },
            {
              "id": 716,
              "value": null
            },
            {
              "id": 777,
              "value": 0
            }
          ],
          "results": [
            {
              "id": 2,
              "value": 0
            },
            {
              "id": 412,
              "value": 0
            }
          ],
          "subparticipants": []
        }
      ]
    }
  }
}


Message structure details:

.message


id

Unique identifier for the message

uuid

Universally

unique identifier

Unique Identifier for the massage.
Note: for certain messages, such as updates to a previous, related message, the UUID may be the same. This intentional duplication allows clients to establish correlations between messages, aiding in tracking updates or related data across a system.

type

event

source

Internal attribute, please do not use this attribute

ut

Information about the date and time of when the message was created. Format UNIX_TIMESTAMP.

..data


...event


id

Identifier of the event

ls_id

For internal purposes

action

Describes type of operation for the event. Possible values:

  • insert - new event generated

  • update - event was updated

  • delete - event was deleted

start_date

Start date for the event in format: YYYY-MM-DD hh:mm:ss

ft_only

Determines if only the full time result/score of the event is given. Possible values:

  • yes - result/score is updated only when the event is finished 

  • no - result/score is updated during the event

coverage_type

Type of event coverage. Possible values:

  • from_venue - means the scout is relaying the event directly from the stadium (max. latency 1 second)

  • from_tv - means the scout is relaying the event from tv transmission (max. latency 8 seconds)

  • basic - for this type of coverage we don't provide detailed event incidents (max. latency around 60 seconds)

status_id

Unique identifier of the event status. The list of available statuses you can find in API service method: statuses.index

status_name

Name of the status

sport_id

Identifier for the sport in which the event is played. The list of available sports you can find in API service method: sports.index

sport_name

Name of the sport

day

Day of the season. This attribute is deprecated and will no longer used

neutral_venue

Determines if event is played at a neutral venue. Possible values:

  • yes

  • no

item_status

Describes status for the item (record). Possible values:

  • active - the record is active

  • deleted - the record was deleted by the admin. In the case of when an event was added by mistake

clock_time

Number of seconds that have passed in the current period

clock_status

Clock status. Possible value:

  • running

  • stopped

area_id

Identifier for the area in which the competitions are played

area_name

Name of the area

competition_id

Unique identifier for the competition. The list of available competitions you can find in API service method: competitions.index

competition_name

Name of the competition

season_id

Unique identifier for the season.

stage_id

Unique identifier for the stage

stage_name

Name of the stage

group_id

Unique identifier for the group

tour_id

Unique identifier for the tour in which a competition is played.

sThe

The list of available competitions you can find in API service method: tours.index

tour_name

Name of tour

gender

Competition gender. Possible values:

  • male

  • female

  • mixed

bet_status

Bet status. Possible values:

  • active

  • suspended

bet_cards

Booking market status. Possible values:

  • active

  • suspended

bet_corners

Corners market status. Possible values:

  • active

  • suspended

relation status

Relation status. Attribute for internal purposes. Possible value:

  • not_started - for an event that has not started

  • in_progress - for a live event

  • finished - for an event that has finished

  • 30_min_left - scout confirms his ability to deliver the coverage 30 min before the event

  • 5_min_left - scout confirms his ability to deliver the coverage 5 min before the event

status_type

Type of status. Possible values:

  • live

  • scheduled

  • finished

  • cancelled

  • interrupted

  • deleted

  • other

name

Name of the event

round_id

The list of available rounds can be found in the API service method: rounds.index. Possible null value

round_name

Name of the round. Possible null value

scoutsfeed

Informs about availability in the Scoutsfeed product. Possible values:

  • yes

  • no

latency

Information about the expected latency. Possible values:

  • null (for the event with scoutsfeed=no parameter)

  • 1-2s

  • 3-6s

  • 7-15s

event_stats_lvl

Informs about statistics level for this event. Possible values:

  • bronze

  • silver

  • gold

  • vip

verified_result

Informs that the result has been verified by an internal unit. Possible values:

  • yes

  • no

is_coverage_limited

Informs, that the coverage is limited (reduced range of data related to players). Possible values:

  • yes

  • no

played_time

Number of seconds that have passed including the additional time (only for soccer)

....details


id

Unique identifier for the event details e.g: 1st quarter start time, length of the period. Possible values are different depending on the sport.

value

Value related to the event detail

....participants

Only last changed participant will be sent in the message.

id

Unique identifier of the participant. The list of available participants you can find in API service method: participants.index

counter

Number of participants in the event. Participant with counter="1" is the home team, "2" is the away team

name

Participant name

short_name

Participants abbreviated name, max length: 20 characters

acronym

Max 3 characters in length mini name, e.g. BAR, REA

area_id

Determines the area represented by the participant. The complete list of possible areas can be retrieved using the API resource: areas.index

area_name

Area name represented by the participant

area_code

Max 3 characters in length of the abbreviated area name e.g. GER, POL, FRA

ut

Information about the date and time of when the record was last updated. Format UNIX_TIMESTAMP

type

Informs about the type of participant. Possible values:

  • person

  • team

  • double

.....results


id

Unique identifier for the result. Possible values are different depending on the sport. For more information please find node details in the sports.show API method

value

Value related to the results

.....stats


id

Unique identifier for the statistic. Possible values are different depending on the sport. For more information please find node details in the sports.show API method

value

Value related to the statistic

..event_status_stats

Only for specific incidents. Description below the table

id

Unique identifier for the statistic. Possible values are different depending on the sport. For more information please find node details in the sports.show API method

value

Value related to the statistic

.....subparticipants


id

Unique identifier of the subparticipant.

......results


id

Unique identifier for the result. Possible values are different depending on the sport. For more information please find node details in the sports.show API method

value

Value related to the results

......stats


id

Unique identifier for the statistic. Possible values are different depending on the sport. For more information please find node details in the sports.show API method

value

Value related to the statistic

Info


Partial Statistics - In the case of certain incidents within the API structure, specifically those that trigger a “break” between parts of a match, there is an additional nesting that contains statistics exclusively for the previous (before the break) part of the match.

Structure of data- example:

"event_status_stats": {

Code Block
"33": [
{
"id": 40,
"value": 0},
{
"id": 8,
"value": 0},

Where “33” is the ID of the specific part of the game for which the statistics have been splitted.

Splitted stats are available for these sports:

  • soccer