laby APIlaby.net ↗
Access Minecraft player profiles, UUID lookups, name history, badges, capes, and laby.net site statistics via a clean REST API.
What is the laby API?
The laby.net API exposes 4 endpoints covering Minecraft player profiles, badge data, featured users, and cape rankings. The get_profile endpoint accepts either a Minecraft username or UUID and returns the player's current name, full name history with change timestamps, and an array of earned badges with descriptions. The remaining endpoints surface global platform statistics, curated featured users, and a popularity-ordered list of every official Minecraft cape tracked on the site.
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
Profile and Name History Lookup
The get_profile endpoint takes a single identifier parameter — either a Minecraft username such as Notch or a UUID such as 069a79f4-44e9-4726-a5be-fca90e38aaf5 — and returns the canonical uuid, the current username, a name_history array, and a badges array. Each name_history entry includes the name, a changed_at timestamp, an accurate boolean indicating whether the timestamp is verified, and a last_seen_at value. Each badge object carries its own uuid, name, description, and a received_at timestamp showing when the player earned it.
Capes and Featured Users
get_capes returns every official Minecraft cape tracked on laby.net, ordered by the number of players currently wearing each one. Each cape object includes a uuid, name, description, tags, a texture_url pointing to the cape image, and a user_count. get_featured_users returns a curated, periodically rotating list of notable accounts; each entry contains the user's uuid, display name, and their full badges array — making it easy to cross-reference against profile lookups.
Platform Statistics
get_statistics requires no parameters and returns a labynet object containing a trends sub-object with profiles and skins fields. Each trends field includes a total count and a real-time velocity figure (profiles or skins added per second), giving a snapshot of platform growth at query time. A contributions array is also included in the labynet object.
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?+
- Resolve a Minecraft username to its canonical UUID for database deduplication
- Audit a player's complete name-change history including timestamps and accuracy flags
- Display a player's earned laby.net badges and when they were received on a community profile page
- Build a cape browser sorted by popularity using user_count and texture_url from get_capes
- Track laby.net platform growth over time by polling get_statistics for profiles and skins velocity
- Populate a featured-players widget on a Minecraft community site using the curated get_featured_users list
- Cross-reference badge ownership across multiple players to find shared achievements
| 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.