Data Sources
Last updated: June 2025
Why This Page Exists
Every recommendation SnapPick shows you is only as good as the data behind it. This page documents every external source we use, what data we pull from each, how often it is updated, and any known limitations. We believe players have the right to know exactly where our numbers come from.
Supercell Official API
Supercell OyBrawl Stars and Clash Royale
Official REST API — requires a registered developer key
The Supercell API is the source of truth for all player-specific data on SnapPick. We use it exclusively to fetch information tied to your player tag. No data from the Supercell API is stored persistently on our servers beyond your active session.
| Data type | Used for | Update cadence |
|---|---|---|
| Player profile (CR) | Card collection, card levels, current deck, exp level | Real-time on request (pulled fresh each session) |
| Battle log (CR) | Deck tracking, win rate analysis, opponent threat scoring | Real-time on request (last 25 battles) |
| Player profile (BS) | Brawler roster, power levels, gadgets, star powers, trophies | Real-time on request |
| Battle log (BS) | Map performance, brawler usage, result history | Real-time on request (last 25 battles) |
Supercell's public API does not expose gold, gems, star points, or detailed trophy road progress. SnapPick cannot show these values without the player entering them manually.
BrawlAPI
BrawlAPI (community-maintained)Brawl Stars
brawlapi.com brawlapi.com
BrawlAPI provides aggregated statistics and enriched game data not available in the official Supercell API. SnapPick uses BrawlAPI as its primary source for map-level and mode-level brawler performance statistics.
| Data type | Used for | Update cadence |
|---|---|---|
| Brawler win rates by map and mode | Primary scoring signal in brawler pick recommendations | Synced on our backend daily; source updates after major patches |
| Event rotation and map schedule | Live events display, time-until-rotation chips | Real-time on request |
| Brawler metadata (roles, gadgets, star powers) | Role-coverage scoring, mastery path engine | Synced on our backend after each game update |
Internal Curated Data
Some data used by SnapPick is curated and maintained internally, because no reliable external API covers it at the required fidelity. This data is assembled by the SnapPick team and stored in our codebase as versioned JSON files.
| Dataset | Contents | Review cadence |
|---|---|---|
| Clash Royale meta decks | 8 curated meta decks with archetype labels, card lists, and playstyle descriptions. Sourced from top-ladder observation and community consensus. | Reviewed after each balance patch; updated when tier shifts occur |
| Clash Royale archetype definitions | Archetype labels, win condition cards, counter relationships, playstyle descriptions in 6 languages. | Reviewed quarterly or after major meta shifts |
| Card metadata and counters | Per-card counters, synergy pairs, recommended upgrade order, and role tags. Used in deck weakness analysis and upgrade priority. | Reviewed after each balance patch |
| Brawl Stars mode profiles | Per-mode role requirements and scoring weights (e.g. which brawler roles are advantaged in Brawl Ball vs. Bounty vs. Gem Grab). | Reviewed after each seasonal update or major mode change |
When internal curated data has not been reviewed following the latest patch, affected recommendations display a staleness indicator.
What We Do Not Use
- Third-party scraping. We do not scrape game clients, unofficial endpoints, or any data source that violates Supercell's Terms of Service.
- User-contributed win rates. We do not aggregate battle outcomes submitted by SnapPick users to build win-rate databases. Our statistics come from official or community-maintained public APIs.
- Paid data feeds. We do not purchase proprietary game data from any third party.
Reporting a Data Error
If you notice a recommendation that uses clearly wrong data (outdated card stats, wrong win rates, missing brawlers post-patch), please contact us at snappickapp@gmail.com with the specific data point and a source. We treat data errors as high-priority bugs.