# Retell AI setup for PopMCP

One workspace API key, created under Settings > API Keys in the Retell dashboard, pasted into PopMCP's single API key field and sent as an Authorization: Bearer header.

- Auth: API credentials
- Setup time: 3 min
- API base URL: https://api.retellai.com
- Credentials screen: https://dashboard.retellai.com/settings/api-keys
- Provider docs: https://docs.retellai.com/accounts/api-keys-overview

## Before you begin

- A Retell AI account with at least one workspace at dashboard.retellai.com
- Admin or Developer access to that workspace, because API keys are issued per workspace
- The workspace that owns the agents, phone numbers and call history PopMCP should read

## Get your credentials

### 1. Sign in and pick the workspace

Open dashboard.retellai.com and sign in. Use the workspace switcher in the top-left corner to select the workspace that owns the agents and phone numbers PopMCP should reach.

Screen: https://dashboard.retellai.com

### 2. Open Settings, then the API Keys tab

Click Settings in the sidebar under System, then open the API Keys tab. Leave the key flagged Set as Webhook Key alone and create a separate one for PopMCP.

Screen: https://dashboard.retellai.com/settings/api-keys

### 3. Add a key named PopMCP

Click Add, type `PopMCP` in the Name field, and click Create. Leave Restrict permissions switched off so the key keeps full access.

### 4. Copy the key into PopMCP

Click Copy in the dialog and paste the `key_...` value into PopMCP's API key field, then connect.

## Fields PopMCP asks for

- API key (apiKey) [required]: Retell dashboard (dashboard.retellai.com) → Settings → API Keys → create/copy a key. Sent as the Authorization: Bearer header. Stored encrypted; used server-side only. The connection is locked to this key's Retell account.

## Verify

PopMCP shows the Retell connector as Connected and names your workspace. Asking for recent calls or the list of agents returns real rows instead of an auth error.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The key was mistyped, truncated on paste, or has since been deleted or rotated in the dashboard.

Fix: Open Settings > API Keys, delete the stale entry, click Add to mint a fresh key, and paste the whole key_ string with no surrounding spaces. The full value is shown only at creation, so a lost key has to be replaced rather than recovered.

### Some tools work but calls or agent edits return 403

Cause: The key was created with Restrict permissions on and the relevant permission left at No Access or Read.

Fix: Edit the key in Settings > API Keys. Raise Call to Edit for outbound calls and Agent to Edit for agent changes, or switch Restrict permissions off entirely.

### PopMCP sees no agents even though the connection succeeded

Cause: The key belongs to a different Retell workspace than the one holding your agents.

Fix: Switch workspaces with the top-left switcher, mint a key there, and reconnect.

### Outbound calls are rejected with a concurrency error

Cause: The workspace has hit its simultaneous-call quota, which defaults to 20 on Pay-As-You-Go.

Fix: Open Settings > Limits and click Adjust Concurrency on the Concurrent Calls Limit card, or enable concurrency burst, then retry.

---

Source: https://www.docs.popmcp.com/docs/integrations/retell-ai/