# Kustomer setup for PopMCP

You paste one Kustomer API key, made under Settings, Security, API Keys. It works for one organization, and PopMCP finds out whether that organization is in the US or EU region for you. The key's roles decide what it can do, and they cannot be changed later.

- Auth: API credentials
- Setup time: 2 min
- API base URL: https://api.kustomerapp.com (US) or https://api.prod2.kustomerapp.com (EU)
- Credentials screen: https://help.kustomer.com/api-keys-SJs5YTIWX
- Provider docs: https://developer.kustomer.com/kustomer-api-docs/reference/authentication

## Before you begin

- A Kustomer organization you can sign in to
- To be an admin, or to have Security permissions. Others can't make API keys.

## Get your credentials

### 1. Open API Keys in Kustomer

Sign in at your own Kustomer address, such as `acme.kustomerapp.com`. Open Settings, then Security, then API Keys, and select Add API Key.

### 2. Name the key and choose its roles

Under Name, enter something you will recognise, like `PopMCP`. Under Roles, choose `org.admin` and `org.user` to reach every tool, or only the roles you want, such as `org.user.customer.write`. For look-ups only, choose read roles such as `org.permission.customer.read`, `org.permission.conversation.read` and `org.permission.message.read`, plus `org.permission.search.create` for search. Roles can't be changed after the key is made. Under Expires, choose how many days the key should last. Leave CIDR IP Restriction empty, then select Create.

### 3. Copy the key

Select Copy Token on the confirmation screen. This is your only chance: Kustomer shows a key once, so if you lose it you need to make a new one.

### 4. Paste the key into PopMCP

Paste it into Kustomer API key. PopMCP tries the key in Kustomer's US and EU regions and remembers where it works. It usually finds your organization's name too. If it says it couldn't, reconnect and add the name under More options: it is the first part of your Kustomer address, and only the public help center tools need it.

## Fields PopMCP asks for

- Kustomer API key (apiKey) [required]: From Settings > Security > API Keys in Kustomer: Add API Key, then Copy Token. Stored encrypted, used server-side only.
- Organization name (optional) (organization): The first part of your Kustomer address, as in acme.kustomerapp.com. We usually find it for you. Public help center tools use it.

## Verify

PopMCP shows Kustomer as Verified, labelled with your organization's name, with (EU) added for an organization in the EU region. Ask for your teams: kustomer_list_teams answers with their ids and names.

## Troubleshooting

### "Kustomer didn't accept this API key in its US or EU region"

Cause: The key was copied incompletely, has been deleted, or has an IP restriction.

Fix: Kustomer can't show a key twice, so make a new one under Settings, Security, API Keys without a CIDR IP Restriction, and paste that.

### "This Kustomer API key expired"

Cause: The number of days chosen under Expires has passed.

Fix: Make a new key and reconnect.

### A tool answers that Kustomer refused this key and names roles

Cause: The key doesn't have a role that tool needs. Kustomer can also answer this way when your plan lacks the feature.

Fix: Roles can't be changed on an existing key, so make a new key with the role and reconnect.

### A public help center tool asks for your organization name

Cause: PopMCP couldn't find the name from the key.

Fix: Reconnect and enter it under More options, or use the kustomer_list_kb_articles and kustomer_search_kb_articles tools, which don't need it.

---

Source: https://www.docs.popmcp.com/docs/integrations/kustomer/