Omnisend
Connect Omnisend to manage contacts, events, and segments, and run email and SMS campaigns and automations for your store.
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.
- Setup time
- 4 min
- Auth
- API credentials
- API base URL
- https://api.omnisend.com/api
- Rate limits
- 400 requests per minute per brand by default, with tighter caps on some endpoints: segment writes 15 a minute, contact tag changes 60 a minute, template rendering 40 a minute, and analytics 10 a minute or 55 per 24 hours.
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
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.
Integrations & API
Connect other apps to Omnisend and manage the keys they use.
| Name | Key | Permissions | Created |
|---|---|---|---|
| Reporting syncCustom integration | 6512••••••••••••ab3d | Campaigns, Orders | Mar 4, 2026 |
| Signup formCustom integration | 6512••••••••••••71c9 | Contacts | Jan 12, 2026 |
Existing keys stay masked. There is no reveal action, only Delete.
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.
Create API key
Pick the data this key is allowed to reach.
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.
Integrations & API
Connect other apps to Omnisend and manage the keys they use.
Omnisend's wording: "You can't view the key again after closing this screen. If you lose it, generate a new one."
Paste it into PopMCP
Paste the key into PopMCP's API key field and connect.
Connect in PopMCP
Open your workspace, choose Omnisend in the marketplace, and fill in the connect dialog:
| Field | What to enter |
|---|---|
| API keysecret | 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.Encrypted with AES-256-GCM on save and never shown again. |
PopMCP verifies the credential against Omnisend immediately. On success the connection flips to Verified and its MCP tools are provisioned.
Verify it worked
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
Why: 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
Why: 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
Why: 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"
Why: 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
Why: 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.