NameMC APIfr.namemc.com ↗
Retrieve Minecraft player profiles, name history, skin gallery, username availability, and recent name changes from NameMC via a structured JSON API.
What is the NameMC API?
This API exposes 5 endpoints covering NameMC data: player profiles, skin galleries, username search, name availability checks, and a live feed of recent name changes. The get_player_profile endpoint returns a player's current username, UUID, full skin history with thumbnail and body-render URLs, and a timestamped name-change history — all in a single call by username, UUID, or NameMC profile ID.
curl -X GET 'https://api.parse.bot/scraper/74336619-75f3-4075-a721-9dc0b199d651/get_player_profile?identifier=Notch' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve a Minecraft player's profile information including name history, skins, and monthly views. Accepts a username, UUID, or NameMC profile ID (e.g. 'Notch', 'Dream.1'). Returns the player's current name, UUID, skin gallery, name change history, and view statistics in a single fetch. name_history holds exactly one entry per name the account has used, newest first, mirroring the site's Name History table: each entry carries the name and the ISO-8601 UTC timestamp the account changed to it, with changed_at set to the literal string 'Original' for the account's first name (no change date exists). Duration/interval annotations shown alongside the table are not part of the history. Skin thumbnails and 3D renders are pre-built URLs. An identifier the site does not recognise as a player yields a not-found (stale input) error rather than an empty profile.
| Param | Type | Description |
|---|---|---|
| identifierrequired | string | Minecraft username, UUID, or NameMC profile ID (e.g. 'Notch', 'Dream.1') |
{
"type": "object",
"fields": {
"name": "current player username",
"uuid": "Minecraft UUID with dashes",
"skins": "array of skin objects with 'id', 'url', 'thumbnail', and 'body_render' fields",
"stats": "object with 'monthly_views' string",
"name_history": "array, newest first, of name records with 'name' (the username) and 'changed_at' (ISO-8601 UTC timestamp the account switched to that name, or the string 'Original' for the account's first name)"
},
"sample": {
"data": {
"name": "Foxxyy8",
"uuid": "a16d8994-2cd2-4b57-8582-1cf5f0234136",
"skins": [
{
"id": "dce273967ecaf396",
"url": "https://namemc.com/skin/dce273967ecaf396",
"thumbnail": "https://s.namemc.com/2d/skin/face.png?id=dce273967ecaf396&scale=4",
"body_render": "https://s.namemc.com/3d/skin/body.png?id=dce273967ecaf396&model=classic&width=256&height=256"
}
],
"stats": {
"monthly_views": "1 / month"
},
"name_history": [
{
"name": "Foxxyy8",
"changed_at": "2025-07-19T05:52:29.256Z"
},
{
"name": "fuxtendo",
"changed_at": "2024-05-21T16:05:03.338Z"
},
{
"name": "thefailcraft8",
"changed_at": "Original"
}
]
},
"status": "success"
}
}About the NameMC API
Player Profiles and Name History
The get_player_profile endpoint accepts a Minecraft username, UUID, or NameMC profile ID (such as Notch or Dream.1) and returns the player's current name, dashed UUID, monthly view count, a skin array with id, url, thumbnail, and body_render fields, and a name_history array sorted newest-first where each entry carries the name and a changed_at ISO-8601 UTC timestamp. This is useful for audit trails, display cards, or detecting account renames over time.
Skin Gallery and Search
The get_trending_skins endpoint paginates through NameMC's skin gallery using a 1-based page parameter and a category string — one of trending, new, top, or random. Each page returns up to 48 skin objects with the same id, url, thumbnail, and body_render shape used in profile responses. The search_players endpoint handles both exact and partial username queries: an exact match returns a single direct-match entry with name, url, and identifier, while partial queries return a list of matching players in the same shape.
Username Availability and Recent Changes
The get_name_availability endpoint takes a single name parameter and returns an Available, Unavailable, or Unknown status alongside a monthly_searches count (or null when the figure is not available). The list_recent_name_changes endpoint requires no parameters and returns a feed of the latest name changes — up to 25 records — sorted newest-first. Each record includes old_name, new_name, and the timestamp of the change, making it practical for monitoring name-change activity across the Minecraft community.
The NameMC API is a managed, monitored endpoint for fr.namemc.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when fr.namemc.com 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 fr.namemc.com 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 Minecraft player lookup tool showing UUID, skin history, and all previous usernames with change timestamps
- Monitor a list of account names for renames using periodic calls to
get_player_profileand comparingname_history - Check whether a desired Minecraft username is currently claimable and how often it is searched each month
- Populate a skin browser with paginated results from the
trending,new, ortopcategories including 3D body renders - Alert bots or Discord webhooks whenever a watched username appears in the
list_recent_name_changesfeed - Resolve a UUID to a current username or vice versa without maintaining your own Mojang API integration
- Search for players by partial name to build autocomplete or player-suggestion features in Minecraft tooling
| 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 NameMC have an official developer API?+
What does `get_name_availability` return when availability cannot be determined?+
status of Unknown when NameMC cannot determine whether the name is taken or free. The monthly_searches field will be null in that case as well.How many recent name changes does `list_recent_name_changes` return, and how fresh is the data?+
Does the API expose Minecraft server statistics or server listings?+
Can I retrieve the full historical name-change log for all players, not just recent changes?+
list_recent_name_changes endpoint covers only the latest feed (up to 25 entries site-wide). Per-player history going back further is available through get_player_profile for individual accounts, but a bulk historical export across all players is not currently exposed. You can fork this API on Parse and revise it to add deeper historical pagination if the source makes more records available.