[Suggestion] Ability to capture an event when an API key is deleted.

Basically an event or via a web hook, to subscribe to a API key delete. (or more kinds of event, if any)

Is this a possible feature?

looking for something like am event that we can subscribe to when an API key is deleted/invalidated.

Via https://wiki.guildwars2.com/wiki/API:2/tokeninfo you could just check, if the API key is still valid.

I do understand there is an end point, but I was thinking more in the line of a realtime event that one can subscribe to, when an API key gets deleted.

Any particular reason why you need an event for when an API key becomes invalid?Curious as to what you would need that kind of time accuracy for

Basically to avoid too many /tokeninfo API calls, so that I can rely on a single event for token consistency.

You will be able to tell if an API Key is valid or not, with every request you make. The API will tell you then, that your API Key is invald.An API should not push information to the client. There is no reason to get the validity of an API key in realtime. It can always be checked when requests are made.

Agreed, thats just one way to go about it, thats one extra hop from my API, i would cache the other data, but when it comes to auth its not the same, caching auth/api key and assuming its valid isnt an option either, and checking for tokeninfo on every request on my API end, is too much of an overhead since Ive to always talk to GW2. Hope i was clear.

@"peekaay.3471" said:Agreed, thats just one way to go about it, thats one extra hop from my API, i would cache the other data, but when it comes to auth its not the same, caching auth/api key and assuming its valid isnt an option either, and checking for tokeninfo on every request on my API end, is too much of an overhead since Ive to always talk to GW2. Hope i was clear.

You don't have to call tokeninfoTake this for example https://api.guildwars2.com/v2/account?access_token=8A0F6DC1-6034-BF48-99FA-ABDF541F13401931E4F6-F174-433A-8563-EDC29561AA92It directly tells you the key is invalid, no need to call tokeninfo