NameMC APInamemc.com ↗
Retrieve Minecraft username availability, player UUIDs, cape holders, and skin history from NameMC via 4 structured endpoints.
What is the NameMC API?
The NameMC API exposes 4 endpoints for querying Minecraft player data from namemc.com, including username drop schedules, player profiles with UUIDs, cape ownership lists, and raw page access. The get_names endpoint returns usernames approaching availability with their exact drop timestamps and search counts, while get_profile returns per-player details including UUID, monthly views, claimed status, and the timestamp of the latest skin upload.
curl -X GET 'https://api.parse.bot/scraper/fdb92c23-8dea-447b-a4ab-fed705a714c1/get_names?url=https%3A%2F%2Fnamemc.com%2Fminecraft-names%3Ftime%3D20260610T093006Z%26sort%3Dasc&limit=5' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace namemc-com-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: NameMC SDK — bounded, re-runnable; every call capped."""
from parse_apis.namemc_api import NameMC, CapeType, ProfileNotFound
client = NameMC()
# List dropping Minecraft names (upcoming username availability)
for name in client.droppingnames.list(limit=5):
print(name.username, name.droptime, name.searches)
# Get a player profile by username
profile = client.profiles.get(username="Notch")
print(profile.username, profile.uuid, profile.monthly_views, profile.is_claimed)
# List holders of a specific cape type using constructible Cape
founders_cape = client.cape(type=CapeType.FOUNDERS)
for holder in founders_cape.holders(limit=10):
print(holder)
# Typed error handling for a non-existent profile
try:
client.profiles.get(username="zzz_nonexistent_xyz_000")
except ProfileNotFound as exc:
print(f"Profile not found: {exc.username}")
print("exercised: droppingnames.list / profiles.get / cape.holders / ProfileNotFound")
Retrieve Minecraft usernames that are about to become available (dropping). Each entry includes the username, its scheduled drop time, and the number of times it has been searched. Results are ordered by drop time ascending. Pagination is cursor-based via a time parameter in the URL. The endpoint returns one page at a time; pass the next_url from a prior response to advance.
| Param | Type | Description |
|---|---|---|
| url | string | Full URL for pagination, obtained from next_url in a prior response. |
| limit | integer | Max number of results to return. Omitting returns all names on the page. |
{
"type": "object",
"fields": {
"names": "array of objects with username (string), droptime (ISO timestamp string), and searches (integer)",
"next_url": "string or null, URL for the next page of results"
},
"sample": {
"data": {
"names": [
{
"droptime": "2026-06-10T09:20:30.921Z",
"searches": 1,
"username": "ru5k"
},
{
"droptime": "2026-06-10T09:20:34.034Z",
"searches": 0,
"username": "TippersVault"
}
],
"next_url": "https://namemc.com/minecraft-names?time=20260610T093006Z&sort=asc"
},
"status": "success"
}
}About the NameMC API
Username Drop Tracking
The get_names endpoint returns an array of Minecraft usernames that are scheduled to become available, ordered by droptime ascending. Each entry includes the username, an ISO timestamp for when it drops, and an integer searches count reflecting how many times it has been looked up on NameMC. Pagination is cursor-based: pass the next_url value from a prior response into the url parameter to fetch the next page. The optional limit parameter caps the number of results returned per call.
Player Profile Lookup
The get_profile endpoint accepts a username (3–16 characters, case-insensitive) and returns the player's uuid in dashed format, a monthly_views count, an is_claimed boolean indicating whether the owner has claimed the profile on NameMC, and a latest_skin_timestamp ISO string for the most recent skin upload. When the username does not exist in the NameMC database, the endpoint returns an input_not_found response rather than an empty object.
Cape Ownership
The get_cape_users endpoint lists Minecraft usernames of players who own a specific cape type. The required cape_type parameter must be one of NameMC's known cape identifiers. Results are paginated with 1-based page numbering; the has_next boolean in the response signals whether additional pages exist. This makes it straightforward to iterate all holders of a given cape type across multiple pages.
Raw HTML Access
The get_raw_html endpoint accepts any relative path or full NameMC URL and returns the full HTML content, the resolved URL, and the HTTP status_code. This is useful for accessing NameMC pages that do not yet have a dedicated structured endpoint, giving callers flexibility to parse additional data not covered by the other three endpoints.
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 expiring Minecraft usernames by polling
get_namesand alerting when a target name'sdroptimeis within a defined window. - Resolve a Minecraft username to its UUID using
get_profilefor integration with the Mojang API or game server authentication. - Build a cape rarity tracker by iterating
get_cape_usersacross multiple pages to count total holders of each cape type. - Track skin update activity for a set of players by comparing
latest_skin_timestampvalues over time via repeatedget_profilecalls. - Identify highly sought-after dropping names by sorting
get_namesresults by thesearchesfield to find the most-searched upcoming drops. - Verify whether a player has claimed their NameMC profile using the
is_claimedfield fromget_profilebefore displaying profile trust indicators. - Fetch and parse NameMC leaderboard or statistics pages not covered by structured endpoints using
get_raw_htmlwith a relative path.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. 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_profile` return when a username doesn't exist?+
get_profile returns an input_not_found result rather than a response object with null fields. This lets callers distinguish a missing profile from a profile with incomplete data (for example, a null uuid or latest_skin_timestamp on a valid but sparse profile).Does the API return historical username changes or name history for a player?+
get_profile returns the current username, UUID, skin timestamp, and view counts, but no previous username list. You can fork this API on Parse and revise it to add a name-history endpoint using get_raw_html against the player's profile path.What cape type identifiers can be passed to `get_cape_users`?+
cape_type parameter must match one of NameMC's internal cape identifiers as they appear on the site's cape listing pages (for example, optifine, minecon2016, birthday). Passing an unrecognized identifier will return an empty or error result. Use get_raw_html against the NameMC capes index to enumerate the full list of recognized cape slugs.Is skin texture or skin image data returned by any endpoint?+
get_profile returns latest_skin_timestamp, which can be combined with the Mojang skin CDN and the player's uuid to construct a skin image URL independently. You can fork this API on Parse and revise it to extract skin texture URLs if get_raw_html exposes them on the profile page.