FMInside APIfminside.net ↗
Access Football Manager player profiles, attributes, positions, club data, and search via 5 endpoints covering the full FMInside.net database.
What is the FMInside API?
The FMInside.net API exposes 5 endpoints covering the Football Manager player and club database, returning detailed player attributes across Technical, Mental, Physical, and Set Pieces categories. Use search_players to find players by name and retrieve their unique IDs, or call get_player_details with a profile URL path to pull a full breakdown including current/potential ability ratings, foot preferences, contract expiry, and biographical fields.
curl -X GET 'https://api.parse.bot/scraper/e737f35d-e126-4fda-8e43-a3a67a4f722f/search_players?limit=5&query=Mbappe' \ -H 'X-API-Key: $PARSE_API_KEY'
Full-text search over the FM player database by name or keyword. Returns a list of matching player summaries with IDs, positions, age, and profile URLs. The server returns only top matches for the query.
| Param | Type | Description |
|---|---|---|
| limit | integer | Maximum number of results to return. |
| queryrequired | string | Player name or search phrase. |
{
"type": "object",
"fields": {
"total": "integer total number of players returned",
"players": "array of player summary objects with name, unique_id, url, age, positions, and image_url"
},
"sample": {
"data": {
"total": 5,
"players": [
{
"age": "26",
"url": "/players/7-fm-26/85139014-kylian-mbappe",
"name": "Kylian Mbappé",
"image_url": "https://img.fminside.net/facesfm26/85139014.png",
"positions": [
"AMR",
"AML",
"ST"
],
"unique_id": "85139014"
}
]
},
"status": "success"
}
}About the FMInside API
Player Search and Browsing
The search_players endpoint accepts a query string and an optional limit, returning an array of player summary objects each containing name, unique_id, age, positions, url, and image_url. Results are ranked by relevance and capped at top matches. The list_players endpoint browses the full database ordered by site ranking, paginating internally to reach the requested limit, returning the same summary shape plus a count field.
Full Player Profiles
Two endpoints return complete player profiles. get_player_details takes a relative or absolute profile URL (e.g. /players/7-fm-26/85139014-kylian-mbappe) and returns fields including club, height, full_name, left_foot, positions, age, image_url, and unique_id. get_player_by_id accepts a player_id string (the unique_id from search or list results) and returns the same profile structure — useful when you have an ID but not a URL slug. Both endpoints expose the same detailed attribute groups: Technical, Mental, Physical, and Set Pieces ratings alongside nationality, current/potential ability, and contract expiry.
Club Data
The list_clubs endpoint browses clubs ordered by reputation and supports an optional league filter accepting values such as 'Premier League', 'LaLiga', 'Serie A', 'Bundesliga', or 'Ligue 1'. Each club summary includes name, unique_id, url, logo_url, league, and reputation. Results are paginated internally up to the requested limit. Omitting the league parameter returns clubs across all leagues.
Data Coverage Notes
All endpoints reflect the FMInside.net database for the current FM edition indexed by the site. Player positions are returned as arrays of position abbreviation strings (e.g. ["ST", "AM"]). The unique_id field is consistent across endpoints and serves as the stable identifier for cross-referencing search results, list results, and detail lookups.
The FMInside API is a managed, monitored endpoint for fminside.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fminside.net changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official fminside.net API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a Football Manager scouting tool that queries
search_playersby name and displays current/potential ability ratings from the full profile. - Populate a squad-builder app by listing clubs filtered by
leagueand then fetching players linked to a given club. - Create a position-filtered talent browser using
list_playersand filtering locally on thepositionsarray in each summary. - Compare player physical attributes (height, foot preferences) across results from
get_player_by_idfor a shortlist ofunique_idvalues. - Build a reputation-ranked club directory by calling
list_clubswith a league filter and displayinglogo_urlandreputationfields. - Automate FM save analysis by resolving player IDs found in exported game data against
get_player_by_idto pull current attribute ratings. - Generate nationality breakdowns across a player pool by collecting
nationalitydata from batchget_player_detailscalls.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does FMInside.net have an official developer API?+
What does `get_player_details` return beyond what `search_players` includes?+
search_players returns summary fields: name, unique_id, age, positions, url, and image_url. get_player_details adds club, full_name, height, left_foot, current and potential ability ratings, nationality, contract expiry, and the full Technical, Mental, Physical, and Set Pieces attribute groups.Can I filter `search_players` results by position or nationality?+
search_players endpoint accepts only a query string and an optional limit. Filtering by position or nationality is not exposed as a parameter. The returned player summary objects do include positions, so client-side filtering on that field is possible. You can fork this API on Parse and revise it to add server-side position or nationality filter parameters.Does the API cover player transfer history or match statistics?+
How do I look up a player if I only have their name, not their ID or URL?+
search_players with the player's name as the query parameter. Each result includes a unique_id and a url field. Pass the unique_id to get_player_by_id or the url to get_player_details to retrieve the full profile.