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

Player-specific identity request A genuine player ID is required; team and event IDs are not interchangeable inputs.
Returned biography field selection Build a profile only from attributes confirmed in the actual player response.
Duplicate-name profile safety Compare validated identity context when several players share a name.
Profile enrichment boundary Missing career, injury or valuation fields must not be inferred from other entity data.

Live API Demo

GET /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'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

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.

Related operations

Guides

View Subscription Plans →