Get OAuth2 identity | Wynncraft

$	curl https://api.wynncraft.com/v3/oauth/me

{
  "application": {
    "client_id": "9fcXAZx0_h2-1FqsTjVQzK_dnOSzmToD",
    "scopes": [
      "identify",
      "main_access"
    ]
  },
  "profiles": {
    "98bc2236-ada5-4039-b560-8aaa4cc50384": {
      "username": "Nepmia",
      "primary": true,
      "rank": "Administrator",
      "supportRank": "champion",
      "shortenedRank": "Admin",
      "legacyRankColour": {
        "main": "#aa0000",
        "sub": "#ff5555"
      },
      "rankBadge": "nextgen/badges/rank_administrator.svg",
      "accessRules": {
        "main_access": "public",
        "character_list_access": "public",
        "character_data_access": "public",
        "character_build_access": "public",
        "online_status": "friend",
        "hunted_characters_access": "public",
        "guild_history_access": "public"
      }
    }
  }
}

<Warning> Try it will not return usable data for this route. It depends on a live OAuth2 authentication context outside the docs. </Warning> <Info> Get started with OAuth by reading [our guide](/oauth2/creating-an-application). </Info> This endpoint returns the authenticated OAuth2 application context and the linked player profiles available to the authorized user. <Info> The `profiles` object contains the player profiles that belong to the authorizing user. Access-rule bypass through OAuth2 only applies to those linked profiles when the user granted permission for it. </Info>

$	curl https://api.wynncraft.com/v3/oauth/me

{
  "application": {
    "client_id": "9fcXAZx0_h2-1FqsTjVQzK_dnOSzmToD",
    "scopes": [
      "identify",
      "main_access"
    ]
  },
  "profiles": {
    "98bc2236-ada5-4039-b560-8aaa4cc50384": {
      "username": "Nepmia",
      "primary": true,
      "rank": "Administrator",
      "supportRank": "champion",
      "shortenedRank": "Admin",
      "legacyRankColour": {
        "main": "#aa0000",
        "sub": "#ff5555"
      },
      "rankBadge": "nextgen/badges/rank_administrator.svg",
      "accessRules": {
        "main_access": "public",
        "character_list_access": "public",
        "character_data_access": "public",
        "character_build_access": "public",
        "online_status": "friend",
        "hunted_characters_access": "public",
        "guild_history_access": "public"
      }
    }
  }
}

Try it will not return usable data for this route. It depends on a live OAuth2 authentication context outside the docs.

Get started with OAuth by reading our guide.

This endpoint returns the authenticated OAuth2 application context and the linked player profiles available to the authorized user.

The profiles object contains the player profiles that belong to the authorizing user. Access-rule bypass through OAuth2 only applies to those linked profiles when the user granted permission for it.

Response

OAuth2 application context and linked profiles.

applicationobject

profilesmap from strings to objects

1	{
2	"application": {
3	"client_id": "9fcXAZx0_h2-1FqsTjVQzK_dnOSzmToD",
4	"scopes": [
5	"identify",
6	"main_access"
7	]
8	},
9	"profiles": {
10	"98bc2236-ada5-4039-b560-8aaa4cc50384": {
11	"username": "Nepmia",
12	"primary": true,
13	"rank": "Administrator",
14	"supportRank": "champion",
15	"shortenedRank": "Admin",
16	"legacyRankColour": {
17	"main": "#aa0000",
18	"sub": "#ff5555"
19	},
20	"rankBadge": "nextgen/badges/rank_administrator.svg",
21	"accessRules": {
22	"main_access": "public",
23	"character_list_access": "public",
24	"character_data_access": "public",
25	"character_build_access": "public",
26	"online_status": "friend",
27	"hunted_characters_access": "public",
28	"guild_history_access": "public"
29	}
30	}
31	}
32	}