> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/manual/account/api-keys/ip-allowlist.md).

# IP Allowlist

An IP Allowlist restricts an API key to requests from specified public outbound IP addresses. You can configure it separately for each key.

IP Allowlist verification is optional and disabled by default. You can save your IP Allowlist first and enable verification when your applications are ready.

## Before you start

Identify every public outbound IP address your applications use to call the API, including production servers, backup environments and scheduled jobs.

Use the public IP seen by the API, which may belong to a NAT gateway or outbound proxy. Your server’s private network address and your browser’s public IP may not be the addresses used by your application.

If outbound addresses change when servers restart or scale, consider configuring a stable outbound IP before enabling the allowlist. Otherwise, update the allowlist before changing your outbound addresses.

You also need permission to manage the relevant API key. If you cannot access the settings, contact your account or organization administrator.

## Save your IP Allowlist

1. Open [System → API](https://app.blocksec.com/phalcon/compliance/system/api).
2. Find the API key you want to protect and select **Manage** to open **Security Settings**.
3. Select **Set Up IP Allowlist**.
4. Enter your applications’ public IP addresses or CIDR ranges. Use **Add IP** to add more entries.
5. Review the full list, then select **Save IP Allowlist** and confirm.

Saving the list does not enable IP Allowlist verification. You can keep verification off while preparing your applications.

## Enable IP Allowlist verification

1. Open the API key’s **Security Settings** and review the saved IP Allowlist.
2. Confirm that it includes all required public outbound IP addresses.
3. Enable IP Allowlist verification when your applications are ready.
4. Make a request from your application to verify that access works as expected.

Once verification is enabled, requests from IP addresses outside the saved list will be rejected, even if they use the correct API key.

## Supported entries

You can enter:

* A single public IPv4 address.
* A single public IPv6 address.
* A public network range in standard CIDR notation.

A CIDR range allows all addresses within that network. Use the smallest range that covers your application’s outbound addresses.

Domains, URLs, port numbers, wildcards such as `*`, private or loopback addresses, and allow-all ranges such as `0.0.0.0/0` or `::/0` are not supported.

Correct any validation errors before saving and stay within the entry limit shown on the page.

## Update your IP Allowlist

1. Open the API key’s **Security Settings**.
2. Select **Edit** in the IP Allowlist section.
3. Add or remove entries as needed.
4. Select **Save IP Allowlist**, review the confirmation, and apply the change.

Saving updates the IP Allowlist. When verification is enabled, requests from IP addresses removed from the list will be rejected. When verification is off, saving the list does not turn it on.

When moving applications to new servers, add the new outbound addresses first. Verify requests from the new environment before removing the old addresses.

## Turn off IP Allowlist verification

1. Open the API key’s **Security Settings**.
2. Turn off IP Allowlist verification and confirm.

IP restrictions are removed immediately. The API key can then be used from any IP address.

Your saved addresses are retained. To enable verification again, review the saved list and turn on IP Allowlist verification.

## Troubleshooting

### Requests fail after enabling or updating the allowlist

* Confirm the request is using the API key whose allowlist you configured.
* Check the actual public outbound IP of the application making the request.
* Include all outbound addresses used by your production servers, backups, NAT gateways or proxies.
* If your infrastructure uses IPv6, check whether requests are leaving through an IPv6 address rather than the IPv4 address you added.
* Check whether a recent deployment or infrastructure change introduced a new outbound IP.

Update the allowlist to include any missing outbound addresses.

### An entry cannot be saved

Check that the entry is a supported public IP address or CIDR range and that the list is not empty. Correct the errors shown on the page and ensure the number of entries does not exceed the displayed limit.

### A save request times out

Reopen or refresh **Security Settings** to check whether the change was saved before retrying.

For further help, contact <phalcon_support@blocksec.com>. Include the request time, endpoint, response details and request ID if available. Do not share your full API key.
