Sport Line API Field Reference

This reference contains request parameters and JSON fields confirmed by actual Sport Line API responses.

For relationships between fields and differences between match objects returned by different methods, see Match Data Model.

If the Description cell is empty, the purpose of that field has not yet been confirmed. Do not interpret such values independently. A description will be added after the API developer or owner provides clarification.

Request Parameters

Standard Successful Response

Rules for processing successful responses, empty result sets, service messages, and errors are documented in Sport Line API Response Format.

API Error

Sport

This object is returned by sports and at the top level of menu.

Standard icon:

https://cdn.sportapi.net/sports/v1/color/{id}.webp

Country

This object is returned by countries and inside a sport object in menu.

Standard icon:

https://cdn.sportapi.net/flags/v1/color/{id}.webp

Tournament in Navigation Methods

This object is returned by tournaments and inside a country object in menu.

Standard icon:

https://cdn.sportapi.net/tournaments/v1/color/{id}.webp

Tournament in an events Response

Match: Identifiers and Placement

The short match fields in this section are also used by the search response. Search returns a flat match array without odds.

Important: a new game_id is generated for the Live version of a match. Prematch and Live matches cannot be linked using this field.

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

Match: Teams or Participants

To retrieve a standard icon, remove the extension from opp_1_icon or opp_2_icon and insert the remaining name into the URL:

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

Match: Short Betting List

The set of markets and selections depends on the sport. Retrieve the complete selection list through event using game_id.

Betting Market in game_oc_list

In the group format, the API has already arranged the data into columns and sorted it by value. Preserve the API order instead of regrouping or re-sorting selections on the client side.

Selection in oc_list

Practical rules for using these fields and real examples of different bet types are documented in Odds and Betting Market Data Model.

Match: Score, Period, and Additional Data

Statistics Entry in stat_list

Processing rules, real examples, and confirmed statistic IDs are documented in Live Match Statistics Data Model.

Submatch in sub_games

The complete process for retrieving and opening additional matches is documented in Additional Matches and Submatches.

sub_games contains links to separate submatch types: periods, corners, cards, fouls, player statistics, and other available options.

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

"sub_games": []

The events method does not use sub_games; it returns only [] here. The list is available when requesting a specific match through event. Each item contains game_id, game_num, and game_name. To retrieve a submatch’s odds, make a separate event request using its game_id.

Object in event_plan

The events method does not use event_plan and returns only [] here. A populated field is available in a specific event response for a group match. The main match may be named “Home — Away,” while the array contains the complete list of actual teams on both sides. Each object describes a pair of teams and the time of their meeting.

Video and Live 3D Tracker

Detailed rules:

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

If zp is null, Live 3D Tracker is not available for the match.