HeLO System APIhelo-system.de ↗
Access HeLO competitive Hell Let Loose data: team rankings, match history, player stats, and series info via 5 structured JSON endpoints.
What is the HeLO System API?
The HeLO System API exposes 5 endpoints covering competitive Hell Let Loose clan data from helo-system.de, including team rankings, full match histories, and per-player statistics. The get_match_detail endpoint returns granular per-player kill, death, and performance metrics alongside team assignments, cap layouts, and gamemode metadata for any single match. Use list_series to enumerate available seasons and pass series tags to filter results across all other endpoints.
curl -X GET 'https://api.parse.bot/scraper/323ae114-81d1-45a4-83fc-94ef2a9a4ac0/search_teams?query=VLK' \ -H 'X-API-Key: $PARSE_API_KEY'
List and search competitive Hell Let Loose teams registered in the HeLO system. Returns all teams for the given series, optionally filtered by a case-insensitive substring match on team tag or name. Teams are returned sorted by ranking score descending. Each team includes its tag, name, HeLO score, match count, and ranking status.
| Param | Type | Description |
|---|---|---|
| query | string | Case-insensitive search substring matched against team tag and name. Omitting returns all teams. |
| series | string | The competitive series/season identifier. Obtain available values from list_series. |
{
"type": "object",
"fields": {
"teams": "array of team objects with tag, name, score, num_matches, ranking, icon, inactive",
"total": "integer count of teams in the result"
},
"sample": {
"data": {
"teams": [
{
"tag": "VLK",
"icon": "https://floriansw.github.io/helo-team-images/teams/vlk_128px.png",
"name": "Valkyria",
"score": 22.2394743313929,
"ranking": "ranked",
"inactive": false,
"num_matches": 42
}
],
"total": 1
},
"status": "success"
}
}About the HeLO System API
Teams and Rankings
The search_teams endpoint returns all teams registered in the HeLO ranking system for a given series, sorted by score descending. An optional query parameter filters by a case-insensitive substring matched against both the team tag and name. Each team object includes ranking, num_matches, icon, and an inactive flag. The series parameter — sourced from list_series — scopes results to a specific competitive season.
Match History
get_team_matches retrieves a paginated match log for a specific team identified by its exact tag. Each match record includes match_id, date, opponent, map, score, faction (Axis or Allies), result, type, tournament, duration, status, and caps. Pagination is handled via limit, offset, and the next_offset field in the response. get_player_matches works similarly but queries by steam_id, returning matches across all types (competitive, friendly, event) with per-match performance fields: kills, deaths, kpm, dpm, cpm, spm, and percentile_side. The response also surfaces the player's recorded display_names with the current name listed first, and all teams the player has been associated with.
Match Detail
get_match_detail accepts a match_id (obtainable from get_team_matches or get_player_matches) and returns the full record for that match: map, date, score, duration, gamemode, type, status, axis_team, cap point layout, aggregated kill statistics per side, and individual player-level statistics. This is the deepest data layer in the API.
Series and Seasons
list_series requires no inputs and returns all available series with their tag, name, and a current boolean indicating the active season. Pass tag values from this endpoint to the series parameter on all other endpoints to scope queries to the correct competitive season.
The HeLO System API is a managed, monitored endpoint for helo-system.de — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when helo-system.de 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 helo-system.de 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 clan leaderboard sorted by HeLO ranking score across a specific series
- Track a team's win/loss record and map pool by parsing get_team_matches results
- Look up a player's kill-per-minute and death-per-minute trends across competitive seasons
- Identify all display names a player has used by inspecting the display_names array from get_player_matches
- Compare Axis vs. Allies kill aggregates for a specific match using get_match_detail
- Display a team's cap point control layout per match using the caps array in match responses
- Enumerate all available competitive seasons programmatically with list_series before querying historical data
| 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 helo-system.de have an official developer API?+
What does get_match_detail return beyond the basic score?+
How does pagination work for team and player match history?+
limit and offset parameters. The response includes a next_offset field: if not null, pass it as the offset on the next request to retrieve the following page. get_team_matches clamps limit to 1–100; get_player_matches clamps it to 1–200.Does the API expose individual player profiles or career statistics aggregated across all seasons?+
Can I filter get_team_matches by map or result type?+
tag, series, limit, and offset. The map and result fields are present in each match object in the response, so client-side filtering is possible. You can fork this API on Parse and revise it to add server-side map or result filtering to the endpoint.