GET Probabilities by Fixture ID

This endpoint returns all the predictions available for your requested fixture ID.

Base URL

https://api.sportmonks.com/v3/football/predictions/probabilities/fixtures/{ID}

Example Response

{
  "data": [
    {
      "id": 3317639,
      "fixture_id": 18535605,
      "predictions": {
        "scores": {
          "0-0": 2.84,
          "0-1": 4.97,
          "0-2": 4.47,
          "0-3": 3.46,
          "1-0": 4.75,
          "1-1": 8.72,
          "1-2": 7.72,
          "1-3": 4.62,
          "2-0": 4.07,
          "2-1": 7.81,
          "2-2": 6.82,
          "2-3": 4.28,
          "3-0": 2.37,
          "3-1": 4.47,
          "3-2": 4.09,
          "3-3": 2.81,
          "Other_1": 9.33,
          "Other_2": 11.81,
          "Other_X": 0.59
        }
      },
      "type_id": 240
    },

Field Description

Field	Description	Type
id	Refers to the id of the state	integer
fixture_id	Refers to the fixture related to the prediction	integer
predictions	The data object with prediction values	object
type_id	Refers to the type of the prediction	integer

Not all fixtures contain sufficient data for reliable predictions. To determine if a fixture is suitable for prediction, use the metadata include to check its "predictable" status.

Query Parameters

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	NO	Enrich the API response with more data by using includes. Ex. &include=participants;events
select	NO	Select specific fields on the base entity. Read how to select fields in our tutorial.
filters	NO	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	NO	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

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
N/A	N/A	Not available for this endpoint	N/A

Dynamic Filters

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 to. Below is an example with an explanation 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=fixtures, you can apply fixture-related filters.

Dynamic Filters	Available on Entity	Description	Examples
Types	Statistics, Events, Lineup, Stages and way more. Check this endpoint for all possibilities.	Filter the predictions on a selection of type IDs separated by a comma.	&filters=predictionTypes:typeIDs &filters=predictionTypes:236

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

YES

Paramaters

Parameter	Required	Description	Example
order	No	Returns predictions ordered by id (asc or desc). Defaults to asc	&order=desc
per_page	No	The amount of results to return per page (max 50.). Defaults to 25.	&per_page=30
page	No	You can paginate using the has_more parameter to determine if you can still propagate through the results.	&page=2

Include depth

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

Include options

type fixture

Related Entities:

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

• Prediction

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

Ruby

require "uri"
require "net/http"

url = URI("ttps://api.sportmonks.com/v3/football/predictions/probabilities/fixtures/{ID}?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

Python

import http.client

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

PHP

<?php

$curl = curl_init();

curl_setopt_array($curl, array(
  CURLOPT_URL => 'https://api.sportmonks.com/v3/football/predictions/probabilities/fixtures/{ID}?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

Java

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

Node.js

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

Go

package main

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

func main() {

  url := "https://api.sportmonks.com/v3/football/predictions/probabilities/fixtures/{ID}?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))
}