Supercell Brawl Stars API

Name: Brawl Stars API
Brand: Brawl Stars API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource Controlbearer9 EndpointsREST

Install Jentic One Beta

Connect the Brawl Stars API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Brawl Stars 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.

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 | sh

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 instance

Jentic 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 Brawl Stars API.

Get player information

Manage developer tools data programmatically

Integrate Brawl Stars API into automated workflows

Query and filter Brawl Stars API records by parameters

GET STARTED

Start building with Brawl Stars API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Brawl Stars API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'get player information', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

9 endpoints — official brawl stars api for accessing game data including players, clubs, rankings, and brawler information.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Brawl Stars API through Jentic.

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.