Sport Line API Latest Updates

This page lists the changes that affect integration: new methods and parameters, changes to responses and errors. Newest entries first.

October 6, 2026

New topchampionships Method — Popular Championships

• Before: there were two ready-made selections, both of matches (topmatches, toplist); a list of popular championships had to be built on your side.
• Now: GET /v1/topchampionships/{live|line}/{lang} returns up to 12 popular championships with sport, country, and match count. Prematch — the main championships (Champions League, top leagues, NBA, and so on); Live — the most popular of those in progress now.
• More: topchampionships.

Match Calendar: All Sports, Periods by Hours and Days

• Before: the line calendar (events by period) worked only for football, its data was collected by separate requests and could lag behind; the method was not described in the documentation.
• After: the calendar works for all line sports and is built from the same Prematch line as events. Periods: the next 2, 4, 6, or 12 hours, today until the end of the day, or a specific day up to 5 days ahead. odds=false is supported.
• More: Match calendar.

toplist for All Prematch Sports

• Before: toplist could return an empty list for a sport that had no Live matches at that moment, and for some time after a service update. Service sections could appear in the selection.
• Now: the top is built for all Prematch sports and is available right after a service update; service sections are filtered out, as in topmatches. If a sport has no top matches, the list is still empty.
• More: toplist.

Responses Without Odds — the odds=false Parameter

• Before: methods returning matches always included odds (game_oc_list), even if a project needed only the schedule, scores, or statistics.
• Now: the optional odds=false parameter returns the same data without game_oc_list. The response is 2–5 times smaller, and dozens of times smaller for a single match page. The game_oc_counter field (the number of outcomes of a match) is kept. It works in events (including the line calendar), event, and in topmatches and toplist with full=true (their short summaries contain no odds anyway). Without the parameter the response is unchanged.
• More: Core Concepts — Data Without Odds, events, event.

October 4, 2026

Prematch for a Whole Sport: “Top-50” by Default, the Full Line with match=all

• Before: a Prematch request for a whole sport (tournamentId=0) returned the full line — about 2,000 matches and ~9 MB of JSON for football.
• Now: by default the “Top” is returned — 50 upcoming matches with the highest popularity weight (top leagues and tournaments). The full line is returned with match=all; its tournaments are ordered by popularity and matches by start time. Requests for a specific tournament, Live, and esports are unchanged.
• More: events.

Sub-events No Longer Duplicate Matches in Lists

• Before: sub-events of a match (for example “Player duel (goals)”) were returned in the events list as separate rows and looked like duplicate matches.
• Now: lists contain only main matches. Sub-events are available in sub_games of the main match and are requested with the event method by their game_id.
• More: events, additional matches and submatches.

New account Method — Client Keys and Access

• Before: the key’s expiration date, available sports, and languages could only be obtained from the manager.
• Now: GET /v1/account with any of the client’s keys returns data for all of their keys: the expiration date, days left, sports and languages, access restrictions, the last request time, the number of requests for 7 days, and the IP address the request came from.
• More: account.

Key Expiration Date in Every Response — the X-Key-Expires Header

• Before: the access expiration date could not be obtained from an API response.
• Now: every successful response contains the X-Key-Expires header with the key’s expiration date (ISO 8601, UTC) — you can use it to remind about renewal in advance.
• More: Authentication and Access.

New Key Errors: Paused and “Not Active Yet”

• Before: a paused key received the same error as an expired one — Package has expired; a key could not be issued with a future start date.
• Now: a paused key receives Package is blocked (its expiration date does not change); a key can be issued in advance and receives Package is not active yet until its start date. Package has expired is returned only when the access period has actually ended.
• More: Error Handling.

Keys with the all Language and a Language Not Enabled in the Line

• Before: a key with all languages (all) requesting a language not enabled in the line received a match without odds.
• Now: such a request receives the Invalid language error — the same as a key with an explicit language list.
• More: Error Handling, languages.

Key Access Restrictions by IP and Website

• Before: a key worked from any server and website.
• Now: at the client’s request, a key can be restricted to the IP addresses of the client’s servers and/or to the client’s websites. From another address the API returns Access from IP … is not allowed for this Package (or site …), and the text contains the address to allow. Without restrictions the key works as before.
• More: Authentication and Access, Error Handling.

A New Key or Renewal Takes Effect Immediately

• Before: after a new key was issued or the term was extended, the change could take effect with a delay.
• Now: a new key, renewal, pause, and resumption take effect immediately.

Service Tournaments Are Excluded from the Line

• Before: menus and lists contained the bookmaker’s service sections (“Special bets”, “Winner”, “Results”, “Alternative”, and similar).
• Now: such sections are excluded from the menu, tournaments, match lists, top matches, and search.

Outcome Names Match the Bookmaker’s

• Before: some outcome names contained unfilled templates and leftover brackets.
• Now: outcome names are built by the bookmaker’s rules; outcomes of an unknown format are not shown. In sports where outcomes are participant names (Formula 1, horse racing, and others), the names are returned in the requested language.
• More: odds and market groups.