# Omnisend setup for PopMCP

One Omnisend API key, created under Store settings, Integrations & API, API keys, with the permissions it needs ticked. Omnisend shows the key once, so copy it before closing the dialog.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.omnisend.com/api
- Credentials screen: https://app.omnisend.com/integrations/api-keys
- Provider docs: https://api-docs.omnisend.com/reference/authentication

## Before you begin

- An Omnisend account with a connected store, on any plan including Free
- A user who can open Store settings. Owners and admins can, restricted seats often cannot reach the API keys screen
- Somewhere safe to paste the key immediately, because Omnisend never shows it again

## Get your credentials

### 1. Open the API keys screen

Sign in at app.omnisend.com and click your profile in the top-right corner, then Store settings. Open Integrations & API and select API keys.

Screen: https://app.omnisend.com/integrations/api-keys

### 2. Name the key and tick its permissions

Click Create API key, name it `PopMCP`, then tick Campaigns, Contacts, Orders, Products, Carts and Events. Click Create API key to confirm.

Screen: https://app.omnisend.com/integrations/api-keys

### 3. Copy the key before you close the dialog

Click Copy API key and paste it somewhere safe. Omnisend shows the full key only on this screen.

### 4. Paste it into PopMCP

Paste the key into PopMCP's API key field and connect.

## Fields PopMCP asks for

- API key (apiKey) [required]: Omnisend dashboard → Store settings → Integrations & API → API keys (app.omnisend.com/integrations/api-keys) → Create API key, give it a name, and copy the key immediately (it's shown only once). Stored encrypted.

## Verify

PopMCP shows Omnisend as Connected, and asking it to look up a contact by email returns that contact's subscription status and tags instead of an authentication error.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The key was mistyped, truncated on copy, or has since been deleted in Omnisend.

Fix: Create a fresh key at app.omnisend.com/integrations/api-keys, copy it straight from the one-time dialog, and re-paste it into PopMCP.

### 403 Forbidden on some tools while others work

Cause: The key was created without the permission that endpoint needs. Events left unticked, for example, blocks Flow triggers while contact lookups keep working.

Fix: Create a new key with every required permission ticked, paste it into PopMCP, then delete the old key. There is no cap on how many keys you can create.

### The name you typed opened a setup wizard instead of the permission list

Cause: Omnisend matches the key name against known apps and routes recognised names into that app's guided flow.

Fix: Back out and enter an unrecognised name such as PopMCP to get the manual permission picker.

### 429 "Rate limit exceeded"

Cause: You crossed the per-brand sliding-window limit of 400 requests a minute, or a tighter per-endpoint cap.

Fix: Wait for the window to slide, honour the retryAfter value when the response includes one, and spread bulk work out rather than looping tightly over segments or analytics.

### You cannot find API keys in the menu

Cause: Your seat does not have permission to open Store settings.

Fix: Ask the Omnisend account owner to create the key, or to raise your role, then repeat the steps.

---

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