There's a lot to go over here.

API Key breaking

Your old API keys will not work anymore as the way we're generating and validating the keys have changed, along with the storage methods for them and as such, they're completely incompatible with the new API.

How to migrate

It's simple! Instead of sending your old API key, you send your new key, and instead of reading the JSON data directly, you read the JSON data's data property in order to get the same data as before. For example instead of getting

{
    "adventures": 170768,
    "guilds": 11138,
    "servers": 63132,
    "users": 445127
}

you'll be getting

{
    "status": 200,
    "data": {
        "adventures": 170768,
        "guilds": 11138,
        "servers": 63132,
        "users": 445127
    }
}

API Dashboard

A big part of the new API is our API Dashboard which we've added.

Instead of constantly asking the support team for an API key, we wanted to allow users to generate the keys themselves in order to reduce the load on the team and to make the API more accessible to everyone. This also helps us with keeping track of all the keys whilst also letting us manage individual ratelimits for keys.

Technical write-up

Coming soon in a later post.