Supercell Clash Royale API
Browse all Supercell APIs★ Only Publicly Available OpenAPI DocumentSocial MediaSocial Managementbearer21 EndpointsREST
For Agents
Programmatically search clans, get clan information. Covers 21 operations with bearer authentication.
Use for: I need to clans, I want to clan information, Search for clan members, Find all clan's clan war log
Not supported: Does not handle payments, communications, or crm - use for social media only.
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.
Install Jentic One Beta
Connect the Clash Royale API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Clash Royale 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Royale API.
Search clans
Get clan information
List clan members
Retrieve clan's clan war log
Information about clan's current clan war
Use Cases
Patterns agents use Clash Royale API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'search clans', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
21 endpoints — provides access to clash royale game data including player profiles, clans, tournaments, cards, and game locations.
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
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
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
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.
Intent-based discovery
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.
Time to first call
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Clash Royale API through Jentic.
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.
GET STARTED