GET Transfer Rumours by Player ID

Returns the transfers from your requested player ID.

https://api.sportmonks.com/v3/football/transfer-rumours/players/PLAYER_ID

{
  "data": [
    {
      "id": 5,
      "sport_id": 1,
      "player_id": 34053,
      "position_id": 27,
      "from_team_id": 20,
      "to_team_id": 8,
      "from_league_id": 8,
      "to_league_id": 8,
      "transfer_fee_id": 78365,
      "status_id": 90319,
      "probability": "HIGH",
      "source_name": "The Guardian",
      "source_url": "https://www.theguardian.com/football/2025/sep/01/
         liverpool-agree-125m-deal-to-sign-alexander-isak",
      "amount": 144000000,
      "currency": "EUR",
      "date": "2025-06-23",
      "type_id": 219,
      "status": {
        "id": 90319,
        "name": "Confirmed Rumour",
        "code": "rumour-confirmed",
        "developer_name": "RUMOUR_CONFIRMED",
        "model_type": "rumour-status",
        "stat_group": null
      }
    }
  ]
}

Field

Description

Type

id

The unique id of the transfer rumour.

integer

sport_id

The sport related to the transfer.

integer

player_id

The player the rumour relates to.

integer

position_id

The position of the player.

integer

from_team_id

The team the player would transfer from.

integer

to_team_id

The team the player would transfer to.

integer

from_league_id

The league of the originating team.

integer / null

to_league_id

The league of the destination team.

integer / null

transfer_fee_id

The fee type id. Use the transferFee include for the full fee object. Resolve values via the config endpoint.

integer

status_id

The current status of the rumour as a numeric id. Use the status include to resolve the name and code, or see the config endpoint for all possible values.

integer / null

probability

The assessed likelihood of the rumoured move: LOW, MEDIUM, or HIGH.

string

source_name

The name of the publication that reported the rumour.

string

source_url

The URL of the original article.

string

amount

The rumoured transfer fee amount. Null if not publicly disclosed.

integer / null

currency

The currency of the transfer fee.

string / null

date

The date the rumour was reported, in YYYY-MM-DD format.

string

type_id

The transfer type id (e.g. loan, permanent). Resolve via the type include or the config endpoint.

integer

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.

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

N/A

Not available on this endpoint

N/A

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=fixtures, you can apply fixture-related filters.

Dynamic Filters

Available on Entity

Description

Examples

types

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

Filter the transfers on a selection of type ids separated by a comma.

&include=type&filters=transferTypes:TypeIDs

&include=type&filters=transferTypes:219,220

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

Parameters

Parameter

Required

Description

Example

order

Returns latest updated transfers (order asc or desc). Defaults to desc

&order=desc

per_page

The amount of results to return per page (max 50.). Defaults to 25.

&per_page=30

page

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

sport player type fromTeam toTeam position detailedPosition status

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/transfer-rumours/players/PLAYER_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

import http.client

conn = http.client.HTTPSConnection("api.sportmonks.com")
payload = ''
headers = {}
conn.request("GET", "/v3/football/transfer-rumours/players/PLAYER_ID?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/transfer-rumours/players/PLAYER_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

OkHttpClient client = new OkHttpClient().newBuilder()
  .build();
Request request = new Request.Builder()
  .url("https://api.sportmonks.com/v3/football/transfer-rumours/players/PLAYER_ID?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/transfer-rumours/players/PLAYER_ID?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/transfer-rumours/players/PLAYER_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))
}

PreviousGET Transfer Rumours by Team ID

NextGET Transfer Rumours Config

Last updated 1 month ago

Was this helpful?