Users

If your app uses the identify scope, you can access details about the user who has authorized your app.

The endpoint https://gw2.me/api/user will return the user's id and name. You will need to pass the access_token as a header (Authorization: Bearer <access_token>). If the users has also authorized the email scope, the response will additionally include the user's email address and verification status.

{
  "user": {
    "id": "84093c3b-a856-4bb5-856b-77b9f94a70e7",
    "name": "darthmaim",
    "email": "[email protected]",
    "emailVerified": true
  }
}

Settings

You can optionally store settings for each user. This is useful if, for example, your app does not have a user database (e.g. a client-side only app) and you want to store user-specific settings.

To store settings, make a POST request to https://gw2.me/api/user/settings and include a JSON object in the request body. You will again need to pass the access_token as a header (Authorization: Bearer <access_token>). Only valid JSON objects below 10kb are accepted.

If you have stored settings for the user, the https://gw2.me/api/user endpoint will include the settings in addition to the user details in the response.

{
  "user": {
    "id": "84093c3b-a856-4bb5-856b-77b9f94a70e7",
    "name": "darthmaim"
  },
  "settings": {
    "locale": "de-DE",
    "theme": "dark",
    "display": {
      "timer": false,
      "items": [
        19675
      ]
    }
  }
}

Keep in mind that, if the access token is visible to the user (e.g. in a client-side app), the user can modify these settings. Only store settings that are not critical to your app. It is your responsibility to validate the settings object before using it.