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

# Supercell Clash Royale API

Provides access to Clash Royale game data including player profiles, clans, tournaments, cards, and game locations. The API exposes 21 endpoints secured with bearer authentication.

## For AI agents

Programmatically search clans, get clan information. Covers 21 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for social media only.

## Capabilities

- Search clans
- Get clan information
- List clan members
- Retrieve clan's clan war log
- Information about clan's current clan war

## Use cases

### Social Media Operations

Use the Clash Royale API to perform social media operations programmatically. The API provides 21 endpoints covering core functionality including search clans, get clan information, list clan members.

Example prompt: Call GET /clans to search clans

### Automated clans Management

Automate clans operations by combining multiple Clash Royale API endpoints. Agents can get clan information and then list clan members in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Clash Royale 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 'search clans', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /clans | Search clans |
| 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 | Information about clan's current clan war |
| GET | /clans/{clanTag}/currentriverrace | Information about clan's current river race |
| GET | /clans/{clanTag}/riverracelog | Retrieve clan's river race log |
| GET | /players/{playerTag} | Get player information |

## Key resources

- **clans** — Clan related operations
- **players** — Player related operations
- **cards** — Card related operations
- **tournaments** — Tournament related operations
- **locations** — Location related operations

## Why Jentic

- **Setup:** Wiring the Clash Royale API by hand means handling its bearer token auth against api.clashroyale.com and managing retries yourself. Through Jentic you install once, import the Clash Royale API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Clash Royale 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 Royale 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 'search clans' or 'read a river race log', and Jentic returns the matching Clash Royale API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Facebook** — Alternative social media API
- **Twitter** — Alternative social media API
- **Linkedin** — Complementary social media API

## FAQ

### What authentication does the Clash Royale API use?

The Clash Royale 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 search clans with the Clash Royale API?

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

### What are the rate limits for the Clash Royale 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 search clans through Jentic?

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

### How many endpoints does the Clash Royale API have?

The Clash Royale API exposes 21 endpoints covering clans, players, cards operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Clash Royale API operations and credentials the agent may use. Since the clan and player tags sit in the URL path (/clans/{clanTag}, /players/{playerTag}), you can pin the agent to a single clan or player so it reads that resource and nothing else. Every operation here is a read, such as GET /clans and GET /players/{playerTag}, so the agent only ever fetches the data you allow it to reach.