Critical Ops Public API

The Critical Ops Public API lets third-party developers integrate data from Critical Ops into their projects, such as websites, Discord bots and other applications. If you plan to use the API in your project, make sure the project follows the terms of use below.

Access to the API is granted with API tokens. You can create a token in the game client, in the token management menu of the game settings. Only linked accounts can create tokens, and banning an account revokes its tokens.

Each project must use its own token. Tokens have rate limits, which can be raised for large projects if necessary. Tokens can also have special permissions that give access to restricted endpoints; at the moment, only trusted partners get these permissions.

The API is described by an OpenAPI specification, which lets you generate client code automatically. The OpenAPI specification always describes the latest version of the game: shortly before a game update is released, it switches to the new version.

Public API terms of use

By using the API, you agree to these terms and to our Terms of Use. Anything you publish with data from the API must also follow our Fan Content Policy.
Keep your API token secret. You are responsible for every request made with it, so call the API from your own server, never from a browser or app where others can see the token.
Stay within the rate limit of your token and don’t try to get around it, for example with several tokens. Cache responses instead of requesting the same data again.
Don’t use the API for cheating, for harassing or impersonating players, or for anything that harms the game, its players or Critical Force.
The API is provided as is. It may change, be limited or stop at any time, and Critical Force may revoke any token, for example breach of the aforementioned terms.

Critical Ops Public API

Public API terms of use

API reference