API disabled ? — Guild Wars 2 Forums
Home API Development

API disabled ?

ThomasC.1056ThomasC.1056 Member ✭✭✭
edited October 4, 2017 in API Development


I'm no big programmer or whatever, and only an efficiency user, and in that case, the site doesn't work. When I try to use the craft calculator, it says "Invalid API key". So, as I'm a good boy, I went back to the application, and made a new one (just in case, you know), and efficiency won't register it because "API key is invalid, or API is disabled".

Considering that I just used the official site to make a new key, I'm guessing it can't be invalid, which means the API is disabled.

Thought you'd want to know it...

EDIT : it works again, then it's off again. I'm not sure where the issue is after all.

Look at that—you broke Scruffy's sarcasm meters. ~ Taimi.



  • Nokomis.5076Nokomis.5076 Member ✭✭✭

    I had the same problem with GW Efficiency. One hour it told me, my key was incorrect, then suddenly it worked again. Eventually it has something to do with the performance problems of the GW servers, eventually the API is connected somehow.

    Was I able to help you or give you a hint? Click on Helpful and/or Thumbs up, I would appreciate it alot!
    When you encounter a bug ingame, at first you should file a ticket via the ingame command /bug, as only this way the devs will know exactly where you were, when the bug happened.

  • I develop a wrapper around the API and some endpoints are indeed spotty; 'colors' seems to be disabled entirely, though it's currently the only one failing unit tests. Been down at least 6 hours.

    Did I miss a post about colors being removed or something? https://api.guildwars2.com/v2/colors/10

  • Lawton Campbell.8517Lawton Campbell.8517 ArenaNet Personal  

    @Patches.7584 said:
    Did I miss a post about colors being removed or something? https://api.guildwars2.com/v2/colors/10

    Yeah. It currently causes one of the backend servers to crash due to a method returning NULL instead of an empty string for an enumeration value missing in a table. Whoops.

    The API key wonkiness was due to requests timing out yesterday due to some internal network congestion.