Misleading error message for 403/Forbidden response from API
Created by: universalhandle
Related to #4 (closed), I think I'd have gotten to the bottom of my configuration problem faster with more nuanced handling of the response. For 403/Forbidden, the extension reports:
Check that the API key is valid.
... which suggests to me that the API key doesn't exist on the server (i.e., analogous to a user name/password mismatch). What it actually means, though, is that your valid API key doesn't have permission to do the requested action.
If I'm not mistaken -- and I could be, because I didn't find good documentation around the return codes for this API -- 401/Unauthorized means the API key is bogus. Did you find better documentation for return codes than this?
Do you agree with my assessment? If so, I'll gladly make a PR to add some clarity to the feedback messages.