Add a Guild Wars 2 API key

Most of Aleeva's features rely on your Guild Wars 2 API key. You add it to Aleeva once and it works on every server that uses her, because the key is tied to your Discord account, not to a single server.

Steps

1. Run in any channel, or in a DM with Aleeva. Only you can see the reply.
2. Create a key on the Guild Wars 2 applications page. Give it the permissions account, builds, characters, inventories, wallet, progression, unlocks and wvw. You cannot change these later, so tick them all now.
3. Click Add new Api-Key, paste your key into the popup, and submit.
4. Aleeva verifies the key and replies Api Key got successfully added to your profile.

That's it. You can now use every command that needs a key, and on servers where Aleeva manages roles or nicknames you will get whatever matches your account.

Full key or light key?

A full key unlocks every feature and needs all eight permissions listed above.

If you only want to get verified, a light key is enough. Click Add new Light Api Key instead, confirm the warning with I'm sure, and paste a key that has just the account and wvw permissions.

For why Aleeva asks for each permission, see Discord permissions.

Troubleshooting

"The provided text seems not to be an api key." What you pasted is not in the shape of a key. Copy it again from the applications page, and make sure you took the key itself rather than its name.

"This key not valid." ArenaNet does not recognise the key. This usually means it was deleted on the applications page after you copied it, or a character got lost in the copy. Create a fresh key and paste that.

"This key is valid but is missing some essential permissions." The key works, but not every permission is ticked. Aleeva lists which ones your key does have. Permissions cannot be added to an existing key, so create a new one with all eight ticked: account, builds, characters, inventories, wallet, progression, unlocks and wvw.

"The api key could not be verified." Aleeva could not reach a verdict, usually because the Guild Wars 2 API is having trouble. Check and try again in a few minutes. If it keeps failing, ask on the support server.

"This key is already assigned to your profile." You pasted a key Aleeva already has. Nothing to do.

"This account is already assigned to your profile." You already have a key for that Guild Wars 2 account. If the new key grants permissions the old one is missing, or the old one has gone invalid, Aleeva replaces it and tells you so. If you instead want to move to a key with fewer permissions, remove the old key first with .

"You already have the max amount of keys assigned to your profile." You can link three Guild Wars 2 accounts. Remove one with to make room. Replacing the key of an account you already have does not count against this.

The key was accepted but something still does not work

• Check which key is active. lists every key with its account name and marks the active one. Commands use the active key, so switch with if the wrong account is selected.
• Look for a key marked invalid. In the same list, a key that has stopped working is marked with a cross and (invalid). Keys break when they are deleted on the applications page, so add a new one.
• Check whether it is a light key. Light keys are labelled in the list and only work for account, guild and WvW verification. No other feature accepts them. Add a full key if you want the rest.
• Ask for your roles right away. If you have a working key but the roles never showed up, run on that server. Aleeva re-runs every role and name mapping for you there and then, instead of waiting for the next scheduled refresh. Run it on each server where you are missing roles, since it only applies to the server you use it in.
• Give role changes a moment. Roles based on your account are otherwise refreshed on a schedule, not instantly, so a role can take a few minutes to appear after you add a key.
• An admin added a key for you. Server admins can add or remove a key on your behalf, but it only takes effect once you confirm it with .