Hi @Kevin_Karobia - Welcome to the community.
I’m hoping maybe details on this post will help narrow down or even resolve the issue. However, as per the Required for Select Resources: API Resource Request Access Lists documentation:
tlas allows your API key to make requests from any address on the internet. Atlas has some exceptions to this rule. These exceptions limit which resources an API key can use without location-based limits defined in an API access list.
To add these location-based limits to your API key, create an API access list. This list limits the internet addresses from which a specific API key can make API requests.
Any API keys with an API access list require all API requests to come from an IP address on that list. Your API access list must include entries for all clients that use the API.
The API access list associated with the API key is different from the Atlas Project Network Access list. I.e. You can still connect to the Atlas instance(s) within a project from a IP that is on the Atlas Project Network Access List and not on the IP Acess List associated with the API Key(s) for that project.
Regards,
Jason