laby.net APIlaby.net ↗
Retrieve Minecraft player profiles, UUID lookups, name history, badges, and laby.net platform statistics via a simple REST API.
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.
| Param | Type | Description |
|---|---|---|
| identifierrequired | string | Minecraft username (e.g. 'Player123') or UUID (e.g. 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'). |
{
"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": "55eccadf-2bef-41ef-b494-099b56ca06b6",
"badges": [
{
"name": "Cape Collector",
"uuid": "ec16a378-c15b-4e6b-a856-d2220b98d3ae",
"description": "The account owns all free common capes",
"received_at": "2024-10-30T03:03:28+00:00"
}
],
"username": "TheFabo",
"name_history": [
{
"name": "TheFabo",
"accurate": true,
"changed_at": null,
"last_seen_at": "2026-05-07T00:09:10+00:00"
}
]
},
"status": "success"
}
}About the laby.net API
The laby.net API provides 3 endpoints for accessing Minecraft player data indexed by laby.net, including full profile lookups via the get_profile endpoint that returns UUID, current username, complete name history, and earned badges. It also exposes platform-wide statistics and a featured user roster, covering the key data surfaces laby.net surfaces for the Minecraft community.
Player Profile Lookup
The get_profile endpoint accepts either a Minecraft username (e.g. Player123) or a UUID (e.g. xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) as the identifier parameter. It returns the player's current username, canonical uuid, a badges array, and a name_history array. Each name history entry includes the name, a changed_at timestamp, an accurate boolean indicating confidence in the timestamp, and a last_seen_at field. Badges carry their own uuid, name, description, and a received_at timestamp.
Platform Statistics
The get_statistics endpoint takes no parameters and returns a labynet object. Inside it, a trends object holds profiles and skins sub-objects, each with a count and a velocity figure representing growth rate. A contributions array is also present, reflecting aggregated platform activity data.
Featured Users
The get_featured_users endpoint returns a users array of accounts that laby.net has highlighted on its platform. Each entry includes the user's uuid, name, and their badges array — the same badge structure returned by get_profile.
- Resolve a Minecraft username to a stable UUID for database keying, using the
get_profileidentifier parameter. - Display a player's badge collection and earned achievements in a third-party Minecraft community site.
- Audit a player's complete name history to detect account rebrands or shared username reuse.
- Build a Minecraft player card showing current username, UUID, and laby.net badges.
- Track laby.net platform growth by polling
get_statisticsfor profile and skin count velocity over time. - Populate a featured-player leaderboard or highlight reel using data from
get_featured_users.
| 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 | 250 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 laby.net have an official developer API?+
What does the name_history array in get_profile actually contain?+
name, a changed_at timestamp for when the name change occurred, an accurate flag indicating whether the timestamp is confirmed or estimated, and a last_seen_at date. The array covers all name changes laby.net has recorded for that UUID.Can I look up a player's skin or cape data through this API?+
Can I search for players by badge type or filter featured users by badge?+
get_featured_users returns all featured users with their badges included, but there is no filter parameter to narrow by a specific badge. You can fork this API on Parse and revise it to add filtered badge search functionality.How fresh is the profile data for a given player?+
accurate field on each name_history object.