> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://doc.cheddar.biz/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://doc.cheddar.biz/_mcp/server.

# IP whitelisting

The REST API accepts requests only from your organization's active IP addresses.
A request from any other address is rejected with `403 Forbidden`, even when its
API key is valid.

## Add an IP address

1. Find your server's **outbound** public IP address. From the server, run:

   ```bash
   curl https://checkip.amazonaws.com
   ```

2. Go to **Dashboard → Organization Security → API IP Whitelist**
   (`/dashboard/organization`).

3. Click **Request IP**, enter the address and your authenticator code, then
   submit.

4. The Cheddar team reviews the request. The address starts working when its
   status changes to **Active**.

Enter each address exactly, in IPv4 or IPv6 form. CIDR ranges are not supported,
so add every outbound address your servers use.

## Statuses

| Status               | Meaning                                                                     |
| -------------------- | --------------------------------------------------------------------------- |
| **Pending approval** | Requested and awaiting Cheddar approval. API requests from it are rejected. |
| **Active**           | Approved. API requests from it are accepted.                                |
| **Revoked**          | Revoked or not approved. API requests from it are rejected.                 |

The table also shows when each address was requested, approved, and revoked.

## Revoke an IP address

Click **Revoke** next to the address and enter your authenticator code. Revoking
takes effect immediately. To use the address again, request it again and wait for
approval.

> **Warning**
>
> If you revoke your last active address, every REST API request is rejected until a
> new address is approved.

## Change server IP addresses

1. Request the new address and wait until it is **Active**.
2. Move your traffic to the new address.
3. Revoke the old address.

## Troubleshooting `403 Forbidden`

* Confirm the address your server actually sends from. NAT gateways, proxies, and
  VPNs change it.
* Confirm that address is **Active** in the dashboard.
* For IPv6 traffic, add the IPv6 address.
* Check that your API key belongs to the organization where the address is listed.