GET All Players
This endpoint returns player information from your requested player ID.
https://api.sportmonks.com/v3/football/players{
"data": [
{
"id": 14,
"sport_id": 1,
"country_id": 320,
"nationality_id": 320,
"city_id": null,
"position_id": 221,
"detailed_position_id": null,
"type_id": 25,
"common_name": "D. Agger",
"firstname": "Daniel Munthe",
"lastname": "Agger",
"name": "Daniel Munthe Agger",
"display_name": "D. Agger",
"image_path": "https://cdn.sportmonks.com/images/soccer/players/14/14.png",
"height": 191,
"weight": 84,
"date_of_birth": "1984-12-12",
"gender": "male"
},
{
"id": 21,
"sport_id": 1,
"country_id": 455,
"nationality_id": 455,
"city_id": null,
"position_id": 26,
"detailed_position_id": null,
"type_id": 26,
"common_name": "L. Miller",
"firstname": "Liam",
"lastname": "Miller",
"name": "Liam Miller",
"display_name": "Liam Miller",
"image_path": "https://cdn.sportmonks.com/images/soccer/players/21/21.png",
"height": 170,
"weight": 66,
"date_of_birth": "1981-02-13",
"gender": "male"
},id
Refers to the unique id of the player
integer
sport_id
Refers to the sport of the player
integer
country_id
Refers to the country of birth of the player
integer
nationality_id
Refers to the national team that the player has opted to represent
integer
city_id
Refers to the city of birth of the player
string
position_id
Refers to the position of the player
integer
detailed_position_id
Refers to the detailed position of the player
integer
type_id
Refers to the type of the player
integer
common_name
Refers to the name the player is known for
string
firstname
Refers to the first name of the player
string
lastname
Refers to the last name of the player
string
name
Refers to the name of the player
string
display_name
Refers to the name that is often used to display in applications
string
image_path
Image path to player headshot
string
height
Refers to the height of the player
integer
weight
Refers to the weight of the player
integer
date_of_birth
Refers to the date of birth of the player
string
gender
Refers to the gender of the player
string
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
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 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.
IdAfter
GET All Players
Filter all players starting from a certain player ID.
Handy if you're doing an import for all players and want to continue from a certain ID.
&filters=IdAfter:playerID
&filters=IdAfter:758
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.
detailTypes
Statistics Check this endpoint for all possibilities.
Filter the statistics (detailTypes) on a selection of types separated by a comma.
&include=statistics.details.type&filters=playerstatisticdetailTypes:typeIDS
&include=statistics.details.type&filters=playerstatisticdetailTypes:59
countries
Coaches, Leagues, Players, Teams, and way more. Check this endpoint for all possibilities.
Filter players and more based on countries.
&include=country&filters=playerCountries:countryIDS
&include=country&filters=playerCountries:462
seasons
Statistics (players, team, coaches, referees), Standings, and way more. Check this endpoint for all possibilities.
Filter player statistics based on seasons.
&include=statistics.details.type&filters=playerstatisticSeasons:seasonIDS
&include=statistics.details.type&filters=playerstatisticSeasons:19735
lineups
Players
Filter the player lineups on types
&include=lineups.type&filters=lineupTypes:typeIDS
&include=lineups.type&filters=lineupTypes:12
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:
Pagination
YES
Parameters
order
No
Returns players 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 3 nested includes on this endpoint
Include options
sport country city nationality transfers pendingTransfers teams statistics latest position detailedPosition lineups trophies metadata
Related Entities:
Get an overview and explanation of all the fields returned in the API response. The related entities for the player endpoints are:
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/players/{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/players/{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/players/{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 $responsOkHttpClient client = new OkHttpClient().newBuilder()
.build();
Request request = new Request.Builder()
.url("https://api.sportmonks.com/v3/football/players/{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/players/{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/players/{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))
}Last updated
Was this helpful?