canonical: https://jentic.com/apis/supercell.com

# Supercell APIs

Supercell publishes official game data APIs for its mobile titles Clash of Clans, Clash Royale, and Brawl Stars. Each API exposes read-only access to player profiles, clans and clubs, war logs, rankings, and card or brawler data, secured with a bearer token. Together they let developers and agents pull live competitive game data across Supercell's three flagship games from a single portfolio.

## For AI agents

An agent can look up player profiles, clan and club information, member lists, war and battle logs, and country rankings across Clash of Clans, Clash Royale, and Brawl Stars. All operations are reads, so agents fetch and compare competitive game data without changing anything in the games.

## Scope

Use for: Reading live player, clan, club, war, ranking, and card data across Clash of Clans, Clash Royale, and Brawl Stars.

Not supported:
- writing game data
- payments
- player messaging
- matchmaking control
- real-time streaming

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Clash of Clans API | maps-geolocation | 22 | Programmatically get clan information, list clan members. |
| Clash Royale API | social-media | 21 | Programmatically search clans, get clan information. |
| Brawl Stars API | developer-tools | 9 | Programmatically get player information, get player battle log. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Read Clash of Clans clan, war, and player data | clash-of-clans | Covers clans, war logs, war leagues, leagues, locations, and player profiles for Clash of Clans. |
| Read Clash Royale clan, tournament, and player data | clash-royale | Adds tournaments, cards, and river race logs alongside clan and player lookups specific to Clash Royale. |
| Read Brawl Stars player, club, and brawler data | brawl-stars | Uses clubs instead of clans and exposes brawler rankings and lists unique to Brawl Stars. |

## Cross-API use cases

### Cross-game player profile lookup

Pull a player's profile from more than one Supercell game by their player tag to build a combined view of their competitive activity across titles.

Example prompt: Call GET /players/{playerTag} on Clash of Clans and GET /players/{playerTag} on Clash Royale, then merge the two profiles into one summary.

### Multi-game clan and club standings

Compare a community's competitive standings across games by reading clan rankings from one title and club rankings from another for the same country.

Example prompt: Call GET /rankings/{countryCode}/clubs on Brawl Stars and the clan ranking endpoint on Clash Royale, then rank the results side by side.

### Unified war and battle activity report

Assemble a report of a group's recent competitive activity by reading clan war logs from Clash of Clans and player battle logs from Brawl Stars.

Example prompt: Call GET /clans/{clanTag}/warlog on Clash of Clans and GET /players/{playerTag}/battlelog on Brawl Stars, then combine both into an activity timeline.

## Why Jentic

- **Setup:** Wiring these APIs by hand means handling a separate bearer token for each game against three different base hosts and managing retries yourself. With Jentic One installed, your agent finds and adds any of the Supercell APIs from the Jentic directory, and you store each token once.
- **Permission scoping:** Every operation across the three APIs is a read, and player and clan tags sit in the URL path, so your own rules in your Jentic One instance can pin the agent to specific games, clans, or players and let it fetch nothing else.
- **Credential handling:** Each game's bearer token is stored encrypted by your own Jentic One instance and injected only at execution time, so raw tokens never enter the agent's prompt, logs, or context.
- **Discovery method:** An agent searches the Jentic directory by intent such as 'get clan information' or 'read a player battle log', and Jentic returns the matching Supercell operation with its input schema so the agent calls the right endpoint across the right game without reading reference docs.

## Related vendors

- **Riot Games** — Offers official game data APIs for League of Legends and other titles, similar player and match data model.
- **Steam** — Provides player, achievement, and game stats APIs across a large catalog of PC games.
- **Blizzard** — Publishes official game data APIs for its titles with player profile and ranking endpoints.

## FAQ

### Which games does the Supercell portfolio cover?

The portfolio covers three official game data APIs: Clash of Clans, Clash Royale, and Brawl Stars. Each exposes read-only access to that game's players, clans or clubs, and competitive data.

### Can one credential access all three Supercell APIs?

No. Each game issues its own bearer token from its developer portal, so an agent needs a separate token for Clash of Clans, Clash Royale, and Brawl Stars. The tokens are not interchangeable.

### Can agents change game state through these APIs?

No. Every operation across the three APIs is a read. Agents can fetch player, clan, war, and ranking data but cannot modify accounts, join clans, or affect matchmaking.

### How consistent are the APIs across the three games?

The APIs share a common shape: player tags and clan tags are the primary keys, responses are JSON, and access uses a bearer token. Brawl Stars uses clubs where the others use clans, and each game adds resources specific to it such as tournaments, cards, or brawlers.

### What kind of data can an agent combine across the games?

An agent can pull the same player or community across titles, compare clan and club rankings by country, and merge war logs and battle logs into a single activity report, since the three APIs share tags and response structures.

### Are these the official Supercell APIs?

The Clash of Clans and Brawl Stars specs are vendor-official, and the Clash Royale spec is sourced from a third party. All three describe Supercell's own public game data endpoints.