HLLRecords APIhllrecords.com ↗
Search Hell Let Loose players and retrieve combat stats, K/D ratios, ELO ratings, win rates, and playstyle data via the HLLRecords.com API.
What is the HLLRecords API?
The HLLRecords.com API provides two endpoints for querying Hell Let Loose player data: search players by username and retrieve detailed profiles containing 10+ fields including enemy kills, team kills, K/D ratio, ELO rating, win rate, and level. The get_player_profile endpoint supports time-period filters ranging from 30 days to full lifetime stats, making it suitable for tracking performance trends over specific seasons or patches.
curl -X GET 'https://api.parse.bot/scraper/2d54c33e-03d9-4f5e-9ebe-571b6c0de49c/search_players?query=soldier' \ -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 hllrecords-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: HLLRecords SDK — bounded, re-runnable; every call capped."""
from parse_apis.HLLRecords_Player_Data_API import HLLRecords, Period, PlayerNotFound
client = HLLRecords()
# Search for players by username
for player in client.player_summaries.search(query="soldier", limit=3):
print(player.name, player.external_id, player.last_seen)
# Drill-down: get detailed profile for the first matching player
hit = client.player_summaries.search(query="soldier", limit=1).first()
if hit:
try:
profile = hit.profile.get(period=Period._365D)
print(profile.name, profile.level, profile.kd_ratio)
print(profile.win_rate, profile.faction_preference)
if profile.playstyle_stats:
print(profile.playstyle_stats.kpm, profile.playstyle_stats.duel_strength)
except PlayerNotFound as e:
print("player gone:", e.player_id)
print("exercised: player_summaries.search, profile.get")
Search for Hell Let Loose players by username. Returns a list of matching players with their external IDs, names, last seen timestamps, and avatar URLs.
| Param | Type | Description |
|---|---|---|
| queryrequired | string | Player username or partial username to search for (e.g. 'soldier', 'sniper'). |
{
"type": "object",
"fields": {
"count": "integer - number of matching players",
"players": "array of player objects with external_id, name, last_seen, last_seen_name, avatar"
},
"sample": {
"data": {
"count": 1,
"players": [
{
"name": "John Doe",
"avatar": "https://avatars.steamstatic.com/fef49e7fa7e1997310d705b2a6158ff8dc1cdfeb_full.jpg",
"last_seen": "2026-06-25T15:44:44Z",
"external_id": "76561199384752782",
"last_seen_name": "John Doe"
}
]
},
"status": "success"
}
}About the HLLRecords API
Player Search
The search_players endpoint accepts a full or partial username string and returns a list of matching players. Each result includes the player's external_id (Steam ID or hash), display name, last_seen timestamp, last_seen_name, and avatar URL. The external_id returned here is the required input for fetching a full profile.
Player Profiles and Combat Statistics
The get_player_profile endpoint accepts a player_id (obtained from search_players) and an optional period parameter. Valid period values are 30d, 90d, 180d, 365d, and 2025; omitting the parameter returns lifetime statistics. The response includes enemy_kills, team_kills, kd_ratio, win_rate, level, first_seen, steam_id, avatar, and player_id. The name field reflects the player's current display name, while the search endpoint's last_seen_name can differ if the player has renamed.
Data Coverage and Identifiers
Player identity is anchored to a Steam ID, so records persist across username changes. The first_seen field marks when HLLRecords first logged activity for the account, providing a rough tenure signal. All numeric stats — kills, ratios, rates — are returned as strings, so downstream code should cast them before arithmetic operations.
The HLLRecords API is a managed, monitored endpoint for hllrecords.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when hllrecords.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 hllrecords.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?+
- Build a Hell Let Loose stat tracker that compares K/D ratios and win rates across time periods
- Identify smurf or alternate accounts by cross-referencing
last_seen_namehistory against Steam IDs - Integrate player ELO and level data into a community tournament seeding tool
- Monitor a squad's enemy kill counts and team kill rates over rolling 30-day windows
- Look up a player's
first_seendate to estimate account age before accepting a clan application - Aggregate win rate and K/D data across multiple players to rank a unit's overall performance
| 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 HLLRecords.com have an official developer API?+
What does the `period` parameter in `get_player_profile` actually filter?+
period parameter restricts the returned combat statistics to a specific time window. Accepted values are 30d, 90d, 180d, 365d, and 2025 (a calendar-year filter). Omitting it returns lifetime aggregated stats. All other response fields — name, level, steam_id, avatar — are not time-scoped.Does the API return match history or individual game logs?+
Can I filter the `search_players` results by level, ELO, or win rate?+
search_players endpoint only accepts a username query string; it does not support filtering by level, ELO, or win rate. Those fields are available in get_player_profile responses after you retrieve a specific player. You can fork this API on Parse and revise it to add server-side filtering logic once profiles are fetched.