events Method — Match List

Purpose

The events method returns matches for a selected sport. You can optionally limit the list to one tournament.

The response contains:

• tournament information;
• main match data;
• teams or participants;
• start time;
• current score and period for Live;
• a short set of betting markets and odds;
• available Live statistics, video, and tracker ID.

Use the event method to retrieve the complete betting market list for one match.

All fields are documented separately in the Sport Line API Field Reference.

Before Making the Request

The request requires sportId. Retrieve it through menu or sports.

To request matches from a specific tournament, you also need tournamentId. Retrieve it from menu or tournaments.

Do not use stored static sportId and tournamentId values without checking the current navigation. These IDs must be present in the current menu, or obtained through the sports → countries → tournaments sequence for the same live or line type.

The API shows only sections that currently contain matches. If the only match in a tournament ends or disappears, the tournament will be absent from the next navigation response. If that was the sport’s only match, the sport itself will disappear as well.

Even when using tournamentId=0, take sportId from a current API response.

Request

GET https://YOUR_API_DOMAIN/v1/events/{sportId}/{tournamentId}/{format}/{count}/{type}/{lang}

Send the API key in the HTTP header:

Package: YOUR_API_KEY

Path Parameters

Values of type:

The format Parameter

The match list supports only the sub format. It groups matches by tournament:

body
└── tournament
    └── events_list
        └── matches

The count Parameter

The parameter was created to limit the amount of returned data, but the limit was later removed. The segment remains a required part of the URL for compatibility.

Always pass 50. Regardless of this value, the API returns all available matches for the selected sport or tournament. Do not use the parameter for pagination or response size limits.

Optional Query Parameter

Example:

GET https://YOUR_API_DOMAIN/v1/events/{sportId}/0/sub/50/live/en?cybersport=true

The full responses stored with this documentation were retrieved without query parameters, which means cybersport=false.

Live Request Example

This example requests all Live football matches from all available tournaments:

curl --request GET \
  --url 'https://YOUR_API_DOMAIN/v1/events/1/0/sub/50/live/en' \
  --header 'Package: YOUR_API_KEY'

Prematch Request Example

This example requests all Prematch football matches from all available tournaments:

curl --request GET \
  --url 'https://YOUR_API_DOMAIN/v1/events/1/0/sub/50/line/en' \
  --header 'Package: YOUR_API_KEY'

To retrieve matches from only one tournament, replace 0 with its tournamentId:

curl --request GET \
  --url 'https://YOUR_API_DOMAIN/v1/events/1/1205475/sub/50/live/en' \
  --header 'Package: YOUR_API_KEY'

Shortened Live Response Example

The following excerpt comes from a real English response. It contains one match, one betting market, three selections, and one statistics row.

{
  "status": 1,
  "page": "/v1/events",
  "body": [
    {
      "tournament_id": 1205475,
      "tournament_name": "Australia. NPL Northern Territory",
      "events_list": [
        {
          "sgame_id": "0",
          "stat_id": "0",
          "game_id": 746037229,
          "game_start": 1787310000,
          "country_id": 4,
          "country_name": "Australia",
          "tournament_id": 1205475,
          "tournament_name": "Australia. NPL Northern Territory",
          "opp_1_name": "Garuda Darwin",
          "opp_2_name": "Darwin Olympic",
          "game_oc_counter": 134,
          "game_oc_list": [
            {
              "group_id": 1,
              "group_name": "1X2",
              "columns": 3,
              "oc_list": [
                {
                  "oc_group_name": "1X2",
                  "oc_name": "W2",
                  "oc_rate": 1.064,
                  "oc_size": 0,
                  "oc_pointer": "746037229|1|3|0",
                  "oc_block": false,
                  "op_id": null
                },
                {
                  "oc_group_name": "1X2",
                  "oc_name": "X",
                  "oc_rate": 10.0,
                  "oc_size": 0,
                  "oc_pointer": "746037229|1|2|0",
                  "oc_block": false,
                  "op_id": null
                },
                {
                  "oc_group_name": "1X2",
                  "oc_name": "W1",
                  "oc_rate": 27.0,
                  "oc_size": 0,
                  "oc_pointer": "746037229|1|1|0",
                  "oc_block": false,
                  "op_id": null
                }
              ]
            }
          ],
          "sport_id": 1,
          "sport_name": "Football",
          "timer": 4617,
          "score_full": "0:1",
          "score_period": "0:1;0:0",
          "stat_list": [
            {
              "id": 45,
              "name": "Attacks",
              "opp1": "62",
              "opp2": "58"
            }
          ],
          "period_name": "2nd half",
          "vi": "DR_2_1783062440",
          "zp": 746037229
        }
      ]
    }
  ]
}

This is a shortened excerpt, not a complete match object. Full responses are linked at the end of this document.

Response Structure

Top-level Fields

Tournament Object

Main Match Fields

A Prematch match’s game_id is not retained when it moves to Live. A new game_id is generated for Live, so do not link Prematch and Live matches by this field.

Do not treat sgame_id, stat_id, game_num, stat_list_extra, or game_plan as required integration fields. They are legacy, test, or reserved fields. game_num is scheduled for removal from the API.

Teams or Participants

The opp_1_ids and opp_2_ids arrays are used when one side of a match contains multiple participants. Examples include a tennis doubles team or a group match with several players or teams on each side.

Ready-to-use Team and Participant Icons

Use the standard SportAPI icons for teams and participants:

https://cdn.sportapi.net/opp/v1/color/{iconName}.webp

Take iconName from opp_1_icon or opp_2_icon. In real responses, the name may include a .png extension. Remove the original extension before creating the CDN URL, then add .webp through the URL template.

For example:

opp_1_icon: 8bd073a686a067e6732d8d1688a517c0.png
iconName:    8bd073a686a067e6732d8d1688a517c0

Complete URL:

https://cdn.sportapi.net/opp/v1/color/8bd073a686a067e6732d8d1688a517c0.webp

Apply the same rule to opp_2_icon.

Score, Period, and Live Data

In Prematch, many Live fields contain default values such as 0, an empty string, an empty array, or null. The client must handle all of these variants correctly.

Object in stat_list

Object in sub_games

sub_games refers to separate submatch types such as corners, cards, fouls, first half only, player statistics, and other available options.

In the events match list, the field is returned as an empty array:

"sub_games": []

The events method does not use sub_games; the field is returned only as []. The submatch list is available when requesting a specific match through event. Each item contains a submatch ID but not its odds. To retrieve the odds, make a separate event request using the selected submatch’s game_id.

The events method does not use event_plan; the field is returned as [] in match lists. A populated component match list is available only when requesting a specific match through event.

Betting Markets and Odds

game_oc_counter may be significantly greater than the number of items actually present in game_oc_list. Use event to retrieve the full betting market list for a selected match.

The Short List Depends on the Sport

Do not assume that game_oc_list contains the same markets, names, or number of selections for every sport.

For example:

• in football, the short list may contain a 1X2 market with the first team to win, a draw, and the second team to win;
• in basketball, selections for the first or second team to win are often returned instead of 1X2;
• tennis has no draw selection.

Handle the array dynamically during integration:

1. Do not build the interface only around the 1X2 market.
2. Do not expect a draw selection to be present.
3. Read the actual group_name, columns, and oc_list from the response.
4. Do not rely on the same market and selection order across different sports.
5. To open all available selections, call event using the selected match’s game_id.

Market in game_oc_list

Selection in oc_list

Odds and oc_block may change with every response update.

Video and Live 3D Tracker

If zp is null, Live 3D Tracker is unavailable for the match. The tracker works only for Live matches and supported sports.

More information:

• Live 3D Tracker in Sport Line API;
• Video Streaming in Sport Line API;
• complete Live 3D Tracker integration guide.

Live and Prematch Differences

The match object has the same structure, but its fields are populated differently:

• Live updates the timer, score, period, and statistics;
• in Prematch, these fields usually contain initial or empty values;
• vi and zp relate to additional Live features and may be null;
• odds and selection blocking update independently in Live and Prematch;
• when a match moves from Prematch to Live, it receives a new game_id.

Request and store Live and Prematch separately.

Snapshot of Saved Responses

The Live and Prematch examples use football (sportId=1) and tournamentId=0, so each file contains all matches from all available football tournaments. The format is sub, and the technical count value is 50.

These figures describe specific responses retrieved on August 21, 2026. They are not a permanent description of the API.

Full unabridged responses:

• Live, Russian
• Prematch, Russian
• Live, English
• Prematch, English

The files contain only API response bodies. No API key is stored in them.

Update Frequency

Recommended request frequency for events:

• Live — no more than once every 7 seconds;
• Prematch (line) — no more than once every 30 seconds.

See Data Update Guidelines for more details.

Key, subscription, and parameter errors are documented in Error Handling.