laby APIlaby.net ↗
Retrieve Minecraft player profiles, UUID lookups, name history, skin history, badges, capes, and site statistics from laby.net via a single REST API.
What is the laby API?
The laby.net API exposes 7 endpoints covering Minecraft player data tracked by laby.net, including full profile lookups, badge details, and skin history. The get_profile endpoint accepts either a Minecraft username or UUID and returns the player's current name, dashed UUID, badge objects with descriptions and award timestamps, and a timestamped name-change history. Additional endpoints surface cape popularity rankings, a live feed of recent username changes, and platform-wide profile and skin growth statistics.
curl -X GET 'https://api.parse.bot/scraper/6ab8df1c-ccdb-4aa1-a8a8-3986f96e9bf1/get_profile?identifier=Notch' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve Minecraft profile data including username, UUID, name history, and badges. Accepts either a Minecraft username or UUID as input. Returns a single Profile with full detail including badge descriptions and name-change timestamps.
| Param | Type | Description |
|---|---|---|
| identifierrequired | string | Minecraft username (e.g. 'Notch') or UUID (e.g. '069a79f4-44e9-4726-a5be-fca90e38aaf5'). |
{
"type": "object",
"fields": {
"uuid": "string, player UUID",
"badges": "array of badge objects with uuid, name, description, and received_at fields",
"username": "string, current Minecraft username",
"name_history": "array of name history entries with name, changed_at, accurate, and last_seen_at fields"
},
"sample": {
"data": {
"uuid": "069a79f4-44e9-4726-a5be-fca90e38aaf5",
"badges": [
{
"name": "Notch",
"uuid": "cb7f5156-2825-4064-8631-6423d76faf0f",
"description": "The founder of Minecraft",
"received_at": "2009-05-09T22:00:00+00:00"
}
],
"username": "Notch",
"name_history": [
{
"name": "Notch",
"accurate": true,
"changed_at": null,
"last_seen_at": "2026-06-10T10:31:29+00:00"
}
]
},
"status": "success"
}
}About the laby API
Player Profiles and Name History
The get_profile endpoint accepts either a Minecraft username (e.g. Notch) or a dashed/undashed UUID and returns the player's current username, canonical uuid, a badges array (each badge carries a uuid, name, description, and received_at timestamp), and a name_history array sorted oldest-to-newest. Each name-history entry includes the name, a changed_at ISO timestamp (null for the original registration name), an accurate boolean indicating whether laby.net has confirmed the exact change time, and last_seen_at. The dedicated get_name_history endpoint returns the same name array alongside a total count, useful when you only need rename data without badge detail.
Skin History and Cape Data
get_skin_history returns every skin texture laby.net has on record for a player, ordered newest-first. Each entry in the skins array includes image_hash, file_hash, texture_url (a direct PNG link), first_seen_at, last_seen_at, and use_count indicating how many players have worn that exact skin texture. The get_capes endpoint lists all official Minecraft capes tracked by laby.net, ordered by user_count descending. Each cape object includes a uuid, name, description, texture_url, and the current user_count.
Name Change Feed and Site Statistics
The list_recent_name_changes endpoint provides a paginated feed of username changes, newest first. Each item exposes old_name, new_name, changed_at, and old_name_available_from (when the vacated name becomes claimable again). Pagination uses limit (1–25) and offset parameters; the response echoes both and includes has_more, resolved_count, and unresolved_count to distinguish items laby.net could and could not link to a confirmed player. The get_statistics endpoint requires no parameters and returns a labynet object with a trends sub-object containing live profiles and skins counts with per-second velocity figures.
Featured Users
get_featured_users returns the curated list of highlighted community members. Each item in the items array contains a uuid, display name, and the user's badges array. The featured list is maintained by laby.net and rotates periodically, so results will change over time without any parameter changes on your end.
The laby API is a managed, monitored endpoint for laby.net — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when laby.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 laby.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?+
- Look up a Minecraft player's full badge collection and award dates by username or UUID using
get_profile. - Track when a Minecraft account changed its username and whether each timestamp is confirmed accurate via
get_name_history. - Monitor the real-time feed of username changes to detect when a desirable name becomes available using
list_recent_name_changesand theold_name_available_fromfield. - Build a cape rarity tool by sorting results from
get_capesbyuser_countto show which capes are least common. - Audit how many distinct skins a player account has used over time and when each was first and last seen via
get_skin_history. - Display laby.net platform growth metrics — profile and skin counts plus per-second velocity — in a statistics dashboard using
get_statistics. - Populate a community showcase page with laby.net featured users, their display names, and earned badges from
get_featured_users.
| 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 laby.net have an official public developer API?+
What does the `list_recent_name_changes` endpoint return for unresolved entries?+
uuid will be null and new_name will be null. The response includes separate resolved_count and unresolved_count fields so you can track the ratio without iterating the full items array. Pagination is handled via limit and offset parameters, and the has_more boolean tells you whether additional entries exist beyond the current page.How accurate are the `changed_at` timestamps in name history?+
accurate boolean. When accurate is false, laby.net recorded the name but cannot confirm the exact moment it changed — the changed_at value is an approximation. last_seen_at reflects when laby.net last observed that name on the account, which may differ from when the change actually occurred.Does the API expose individual player cape ownership or only the global cape list?+
get_capes returns the global list of capes with aggregate user_count values. Per-player cape data — which specific cape a given player is wearing — is not returned by any current endpoint. You can fork this API on Parse and revise it to add a per-player cape lookup endpoint.