Sumogames APIsumodb.sumogames.de ↗
Access sumo wrestler profiles, banzuke rankings, kimarite stats, and yusho winners from the Sumo Reference Database via a clean JSON API.
What is the Sumogames API?
This API exposes 5 endpoints covering the Sumo Reference Database at sumodb.sumogames.de, giving developers structured access to wrestler profiles, historical tournament winners, technique breakdowns, and official banzuke ranking sheets. Use search_rikishi to find wrestlers by ring name, then pass the returned numeric ID to get_rikishi_profile for full career data including height, weight, stable, birthplace, and a basho-by-basho history.
curl -X GET 'https://api.parse.bot/scraper/289c1828-b0d6-4d26-af45-202ba31ac1d7/search_rikishi?name=Hakuho' \ -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 sumodb-sumogames-de-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.sumo_reference_api import SumoReference, RikishiSummary, Rikishi, KimariteStats, BanzukeEntry, YushoWinner
sumo = SumoReference()
# Search for wrestlers by ring name
for summary in sumo.rikishisummaries.search(name="Hakuho"):
print(summary.id, summary.shikona, summary.details_url)
# Get full profile for a specific wrestler
rikishi = sumo.rikishis.get(id="1123")
print(rikishi.shikona_full, rikishi.highest_rank, rikishi.career_record)
print(rikishi.height_cm, rikishi.weight_kg, rikishi.heya, rikishi.shusshin)
# Navigate from search result to full profile
for summary in sumo.rikishisummaries.search(name="Terunofuji"):
full_profile = summary.details()
print(full_profile.shikona, full_profile.birth_date, full_profile.hatsu_dohyo)
for record in full_profile.career_history:
print(record.basho, record.rank, record.record)
break
# Get kimarite (technique) statistics for a wrestler
stats = rikishi.kimarite_stats()
print(stats.rikishi_id)
for technique in stats.wins_by_kimarite:
print(technique.kimarite, technique.count)
# Get banzuke for a specific tournament
for entry in sumo.tournament(basho="2024.01").banzuke():
print(entry.id, entry.shikona, entry.height_cm, entry.weight_kg)
# List all yusho (tournament) winners
for winner in sumo.yushowinners.list():
print(winner.basho, winner.makuuchi_winner, winner.makuuchi_winner_id)
Full-text search over sumo wrestlers by shikona (ring name). Returns a list of matching rikishi with their IDs and profile URLs. Matches are partial — searching 'Hakuho' also returns wrestlers whose real names match. Each result carries an id usable with get_rikishi_profile and get_rikishi_kimarite_stats.
| Param | Type | Description |
|---|---|---|
| namerequired | string | Shikona (ring name) of the wrestler to search for. |
{
"type": "object",
"fields": {
"results": "array of matching rikishi objects with id, shikona, and details_url"
},
"sample": {
"data": {
"results": [
{
"id": "1123",
"shikona": "Hakuho",
"details_url": "https://sumodb.sumogames.de/Rikishi.aspx?r=1123"
}
]
},
"status": "success"
}
}About the Sumogames API
Wrestler Search and Profiles
The search_rikishi endpoint accepts a shikona (ring name) string and returns an array of matching wrestlers, each with a numeric id, shikona, and a details_url. Matching is partial — a search for 'Haku' can surface wrestlers whose real names or ring names contain that string. The returned id is the key that unlocks the rest of the API. Pass it to get_rikishi_profile to retrieve physical attributes (height_cm, weight_kg), birth_date, hatsu_dohyo (first tournament, YYYY.MM format), heya (stable), shusshin (birthplace), real_name, and highest_rank with its associated date.
Technique Statistics and Fighting Style
get_rikishi_kimarite_stats accepts the same numeric id and returns two arrays: wins_by_kimarite and losses_by_kimarite. Each entry pairs a technique name (kimarite) with a count. This makes it straightforward to quantify how reliant a wrestler is on specific techniques — for instance, whether a yokozuna wins predominantly by yorikiri (force-out) or uwatenage (overarm throw).
Rankings and Tournament Records
get_banzuke retrieves the official ranking sheet for any historical or current tournament. The basho parameter accepts YYYY.MM or YYYYMM format; tournaments run in January, March, May, July, September, and November. The response includes an array of ranked wrestlers with id, shikona, height_cm, weight_kg, title_raw, and optionally rank. get_yusho_winners requires no parameters and returns every makuuchi division tournament champion in reverse chronological order, each entry containing basho, makuuchi_winner (rank and name string), and makuuchi_winner_id for cross-referencing with the profile endpoints.
The Sumogames API is a managed, monitored endpoint for sumodb.sumogames.de — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when sumodb.sumogames.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 sumodb.sumogames.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 yokozuna career tracker by chaining search_rikishi and get_rikishi_profile to collect highest_rank and hatsu_dohyo across all grand champions.
- Analyze fighting style tendencies by comparing wins_by_kimarite distributions across active wrestlers via get_rikishi_kimarite_stats.
- Reconstruct historical banzuke sheets for any of the six annual tournaments using get_banzuke with a specific YYYY.MM basho parameter.
- Power a yusho history timeline by iterating get_yusho_winners and grouping champion IDs to count total tournament wins per rikishi.
- Cross-reference banzuke weight and height data from get_banzuke to study physical trends across different eras of sumo.
- Build a wrestler comparison tool using height_cm, weight_kg, and kimarite win ratios pulled from profile and stats endpoints.
- Track stable representation across tournaments by aggregating the heya field from multiple get_rikishi_profile calls against a banzuke roster.
| 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.