Introduction

Welcome to RoyaleAPI, the unofficial public API for Clash Royale! You can use our API to access Clash Royale API endpoints, which provides real-time information about players, clans, clan wars, tournaments and more.

Note

We have sunsetted our public API starting on March 1st, 2020. Our website for end users will not be affected. Please read our blog post for full details.

Proxy IP Update 2022-02-08

Supercell made some changes with how tokens are handled. Because of this, the proxy will no longer work with 128.128.128.128 but you can create a new key with 45.79.218.79.

You can see implementations of this API in Showcase by third-party developers and on our web site: https://royaleapi.com

Wrappers in multiple languages are also available.

If you are new to development using REST APIs, we recommend that you try out Postman, which provides many useful tools for your daily development needs.

If you find this API useful, please consider donating so we can continue to provide this service free of charge to everyone.

Note

The JSON structure may change over time. Please follow our Twitter @RoyaleAPI or join our Discord server for important updates.

Documentation

Note

The popular and tournament related endpoints are currently not implemented and will return a 501 Not Implemented error.

• Getting Started
  • Introduction
  • Authentication
  • Errors
  • Showcase
  • Wrappers
  • FAQ
  • Donate
• Endpoints
  • Version
  • Constants
  • Player
  • Player Battles
  • Player Chests
  • Clan Search
  • Clan
  • Clan Battles
  • Clan War
  • Clan War Log
  • Clan History
  • Clan Weekly History
  • Clan Tracking
  • Top Clans
  • Top Players
  • Top War Clans
  • Endpoints

Support + Feature Requests

If you have a suggestion or an issue to report, please use the issue tracker. We recommend that you search the issue tracker to check if someone else has already reported the issue and whether there is a known solution that you can use. This probably is the fastest way for you to find a solution to any issue that you are facing.

If you are adding a bug report, please add steps to reproduce the bug, exact request (method and URL) and response (including response code). Any additional information (console errors, screenshots) would be helpful.

Community

If you are interested in talking to the team, we are there on Discord. Feel free to drop by and say hello. Our upcoming features and beta releases are discussed here along with deck advice and Die Hard quotes.

Join our Discord Server at: https://discord.royaleapi.dev

We are also available as @RoyaleAPI on Twitter. Feel free to drop in a line wherever it is easiest for you. Twitter would be the best place for you to stay updated with latest news, features and releases regarding RoyaleAPI.

Authors

	Selfish	SML
Github	Selfish	smlbiobot
Twitter	@selfishio	@seeminglee

Repositories

Name	URL	Description
Main	https://github.com/RoyaleAPI/cr-api	Feature requests, bug reports, etc.
Assets	https://github.com/RoyaleAPI/cr-api-assets	Image assets for cards, arenas, etc.
Data	https://github.com/RoyaleAPI/cr-api-data	Constants as JSON.
Docs	https://github.com/RoyaleAPI/cr-api-docs	Documentation.
UX	https://github.com/RoyaleAPI/cr-api-docs	User experience, website feature request, family configs.

Social

Name	URL	Description
Discord (Dev)	https://discord.me/RoyaleAPI	Community support and status updates
Discord (UX)	https://discord.royaleapi.com	UX and end-user support for non-developers
Twitter	https://twitter.com/RoyaleAPI	Status updates.
Facebook	https://facebook.com/RoyaleAPI	Fan page.