GET Inplay Livescores

GET All Inplay Livescores: returns all the inplay fixtures.

https://api.sportmonks.com/v3/football/livescores/inplay

{
    "data": {
        "id": 19146701,
        "sport_id": 1,
        "league_id": 501,
        "season_id": 23690,
        "stage_id": 77471570,
        "group_id": null,
        "aggregate_id": null,
        "round_id": 340573,
        "state_id": 5,
        "venue_id": 8909,
        "name": "Celtic vs Kilmarnock",
        "starting_at": "2024-08-04 15:30:00",
        "result_info": "Celtic won after full-time.",
        "leg": "1/1",
        "details": null,
        "length": 90,
        "placeholder": false,
        "has_odds": true,
        "has_premium_odds": true,
        "starting_at_timestamp": 1722785400
    },

Field

Description

Type

Refers the unique id of the fixture

integer

sport_id

Refers to the sport the fixture is played at

integer

league_id

Refers to the league the fixture is played in

integer

season_id

Refers to the seasons the fixture is played in

integer

stage_id

Refers to the stage the fixture is played in

integer

group_id

Refers to the group the fixture is played in

integer / null

aggregate_id

Refers to the aggregate the fixture is played at

integer / null

state_id

Refers to the state the fixture is played at

integer

round_id

Refers to the round the fixture is played at

integer / null

state_id

Refers to the state the fixture is played at

integer

venue_id

Refers to the venue the fixture is played at

integer / null

name

Represents the name of the participants

string / null

starting_at

Datetime object representing the start time

date / null

result_info

Represents the final result info

string / null

leg

Represents the leg of the fixture

string

details

Represents details about the fixture

string / null

length

Length of the fixture (minutes)

integer / null

Name

Required?

Description

api_token

YES

Another option is to provide the API token in the header.

Your unique API token. Ex. ?api_token=YOUR_TOKEN

include

Enrich the API response with more data by using includes. Ex. &include=participants;events

select

Select specific fields on the base entity. Read how to select fields in our tutorial.

sortBy

Order by specific fields on the base entity. For more information check out this page.

filters

Filter the API response on multiple related entities. There are static filters and dynamic filters. Please find the possibilities in the Static and Dynamic Filter tab.

locale

Translate name fields of the API Response in your selected language. Find more information and which languages are available on our translations page.

Static filters are always the same and filter in one specific way without any custom options. Each static filter is listed below and has a description of how it filters. For more information, please look at our Filters page.

Static Filters

Available on Entity

Description

Example

ParticipantSearch

Fixture

Filter on the matches of specific participants.

&include=participants&filters=participantSearch:Celtic

todayDate

Fixture

Filter all fixtures to find only the fixtures of today.

&filters=todayDate

venues

Fixture

Find all fixtures that are played in a specific venue.

&include=venue&filters=venues:venueIDs &include=venue&filters=venues:10,12

IsDeleted

Fixture

Filter on deleted fixtures only. This filter helps to keep your database in sync.

&filters=IsDeleted

markets

Odds

Filter the odds on a selection of markets separated by a comma.

&include=odds&filters=markets:marketIDs &include=odds&filters=markets:12,14

bookmakers

Odds

Filter the odds on a selection of bookmakers separated by a comma. (e.g: 2,14).

&include=odds&filters=bookmakers:bookmakerIDs &include=odds&filters=bookmakers:2,14

WinningOdds

Odds

Filter all winning odds.

&include=odds&filters=WinningOdds

The dynamic filters are based on entities and includes. Each dynamic filter uses an entity to filter on and one entity to apply the filter on. Below are examples with explanations of how filters are set up. For more information, please look at our Filters page.

Using an include? Check their respective filters on their entity page. For example if you use &include=participants you can apply team-related filters.

Dynamic Filters

Available on Entity

Description

Examples

types

Statistics, Events, Lineup, and way more. Check this endpoint for all possibilities.

Filter the Types on a selection of Fixture statistics separated by a comma. Filter on the specific events you want to show.

&include=statistics&filters=statisticTypes:TypeIDs &include=statistics&filters=statisticTypes:42,49 &include=events&filters=eventTypes:14

states

Fixtures Check this endpoint for all possibilities.

Filter the states of fixtures separated by a comma.

&include=state&filters=fixtureStates:StateIDs &include=state&filters=fixtureStates:1

leagues

Fixtures, Seasons, Standings, and way more. Check this endpoint for all possibilities.

Filter the fixtures based on leagues and their rounds.

&filters=fixtureLeagues:leagueIDs

&filters=fixtureLeagues:501,271

groups

Fixtures, Standing, and more. Check this endpoint for all possibilities.

Filter the fixtures based on groups. Get their fixtures and standings.

&include=group&filters=fixtureGroups:groupIDs &include=group&filters=fixtureGroups:246691

countries

Coaches, Leagues, Players, Teams, and way more. Check this endpoint for all possibilities.

Filter the coaches, leagues, players and more based on countries.

&include=coaches&filters=coachCountries:CountryIDs &include=coaches&filters=coachCountries:1161

seasons

Statistics (players, team, coaches, referees), Standings, and way more. Check this endpoint for all possibilities.

Filter statistics, standings and topscorers based on seasons.

&include=season.statistics&filters=seasonStatisticTypes:TypeIDs &include=season.statistics&filters=seasonStatisticTypes:52

Filters

More information on how to use filters can be found on our tutorials on how to filter. If you want more information on which filters to use you can check out the following endpoint:

https://api.sportmonks.com/v3/my/filters/entity?api_token=YOUR_TOKEN

Pagination

Include depth

You can use a total of 3 nested includes on this endpoint

Include options

sport round stage group aggregate league seasoncoaches tvStations venue state weatherReport lineups events timeline comments trends statistics periods participantsinplayOdds prematchNews postmatchNews metadata sidelinedpredictions referees formations ballCoordinates scores xGFixture expectedLineups matchfacts AIOverviews

Related Entities:

Get an overview and explanation of all the fields returned in the API response. The related entities for the livescores endpoints are:

Fixture

Postman

We also offer detailed postman documentation with examples and a complete up-to-date version of all our endpoints. Below is a button that lets your fork the collection or import it.

Code Example

require "uri"
require "net/http"

url = URI("https://api.sportmonks.com/v3/football/livescores/inplay?api_token=YOUR_TOKEN")

https = Net::HTTP.new(url.host, url.port)
https.use_ssl = true

request = Net::HTTP::Get.new(url)

response = https.request(request)
puts response.read_body

import http.client

conn = http.client.HTTPSConnection("api.sportmonks.com")
payload = ''
headers = {}
conn.request("GET", "/v3/football/livescores/inplay?api_token=YOUR_TOKEN", payload, headers)
res = conn.getresponse()
data = res.read()
print(data.decode("utf-8"))

<?php

$curl = curl_init();

curl_setopt_array($curl, array(
  CURLOPT_URL => 'https://api.sportmonks.com/v3/football/livescores/inplay?api_token=YOUR_TOKEN',
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_ENCODING => '',
  CURLOPT_MAXREDIRS => 10,
  CURLOPT_TIMEOUT => 0,
  CURLOPT_FOLLOWLOCATION => true,
  CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
  CURLOPT_CUSTOMREQUEST => 'GET',
));

$response = curl_exec($curl);

curl_close($curl);
echo $respons

OkHttpClient client = new OkHttpClient().newBuilder()
  .build();
Request request = new Request.Builder()
  .url("https://api.sportmonks.com/v3/football/livescores/inplay?api_token=YOUR_TOKEN")
  .method("GET", null)
  .build();
Response response = client.newCall(request).execute();

var unirest = require('unirest');
var req = unirest('GET', 'https://api.sportmonks.com/v3/football/livescores/inplay?api_token=YOUR_TOKEN')
  .end(function (res) { 
    if (res.error) throw new Error(res.error); 
    console.log(res.raw_body);
  });

package main

import (
  "fmt"
  "net/http"
  "io/ioutil"
)

func main() {

  url := "https://api.sportmonks.com/v3/football/livescores/inplay?api_token=YOUR_TOKEN"
  method := "GET"

  client := &http.Client {
  }
  req, err := http.NewRequest(method, url, nil)

  if err != nil {
    fmt.Println(err)
    return
  }
  res, err := client.Do(req)
  if err != nil {
    fmt.Println(err)
    return
  }
  defer res.Body.Close()

  body, err := ioutil.ReadAll(res.Body)
  if err != nil {
    fmt.Println(err)
    return
  }
  fmt.Println(string(body))
}

PreviousLivescores NextGET All Livescores

Last updated 4 months ago

Was this helpful?