403 Forbidden errors typically occur when an API key is invalid or access to the API is being prevented in some other way.
Double check that the API key that you are using on input matches the API key in your account. You can copy your key directly in your account dashboard by clicking the 'copy' icon on the right-hand side of the key.
Certain input records might have characters like "#" that could conflict with the overall URL structure, unless they are "escaped". This can be accomplished by URL encoding your query parameter. Most programming languages have a built-in URL encode function that might help you out with this. For example, this is the Ruby iteration: https://www.urlencoder.io/ruby/
Certain Geocodio API endpoints, specifically those used in conjunction with our Lists API, are not automatically configured when you generate your API key.
To activate our List API endpoints, click the "Edit" button on the impacted API key in your account dashboard. From there, make sure that the necessary lists endpoints are checked. If you've turned off either of our geocode endpoints in the past, you can toggle them on and off from this menu as well.
Customers can manually set a limit on what IP addresses are allowed to access an API key. By default, there is no limit in place, but it is possible to have set one in the past that is impacting your current results.
To check to see which IP addresses are allowed, click the "Edit" button on the impacted API key in your account dashboard. At the bottom of the page, you'll see a field titled "Allowed IP Addresses". If this field is empty, no limit is in place and all IP addresses should be able to access the API Key. However, if any IPs are listed, they are the only IPs that will be able to make a call to the Geocodio API.
If your current IP is not in the list, be sure to add it. That should make it as "allowed".
If you or your organization uses a firewall or other security tools, verify that you are not currently blocking Geocodio or any of our active IP addresses. If you require a list of our IP addresses to whitelist, feel free to reach out to our support team.
The pygeocodio library was built by a third-party and designed to make implementing Geocodio a little easier for Python users. On occasion, we have seen Geocodio Enterprise customers receive a 403 error when attempting to use this library.
Our Enterprise product uses a separate API architecture and endpoint from our standard services, but pygeocodio was built before we introduced our Enterprise product, so it defaults to utilizing the non-Enterprise, standard endpoint.
To update the endpoint, make sure that your custom_base_domain parameter is set to https://api.enterprise.geocod.io/ when you instantiate your GeocodioClient object.