StarCraft 2 API

Name: StarCraft 2 API API
Brand: StarCraft 2 API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliveryoauth215 EndpointsREST

For Agents

Look up StarCraft 2 player profiles, ladder standings, match history, and league data across Blizzard's regional servers. Useful for esports trackers and tournament agents.

Quickstart

Get started with StarCraft 2 API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"look up a starcraft 2 player profile"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with StarCraft 2 API API.

Look up a StarCraft 2 player profile by region, realm, and profile ID

Fetch the grandmaster ladder for a region with GET /sc2/ladder/grandmaster/{regionId}

Retrieve a player's ladder summary and per-ladder placement

Pull a player's recent match history via the legacy profile endpoints

GET STARTED

Start building with StarCraft 2 API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for StarCraft 2 API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for StarCraft 2 API, keeping it validated and agent-ready. Blizzard's StarCraft 2 API on Battle.net exposes player profiles, ladder rankings, match history, and league standings for the StarCraft II competitive scene. The API is split into community endpoints (profiles, ladders, matches) and game-data endpoints (leagues, seasons), all secured with OAuth 2.0 client-credentials. Regional servers cover US, EU, KR, TW, and a separate China gateway, so client code must select the correct base URL for the player's region.

Use Cases

Patterns agents use StarCraft 2 API API for, with concrete tasks.

★ Esports Ladder Tracker

Tournament organisers and content creators need a live view of grandmaster and master league standings across regions. The StarCraft 2 API exposes GET /sc2/ladder/grandmaster/{regionId} and GET /sc2/ladder/season/{regionId} to pull current leaderboards. The tracker can poll on an interval (respecting Blizzard's rate limits) and surface ranking changes between snapshots.

Call GET /sc2/ladder/grandmaster/2 (EU) and compare results to a stored snapshot to surface rank changes for a Twitch overlay

Player Profile and Match History

Coaches and analysts looking at a specific player can pull their profile, ladder summary, and recent match list to study performance. The legacy match endpoint GET /sc2/legacy/profile/{regionId}/{realmId}/{profileId}/matches returns the player's most recent matches with race, opponent, and result, enabling automated post-game analysis.

Call GET /sc2/profile/1/1/12345 for a player, then GET /sc2/legacy/profile/1/1/12345/matches to retrieve their last 25 matches

Season and League Data Snapshot

Researchers studying StarCraft 2's competitive landscape can call GET /sc2/ladder/season/{regionId} to find the current season ID, then GET /data/sc2/league/{seasonId}/{queueId}/{teamType}/{leagueId} to pull every player in a given league tier. The data feeds dashboards comparing ladder distribution by region and queue.

Call GET /sc2/ladder/season/1 to get the current season ID, then GET /data/sc2/league/{seasonId}/201/0/6 to pull the grandmaster 1v1 league

Agent-Driven Tournament Lookup via Jentic

A Discord bot or stream overlay agent can use the StarCraft 2 API through Jentic to answer commands like 'show me NotPickle's last 5 matches' without the bot author handling OAuth refresh. Jentic isolates the Blizzard client credentials and exposes the 15 SC2 operations as discoverable tools.

Search Jentic for 'starcraft 2 player profile', load the GET /sc2/profile/{regionId}/{realmId}/{profileId} schema, and execute with the requested player's identifiers

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for starcraft 2 api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/sc2/profile/{regionId}/{realmId}/{profileId}

Fetch a StarCraft 2 player profile

GET

/sc2/profile/{regionId}/{realmId}/{profileId}/ladder/summary

Get a player's ladder summary

GET

/sc2/ladder/grandmaster/{regionId}

Get the grandmaster ladder for a region

GET

/sc2/ladder/season/{regionId}

Get the current season for a region

GET

/sc2/legacy/profile/{regionId}/{realmId}/{profileId}/matches

Get a player's recent match history

GET

/data/sc2/league/{seasonId}/{queueId}/{teamType}/{leagueId}

Fetch league composition data

GET

/sc2/profile/{regionId}/{realmId}/{profileId}

Fetch a StarCraft 2 player profile

GET

/sc2/profile/{regionId}/{realmId}/{profileId}/ladder/summary

Get a player's ladder summary

GET

/sc2/ladder/grandmaster/{regionId}

Get the grandmaster ladder for a region

GET

/sc2/ladder/season/{regionId}

Get the current season for a region

GET

/sc2/legacy/profile/{regionId}/{realmId}/{profileId}/matches

Get a player's recent match history

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Battle.net OAuth 2.0 client_id and secret are stored encrypted in the Jentic vault. The vault performs the client-credentials grant and exposes scoped access tokens to the agent — raw secrets never enter the agent's context when calling endpoints like GET /sc2/profile/{regionId}/{realmId}/{profileId}.

Intent-based discovery

Agents search by intent (e.g. 'get a starcraft 2 player profile' or 'fetch the grandmaster ladder') and Jentic returns matching SC2 operations with their input schemas, including the regionId/realmId parameter requirements.

Time to first call

Direct Battle.net integration: 1-2 days for OAuth client setup, regional server selection, and rate-limit handling. Through Jentic: under an hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

BBC Radio & Music Services

Different content domain; included as a placeholder media-API peer in the absence of another esports API

Not a real alternative — listed because the corpus does not currently contain a competing esports/game-stats API.

Complementary

Basesnap API

Database snapshot service — useful for backing up the database that ingests SC2 ladder snapshots

Use Basesnap when the agent needs to back up the warehouse storing SC2 historical data.

Complementary

Baseten API

ML model deployment — pair with SC2 data to serve match-prediction or skill-rating models

Choose Baseten when serving an ML model trained on StarCraft 2 ladder or match data.

FAQs

Specific to using StarCraft 2 API API through Jentic.

Why is there no official OpenAPI spec for StarCraft 2 API?

Blizzard does not publish an OpenAPI specification for the StarCraft 2 API. Jentic generates and maintains this spec so that AI agents and developers can call StarCraft 2 API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the StarCraft 2 API use?

Battle.net uses OAuth 2.0 client credentials. Register an application on the Blizzard developer portal, exchange the client_id/secret for an access token, and pass it as Authorization: Bearer <token>. Through Jentic the credentials live in the vault and the agent only receives a scoped token.

Which regions does the StarCraft 2 API cover?

The API supports four regional servers (US, EU, KR, TW) under https://{region}.api.blizzard.com plus a China gateway at https://gateway.battlenet.com.cn. Most endpoints take a regionId path parameter (1=US, 2=EU, 3=KR, 5=CN) so make sure the host and regionId match.

How do I look up a StarCraft 2 player profile through Jentic?

Search Jentic for 'starcraft 2 player profile', which surfaces GET /sc2/profile/{regionId}/{realmId}/{profileId}. Load the schema, supply regionId, realmId, and profileId, and execute. The response includes career stats, season highlights, and rewards.

What are the rate limits for the StarCraft 2 API?

Blizzard applies per-account rate limits (commonly 100 requests/second and 36,000 per hour) across all Battle.net APIs. The OpenAPI spec does not enumerate them — check the Blizzard developer portal for current limits and back off on 429 responses.

Can I get a player's match history with the StarCraft 2 API?

Yes, via the legacy match endpoint: GET /sc2/legacy/profile/{regionId}/{realmId}/{profileId}/matches. It returns the player's most recent matches with race, map, opponent, and result. The endpoint is labelled legacy by Blizzard but remains the canonical source for SC2 match history.