We have the validate API method (or will, anyways), but messages about failed geocoding calls due to invalid API keys are getting swallowed, resulting in lots of wasted time tracking down the problem. Don't swallow the messages.
{"status":400,"message":"Invalid API key. The IP you provided does not match what the API is receiving. Double check your API key or create a new one using 10.72.30.1 as the pattern."}
We have the validate API method (or will, anyways), but messages about failed geocoding calls due to invalid API keys are getting swallowed, resulting in lots of wasted time tracking down the problem. Don't swallow the messages.
{"status":400,"message":"Invalid API key. The IP you provided does not match what the API is receiving. Double check your API key or create a new one using 10.72.30.1 as the pattern."}