NameMC APInamemc.com ↗
Access Minecraft username availability, drop times, player UUIDs, skin history, name history, and cape holder lists via the NameMC API.
What is the NameMC API?
The NameMC API exposes 6 endpoints covering Minecraft player profiles, username availability, and cape ownership data. Use get_names to retrieve usernames scheduled to drop with exact ISO timestamps and search counts, get_profile to pull a player's UUID, monthly view count, and claim status by username, or search_name to see every profile that has ever held a given name along with its current availability status.
curl -X GET 'https://api.parse.bot/scraper/fdb92c23-8dea-447b-a4ab-fed705a714c1/get_names?limit=5&length=4&charset=letters&length_op=eq' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve Minecraft usernames that are about to become available (dropping), ordered by drop time ascending. Each entry includes the username, its scheduled drop time, and the number of times it has been searched per month. Filters supported by the site itself are applied before pagination: name length with a comparison (exactly, at most, at least 3-16 characters), dictionary-word language (English, French, Dutch, German, Italian, Polish, Portuguese, Spanish) and a minimum monthly search count. The site offers no character-class filter, so charset (digits only, letters only, alphanumeric) is applied by this API to the rows of each fetched page; when charset is set, up to 5 consecutive pages are read in one call until limit matches are collected or the list ends, and a page can legitimately yield no matches (e.g. 4-digit names are rare). Pagination is cursor-based: next_url is the site's link to the following page and carries the site-side filters, so pass it back as url unchanged (repeat charset and limit, which the URL does not carry); the other filter inputs are ignored when url is supplied. next_url is null on the final page. One request per call without charset. Example of one shape: length 4 with length_op eq and charset letters yields names of exactly four letters.
| Param | Type | Description |
|---|---|---|
| url | string | Full URL for pagination, obtained from next_url in a prior response. When supplied, length, length_op, lang and min_searches are ignored because the URL already carries them. |
| lang | string | Keep only names that are dictionary words in this language (site-side filter), e.g. en for English words or fr for French words. |
| limit | integer | Max number of results to return. Omitting returns all names on the page (or all charset matches across the pages read). |
| length | integer | Name length to filter on, 3-16 (site-side). Combined with length_op; when length_op is omitted, exact match is used. |
| charset | string | Character class the whole name must consist of: digits, letters or alphanumeric. Applied by this API to the fetched rows, not by the site. |
| length_op | string | How length is compared: le (at most), eq (exactly) or ge (at least). Only meaningful together with length. |
| min_searches | integer | Keep only names searched at least this many times per month (site-side filter). |
{
"type": "object",
"fields": {
"names": "array of objects with username (string), droptime (ISO timestamp string), and searches (integer, searches per month)",
"next_url": "string or null, URL for the next page of results (null on the final page)"
},
"sample": {
"data": {
"names": [
{
"droptime": "2026-09-28T21:37:37.687Z",
"searches": 0,
"username": "fxvb"
},
{
"droptime": "2026-09-28T21:52:18.747Z",
"searches": 1,
"username": "hejv"
},
{
"droptime": "2026-09-28T22:08:10.027Z",
"searches": 2,
"username": "Nzlu"
},
{
"droptime": "2026-09-28T22:17:35.867Z",
"searches": 6,
"username": "ihif"
},
{
"droptime": "2026-09-28T22:24:34.187Z",
"searches": 1,
"username": "smmw"
}
],
"next_url": "https://namemc.com/minecraft-names?time=20260929T024652Z&length_op=eq&length=4&sort=asc"
},
"status": "success"
}
}About the NameMC API
Player Profiles and Username Lookup
The get_profile endpoint accepts a Minecraft username (case-insensitive, 3–16 characters) and returns the player's UUID in dashed format, whether the profile is claimed by its owner (is_claimed), monthly profile views, and the ISO timestamp of the most recent skin upload. The search_name endpoint goes further: given a query name it returns every profile that has ever held that name, each with its profile_id, current username, and full name list, plus the name's current status (available or unavailable) and searches_per_month.
Name and Skin History
get_name_history returns a player's complete rename log, ordered newest-first, with each entry carrying a order integer (1 = the original name), the username, and a changed_at ISO timestamp. get_skin_history returns every skin the site has on record for a profile: each entry includes a skin_id, the player model (slim or classic), an uploaded_at timestamp, a flag indicating whether it is the currently worn skin, and a direct skin URL. Both endpoints accept a username parameter and also return the player's uuid.
Dropping Names and Cape Holders
get_names lists usernames whose Mojang name-change cooldown is expiring, sorted by droptime ascending. Each result includes the username, the scheduled drop ISO timestamp, and a searches count reflecting how often the name has been looked up on the site. Results are paginated via a next_url field; pass that URL as the url parameter on the next call. get_cape_users accepts a cape_type code (e.g. minecon2012, founders) or a display name and returns up to 1,000 usernames of holders for that cape, the cape's display name, and the site's reported total_profiles count, which may exceed the number of usernames returned.
The NameMC API is a managed, monitored endpoint for namemc.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when 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 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?+
- Monitor username drop times with get_names to register desirable names the moment they become available
- Verify a player's UUID and claimed status via get_profile before issuing rewards or permissions on a Minecraft server
- Audit a player's full rename history with get_name_history to detect ban evasion or impersonation
- Track skin changes over time using get_skin_history to verify account ownership or document a player's history
- Check whether a specific cape (e.g. minecon2016) is owned by a player by cross-referencing get_cape_users results
- Measure name desirability by comparing searches_per_month from search_name before bidding on or trading a username
- Identify all profiles that have previously held a target username using search_name to assess name history and availability
| 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.