Laby APIlaby.net ↗
Retrieve Minecraft player profiles, UUID lookups, name history, badges, and laby.net platform statistics via a simple REST API.
What is the Laby 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.
curl -X GET 'https://api.parse.bot/scraper/6ab8df1c-ccdb-4aa1-a8a8-3986f96e9bf1/get_profile?identifier=Notch' \ -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 laby-net-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.
from parse_apis.laby_net_api import Laby, Profile, Featured, Statistic, ProfileNotFound
laby = Laby()
# Get global site statistics
stats = laby.statistics.get()
print(stats.labynet.trends.profiles.amount, stats.labynet.trends.profiles.velocity)
print(stats.labynet.trends.skins.amount, stats.labynet.trends.skins.velocity)
# Look up a specific player profile by username or UUID
profile = laby.profiles.get(identifier="Notch")
print(profile.uuid, profile.username)
for entry in profile.name_history:
print(entry.name, entry.changed_at, entry.last_seen_at)
for badge in profile.badges:
print(badge.name, badge.description, badge.received_at)
# List featured community users and their badges
for user in laby.featureds.list():
print(user.uuid, user.name)
for badge in user.badges:
print(badge.name, badge.description)
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 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.
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 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 | 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 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.