canonical: https://jentic.com/apis/supercell.com/brawl-stars-api

# Supercell Brawl Stars API

Official Brawl Stars API for accessing game data including players, clubs, rankings, and brawler information. The API exposes 9 endpoints secured with bearer authentication.

## For AI agents

Programmatically get player information, get player battle log. Covers 9 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get player information
- Manage developer tools data programmatically
- Integrate Brawl Stars API into automated workflows
- Query and filter Brawl Stars API records by parameters
- Monitor Brawl Stars API operational status and events

## Use cases

### Developer Tools Operations

Use the Brawl Stars API to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including get player information, get player battle log, get club information.

Example prompt: Call GET /players/{playerTag} to get player information

### Automated Brawlers Management

Automate brawlers operations by combining multiple Brawl Stars API endpoints. Agents can get player battle log and then get club information in a single workflow.

Example prompt: Call GET /players/{playerTag}/battlelog to get player battle log, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Brawl Stars 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 player information', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /players/{playerTag} | Get player information |
| GET | /players/{playerTag}/battlelog | Get player battle log |
| GET | /clubs/{clubTag} | Get club information |
| GET | /clubs/{clubTag}/members | Get club members |
| GET | /rankings/{countryCode}/players | Get player rankings |
| GET | /rankings/{countryCode}/clubs | Get club rankings |
| GET | /rankings/{countryCode}/brawlers/{brawlerId} | Get brawler rankings |
| GET | /brawlers | Get brawlers list |

## Key resources

- **Brawlers** — Operations for brawlers
- **Clubs** — Operations for clubs
- **Players** — Operations for players
- **Rankings** — Operations for rankings

## Why Jentic

- **Setup:** Wiring the Brawl Stars API by hand means handling its bearer token auth against api.brawlstars.com and managing retries yourself. Through Jentic you install once, import the Brawl Stars API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Brawl Stars API puts the player and club tags in the URL path (/players/{playerTag}, /clubs/{clubTag}), so a rule can pin your agent to one player or one club: 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 Brawl Stars 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 player information' or 'read a club battle log', and Jentic returns the matching Brawl Stars API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Brawl Stars API use?

The Brawl Stars 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 player information with the Brawl Stars API?

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

### What are the rate limits for the Brawl Stars 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 player information through Jentic?

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

### How many endpoints does the Brawl Stars API have?

The Brawl Stars API exposes 9 endpoints covering brawlers, clubs, players operations.

### Can I limit what my agent is allowed to do with the Brawl Stars API?

Yes. Because you run Jentic One yourself, your own rules decide which Brawl Stars API operations and credentials your agent may use. Every operation here is a read, and the API carries the player and club tags in the URL path (/players/{playerTag}, /clubs/{clubTag}), so you can pin the agent to a single player or club and let it fetch only that resource. It can never write data or reach players, clubs, or rankings you have not allowed.