Supercell Clash of Clans API
Browse all Supercell APIs60
AI ReadinessFoundational (C+)60/100
Official vendor OpenAPI document · agent-readyMaps GeolocationMappingbearer22 EndpointsREST
For Agents
Programmatically get clan information, list clan members. Covers 22 operations with bearer authentication.
Use for: I need to clan information, I want to clan members, Search for clan's clan war log, Find all information about clan's current clan war
Not supported: Does not handle payments, communications, or crm - use for maps and geolocation only.
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.
Install Jentic One Beta
Connect the Clash of Clans API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clash of Clans API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsupercell.com%2Fclash-of-clans-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsupercell.com%2Fclash-of-clans-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Clash of Clans API.
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
Patterns agents use Clash of Clans API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'get clan information', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
22 endpoints — official clash of clans api for accessing game data including clans, players, leagues, locations, and war information.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
C
Clash of Clans API
- Foundational (C+)60/100
76
Foundational Compliance57
Developer Experience & Jentic Compatibility48
AI-Readiness & Agent Experience94
Agent Usability60
Security43
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
76
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A-Signals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
7%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
57
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
26%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
48
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D+Signals: 4
44%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
60
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
60%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
43
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: D-Signals: 1
43%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Clash of Clans API through Jentic.
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.
GET STARTED