---
title: "Manage the network's REST API and Anthropic keys"
description: "Read, set or regenerate the network-level public and private key that signs the keyed REST endpoints, and store the network's own Anthropic API key so every user without a key of their own runs the AI assistant on it — on the REST API keys tab of White label preferences."
type: "howto"
audience: [admin]
keywords: [REST API keys, public key, private key, regenerate keys, keyed REST endpoints, register-user, user-sign-up, Anthropic API key, network key, AI assistant, replace key, remove key]
ui_path: "Admin → Ad serving → White label preferences → REST API keys"
---

Fetch the complete documentation index at: https://epom.com/ad-server/docs/llms.txt. Use this file to discover all available pages before exploring further. Append .md to any documentation page URL to get its markdown version.

# Manage the network's REST API and Anthropic keys

The **REST API keys** tab of White label preferences holds two network-level secrets: the public
and private key pair that signs the keyed REST endpoints for registering and signing up users,
and the network's own Anthropic API key, which every user without a key of their own runs the AI
features on. It is the last of the four tabs on
[Configure white-label branding](https://epom.com/ad-server/docs/guides/admin/white-label.md).

**Example.** Northwind Media pastes its own Anthropic key under **AI (Anthropic API key)**. From
then on its 40 publishers use the AI assistant, the Traffic Quality analyst notes and AI matching
of pasted targeting lists on Northwind's key, and the platform bills nothing for it; the page
shows *The network key …7f3a is in use*.

## Typical scenarios

| You want | Set | Where |
|---|---|---|
| The AI assistant on your own Anthropic key, billed to you not Epom | Paste the key under **AI (Anthropic API key)** → **Save key** | REST API keys |
| Rotate the pair an integration signs its user-registration calls with | **Regenerate keys**, then update every integration within the minute | REST API keys → Keys management |

## Step by step

1. Open **REST API keys**. **Keys management** holds the network-level pair: **Public key
   (username)** and **Private key (password)**, which authenticate the keyed REST endpoints
   `POST /rest-api/register-user/{key}/{hash}/{timestamp}` and
   `POST /rest-api/user-sign-up/{key}/{hash}/{timestamp}` (the hash is signed with the private
   key).

   ![REST API keys tab: the network's public and private key with Regenerate keys, and the AI (Anthropic API key) section waiting for a key](https://epom.com/docs-images/ad-server/white-label/api-keys-tab.webp)

2. To rotate both, click **Regenerate keys** and confirm: a new random pair is saved at once and
   *Keys regenerated.* confirms it. To set your own, type the value (16 hex characters) and click
   **Save**. Either way the old pair stops working within about a minute — update every
   integration first.
3. Under **AI (Anthropic API key)**, paste the network's own key from the Anthropic Console and
   click **Save key**. Every user without a key of their own then runs the
   [AI assistant](https://epom.com/ad-server/docs/guides/collaboration/ai-assistant.md) and the other AI features on it (the Traffic
   Quality report's analyst notes, AI matching of pasted targeting lists) and the platform bills
   nothing for it. The key is checked with Anthropic before it is stored (a refused key is not
   saved), kept encrypted and shown only by its last four characters (*The network key …7f3a is
   in use*). **Replace key** swaps it; **Remove key** deletes it, and users without their own key
   lose the AI features at once unless the platform's key is switched on for the network (and
   then billed).

## Caveats and exceptions

**Whoever manages logos can also regenerate the keys.** The **White Label Preferences** admin
permission is all-or-nothing: there is no images-only or theme-only variant, so the people who
hold it can rotate the REST pair and replace the Anthropic key too.

The caveats that apply to every tab are on
[Configure white-label branding](https://epom.com/ad-server/docs/guides/admin/white-label.md#caveats-and-exceptions).

## Not working?

| Symptom | Check | Where |
|---|---|---|
| The AI assistant stopped for everyone | The network key was removed and the platform key is off | REST API keys → AI; [AI assistant](https://epom.com/ad-server/docs/guides/collaboration/ai-assistant.md) |
| Keyed REST calls fail after Regenerate | The old pair stops within a minute | Update every integration with the new pair |

The causes for the other tabs are on
[Configure white-label branding](https://epom.com/ad-server/docs/guides/admin/white-label.md#not-working).

## Reference

The fields of the tab: [REST API keys tab](https://epom.com/ad-server/docs/guides/admin/white-label-reference.md#rest-api-keys-tab). Which
key the AI assistant picks for a user, and how the platform key is billed:
[AI assistant](https://epom.com/ad-server/docs/guides/collaboration/ai-assistant.md#which-key-it-runs-on).

## Related

- [Configure white-label branding](https://epom.com/ad-server/docs/guides/admin/white-label.md)
- [Set the company details and platform defaults](https://epom.com/ad-server/docs/guides/admin/white-label-main-tab.md)
- [Set the theme, logos and sign-in background](https://epom.com/ad-server/docs/guides/admin/white-label-appearance-and-images.md)
- [White-label preferences reference](https://epom.com/ad-server/docs/guides/admin/white-label-reference.md)
- [AI assistant](https://epom.com/ad-server/docs/guides/collaboration/ai-assistant.md)