Slight change to error handling - 401 versus 403 status code
23 Apr 2019
We have slightly changed how we respond to a few edge cases around invalid requests to our geocoding API.
Previously if you sent the API a request without the required
or with an invalid value for that parameter (for example we occasionally saw
people trying to mistakenly use API keys from other online services), we would
403 status. We now instead return a
401 status and
messsage to help in debugging.
We contine to return a
403 status in the case where the key has been
blocked due to abuse (I hope you, gentle reader, never have to see that).
We hope this change leads to fewer misunderstandings and faster debugging.
This change was listed in our API Change Log and all the various response codes the geocoding API can return can be found in our API documentation.