As of mid-July, all API requests are now served by a fully rewritten backend. This rewrite closely matches and re-uses parts of our existing codebases, making (future) alignment quicker and easier. We have also observed a significant improvement in response times.

The initial goal of the rewrite was to match the v0 response formats (and quirks) 1:1, which has been delivered. The next step is the v2 API, designed from the ground up based on industry standards, best practices, and generally better aligned with the data we serve.

We recognize the value that is delivered to our players by the various popular API projects. That said, like every engineering organization, we have to prioritize the areas we invest resources in. As maintaining the new API backend is easier, we expect to be able to make future changes and improvements quicker, but we’re unable to commit to any timelines.

All V2 endpoints will require a valid API key. We continue to consider the best approach here that allows legitimate users/creators to easily access and use our public data, without allowing malicious users to use the API to harm our playerbase.

Outside of basic maintenance and important fixes, we do not expect to release any communication about the big changes (V2, auth) until after the public release of SkyBlock Horizons.

You may only request the same player/game combination 3 times per 60 minutes. When this limit is exceeded, you will receive a “Too Many Attempts (game and player combination)” rate limit error.

We are not accepting API key requests until the launch of the V2 endpoints (see V2 blogpost).

The new keys are added to the _unlocked and _equipped cosmetic objects:

edition: the unique purchaser amount editional_total: total units sold

Both keys are optional, and you should support/tolerate any combination of the keys existing and missing.