Reoccurring 429 Error Code — Guild Wars 2 Forums
Home API Development

Reoccurring 429 Error Code

Hello everyone! I am very new to APIs, so forgive me if this is a simple problem. I am using Google Apps Script to perform calls and write the returned data into a google sheet. I have tested my API Key via Postman and confirmed it is working properly. My google apps script was working properly on Friday, but it is now returning a 429 error repeatedly. Based on this error code, I would expect it to be related to a rate limit, but I am not receiving this error via Postman (which still functions properly), so I am confused as to what my next steps should be to resolve this issue. My code is pasted below:

// Set API URL - https://wiki.guildwars2.com/wiki/API:2/currencies
var url = "https://api.guildwars2.com/v2/currencies?ids=all";

// Set API Call headers
var headers = {
"Authorization": "Bearer " + Auth() //Auth() is a sub-function which returns my API Key value
};

// Set API call options
var options = {
"method": "get",
"headers": headers
};

// Fetch Data
var response = UrlFetchApp.fetch(url,options);

Any assistance would be appreciated.

Comments

  • YtseJam.9784YtseJam.9784 Member ✭✭✭

    Hi, there were issues with the API over the weekend, not sure if you were doing this at the same time it was happening. BTW the /v2/currencies endpoint doesn't require authorization so you dont need to set the auth bearer token header

  • @YtseJam.9784 said:
    Hi, there were issues with the API over the weekend, not sure if you were doing this at the same time it was happening. BTW the /v2/currencies endpoint doesn't require authorization so you dont need to set the auth bearer token header

    Thanks for the info! Is there a status page for the API or something we can subscribe to in order to be notified about outages?

  • YtseJam.9784YtseJam.9784 Member ✭✭✭

    idk, i just know cause a lot websites i use that use API were having issues

  • Confirming that my script started working by itself today without me making any changes. As such, it is safe to assume that this was due to API Issues on the ArenaNet side.