canonical: https://jentic.com/apis/supercell.com/clash-of-clans-api

# Supercell Clash of Clans API

Official Clash of Clans API for accessing game data including clans, players, leagues, locations, and war information. The API exposes 22 endpoints secured with bearer authentication.

## For AI agents

Programmatically get clan information, list clan members. Covers 22 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for maps and geolocation only.

## Capabilities

- Get clan information
- List clan members
- Retrieve clan's clan war log
- Search clans
- Monitor Clash of Clans API operational status and events

## Use cases

### Maps and Geolocation Operations

Use the Clash of Clans API to perform maps geolocation operations programmatically. The API provides 22 endpoints covering core functionality including get clan information, list clan members, retrieve clan's clan war log.

Example prompt: Call GET /clans/{clanTag} to get clan information

### Automated Clans Management

Automate clans operations by combining multiple Clash of Clans API endpoints. Agents can list clan members and then retrieve clan's clan war log in a single workflow.

Example prompt: Call GET /clans/{clanTag}/members to list clan members, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Clash of Clans API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.

Example prompt: Search Jentic for 'get clan information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /clans/{clanTag} | Get clan information |
| GET | /clans/{clanTag}/members | List clan members |
| GET | /clans/{clanTag}/warlog | Retrieve clan's clan war log |
| GET | /clans/{clanTag}/currentwar | Retrieve information about clan's current clan war |
| GET | /clans/{clanTag}/currentwar/leaguegroup | Retrieve information about clan's current war league group |
| GET | /clanwarleagues/wars/{warTag} | Retrieve information about individual clan war league war |
| GET | /clans | Search clans |
| GET | /players/{playerTag} | Get player information |

## Key resources

- **Clans** — Operations for clans
- **Clanwarleagues** — Operations for clanwarleagues
- **Labels** — Operations for labels
- **Leagues** — Operations for leagues
- **Locations** — Operations for locations

## Why Jentic

- **Setup:** Wiring the Clash of Clans API by hand means handling its bearer token auth against api.clashofclans.com and managing retries yourself. Through Jentic you install once, import the Clash of Clans API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Clash of Clans API puts the clan and player tags in the URL path (/clans/{clanTag}, /players/{playerTag}), so a rule can pin your agent to one clan or one player: it can read that resource and nothing else. Every operation here is a read, so the agent only ever fetches data you allow it to reach.
- **Credential handling:** Your Clash of Clans API bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get clan information' or 'read a current war', and Jentic returns the matching Clash of Clans API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Here** — Alternative maps geolocation API
- **Tomtom** — Alternative maps geolocation API
- **Googleapis** — Complementary maps geolocation API

## FAQ

### What authentication does the Clash of Clans API use?

The Clash of Clans API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get clan information with the Clash of Clans API?

Yes. Use the GET /clans/{clanTag} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Clash of Clans API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get clan information through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get clan information'. Jentic returns the matching Clash of Clans API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Clash of Clans API have?

The Clash of Clans API exposes 22 endpoints covering clans, clanwarleagues, labels operations.

### Can I limit what my agent is allowed to do with the Clash of Clans API?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials your agent may use. Because the Clash of Clans API carries the clan and player identifiers in the URL path, such as GET /clans/{clanTag} and GET /players/{playerTag}, you can pin your agent to a single clan or player and let it reach nothing else. Every operation here is a read, so the agent only ever fetches the data you allow, never writes or deletes.