Fix UPCS Error: IP Address Not Allowed for Key

This 403 error means the request reached UPCS from an IP address that is not allowed for the API key you used. The key is valid, but the place it is called from is not.

Symptom

Calls that worked before now return HTTP 403 with success: false and no code, with a message explaining that the IP address is not allowed for the key. They may still work from your laptop or fail only from your live server.

Likely causes

• Your server or hosting provider changed its outgoing IP address.
• The request now goes through a proxy, CDN, VPN or load balancer with a different outgoing address.
• Staging and production servers use different IPs, and only one is allowed.
• The key is used from a place it was not meant for.

Fix it step by step

1. Find the outgoing IP of the machine making the call. Your host's control panel often shows it, or you can ask your hosting provider.
2. Note that the partner panel does not show or change IP restrictions for a key, so this check is done by the UPCS team.
3. Contact us with the key name (never the full key) and the outgoing IP address, and ask for the address to be allowed or the restriction reviewed.
4. If your host rotates outgoing IPs, ask them for a fixed outgoing address and allow that one.
5. Make sure the call is made from your server, not from a visitor's browser. Visitors have many different IPs, so browser calls will not match.
6. Retry the request.

Confirm it is fixed

The same request now returns data instead of 403. If you instead see origin_not_allowed, that is a different check; see origin_not_allowed. For key problems in general, see missing or invalid x-api-key.

When to contact support

If you cannot determine the outgoing IP, or the address is allowed and the error persists, contact support with the IP address, the time of the failure and the endpoint called.