API talk:2/account

Non persistent name

The name is non persistent. Proof: [1]

From personal experience: I have bought the collectors edition half a year after release and I asked the support if it is possible to merge the collectors benefits with my already existing account. It was possible but they needed to generate a new account suffix. I add this back in. --Teranas (talk) 12:26, 29 March 2015 (UTC)

Missing information

According to the https://account.guildwars2.com/account/api-keys/create link the following is listed in the accounts api: Your account display name, ID, home world, and list of guilds. The last one is not listed on the page. Can someone add this? Jurrit (talk) 10:21, 29 May 2015 (UTC)

Done. However, all the OAuth2 info is outdated too. I just don't know what poke's plans on this. --Smiley™ de: user | talk 11:45, 29 May 2015 (UTC)

Out of Date/ incomplete

The link in References discusses the now-defunct Oauth implementation. A better link might be the one that describes the current implementation: https://forum-en.gw2archive.eu/forum/community/api/HEADS-UP-OAuth2-being-replaced-next-week/first

Also, this article omits the mostly commonly used method of passing the API key, as a URL parameter. Indeed I feel this should appear under Parameters.

The parameter is "access_token"

Usage: https://api.guildwars2.com/v2/account?access_token=<API_Key>

As implied by the example (but not actually stated in the article), the developer can alternatively pass the API-key by altering the HTTP Request "Authorizaton" header. —The preceding unsigned comment was added by Lakshmi (talk • contribs).

The link within the references is still valid, it's only meant to point out that specific post from Lawton discussing the fact that the account ID is immutable. I'll add the parameter and update the response (because there have been some fields added since the last edit) but as for the information regarding the header, that is covered under v2's main page and it would seem redundant to add it here; especially since none of the other endpoint pages have it. Eearslya (talk) 16:11, 23 September 2015 (UTC)

Document scope for guild_leader

An access token without the 'guilds' scope will not permit access to the 'guild_leader' data. I've tested this myself. ~Steven (talk) 21:40, 20 May 2019 (UTC)

Commander Field

It seems the API does not recognize a Catmander as a Commander. Owning a catmander tag without also owning the default commander tag reported 'commander' as false for me. Since I only have one point of data to work with, I'm limiting my comment to the discussion page for now. SomeGuy (talk) 23:31, 6 January 2022 (UTC)

I can confirm TwoLate (talk) 09:43, 5 September 2023 (UTC)

access array

The caveats aren't strictly true. My account from 2013 does not have FreeToPlay, and I have the HeartOfThorns value even though I acquired it with PoF in 2017. Maybe FreeToPlay will only show for accounts created after the base game was made free? Sickhippie (talk) 20:26, 25 May 2024 (UTC)

Fields updated with WvW restructuring beta (version: 2024-07-20T01:00:00.000Z)

I found that there is a new wvw field:

"wvw": {
  "team_id": 11002,
  "rank": 322
},

Additionally, the wvw_rank field is no longer present on my personal account.

--Yoone (talk) 15:28, 4 September 2024 (UTC)

Made some changes. If you want any further edits, comment here or get yourself access via Guild Wars 2 Wiki:Requests for API editorship. -Chieftain Alex 19:28, 4 September 2024 (UTC)