Get Football Player Details
View all Football Data API endpoints →Resolve a player identifier through the player-detail operation for a profile assembled from fields the response actually supplies. Requires playerid from player search or a validated squad. The catalogue supplies 671529 as an example input, but no player-detail payload has been verified. Confirm identity and available attributes before display; do not assume career history, injury status, valuation or biographical fields from the endpoint name.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/football/get-player-detail-by-player-id API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/football/get-player-detail-by-player-id?key=<API_KEY>&playerid=671529'
Query Result
Use Cases
- Create a player page from a verified squad or player-search selection.
- Disambiguate namesakes before linking player profiles in match articles.
- Audit which profile fields are actually available before committing to a roster-card design.
- Validate a stored player identifier before associating news and image requests with it.
Frequently asked questions
Where should playerid come from?
Use player search or a validated club roster. The catalogue example 671529 does not establish a particular identity or a demonstrated profile response.
Which biography fields will the profile include?
The response has not been demonstrated. Inspect actual attributes before assuming birthday, nationality or career-history fields exist.
Are injuries and player market values guaranteed?
No. The operation name does not establish those attributes. Do not infer missing values, and verify namesakes and genuine player IDs.