Search Football Players API

Find player candidates by name and verify player identifiers before opening profiles, images or player news. Requires search. Preserve any returned identity context to distinguish namesakes, then pass a confirmed player ID to a player-specific operation. No player-search response sample has been verified, so exact fields, pagination and empty-result semantics are not established.

API Features

Player-name discovery contract The required search field allows player lookup without reusing a team identifier.

Namesake-safe selection Use validated context in returned candidates rather than choosing the first matching name.

Player-profile input preparation Resolve a candidate's genuine player ID before issuing a profile request.

Watchlist identity discipline Keep separate player identifiers even when multiple records have the same name.

Live API Demo

GET /api/project/football/get-search-players

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/football/get-search-players?key=<API_KEY>&search=m'

curl -X GET 'https://api.opendata-api.com/api/project/football/get-search-players?key=<API_KEY>&search=m'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Provide a player selector before a profile and image lookup.
Create a scouting watchlist that retains namesakes as separate identities.
Find a valid player ID for a news panel instead of copying a club ID into playerid.
Review ambiguous player-name matches when importing an editorial contact sheet.

Frequently asked questions

Can I search by name without knowing playerid?

Yes. The required input is search. Confirm the intended player before passing the returned genuine player identifier to playerid.

Does player search support pagination?

Only search is declared, not page. Response structure and pagination semantics have not been demonstrated; do not add unsupported pagination inputs.

How should I handle namesakes or no matches?

Inspect identity context and keep namesakes separate. Validate this operation's empty-result format instead of assuming general search's suggestions=[].

Related operations

Guides

View Subscription Plans →