Pricing, limits, and integration
Omnisend's API is part of the product, not a separately-priced line: there is no API-only plan or per-call metering. Programmatic access runs on your normal Omnisend subscription, which meters on contacts and sends, so the API operates within whatever your plan already allows. Authentication is an API key in the Authorization header, and every 2026-03-15 request also carries an Omnisend-Version header to pin the schema.
Rate limits are set per endpoint group rather than one global number. Segments, for example, are documented at 100 requests per minute for reads and 15 per minute for create and update. Plan for those per-resource ceilings on any bulk sync. There are no official SDKs, so you call the endpoints directly or generate a typed client from the docs; a public Postman collection and an llms.txt index at api-docs.omnisend.com speed that up. For event-driven flows, note that webhooks are a send-webhook action inside an automation workflow, not a standalone subscriptions API, so wire real-time triggers through the automation builder.
How much does the Omnisend API actually cost?
Omnisend publishes an API, but per-tier gating wasn't extracted automatically.
- Most likely scenario: API access is either included in all paid plans, or it's gated to higher tiers and we need to verify on the live docs page.
- Until verified, treat the question "which plan unlocks the API" as open. Don't budget on the assumption it's free with the cheapest paid plan.
API at a glance
Which AI clients can read Omnisend data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Omnisend specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Via connectors | Add as a custom connector (Settings, Connectors) pointing at mcp.omnisend.com/mcp, then OAuth login. Official one-click connector coming soon. |
| ChatGPT | Native MCP | Published Omnisend app in the ChatGPT app directory; connects over OAuth. |
Omnisend also has an MCP server
If you're wiring Omnisend into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Omnisend MCP pageWhat you can build with the Omnisend API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Omnisend into your daily workflow
- Pull a digest of campaign performance into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Omnisend reporting at scale
- White-label Omnisend data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Omnisend UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Omnisend
- Real-time sync into your warehouse on a cron
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Omnisend data older than the dashboard exposes
Quickstart template
# Starter template — endpoint paths and SDK package names come from # the Omnisend API docs: https://api-docs.omnisend.com/ curl -X GET "https://api-docs.omnisend.com/<your-endpoint>" \ -H "Authorization: Bearer $TOKEN" \ -H "Accept: application/json" | jq .
Template only. Endpoint paths, exact base URL, and auth header format come from api-docs.omnisend.com.
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- No official SDK detected. Plan on hitting the API directly with your HTTP client of choice.
- Rate limits: always read the docs page before scaling — the published limit is usually lower than the practical one and overages can be expensive.
- No-code fallback: Zapier and Make.com cover the common triggers if you want to skip writing API code for simple flows.
Agent-readiness verdict
Score: 7/10 on API-readiness. Omnisend's REST API is well-designed and broad: date-versioned via Omnisend-Version, cursor pagination, RFC 9457 error bodies, API-key auth, an llms.txt index, and a Postman collection, spanning contacts, events, products, campaigns, segments, automations, and reporting. That is a clean, agent-friendly surface. It sits at 7 rather than higher because there are no official SDKs and no dedicated webhook-subscription endpoint (webhooks are an automation-workflow action), which adds glue work for real-time and code-heavy integrations.
Solid agent fit with a first-party MCP server and a clean REST API. Omnisend hosts an official MCP server at mcp.omnisend.com/mcp, authenticated over OAuth, so an agent can create campaigns, build automations, recommend and edit segments, and pull revenue reporting from Claude or ChatGPT. The REST API (api.omnisend.com/api) is date-versioned via an Omnisend-Version header, uses cursor pagination and RFC 9457 error bodies, and spans contacts, events, products, campaigns, segments, automations, and reports. It sits below the GA-official tier because the one-click Claude connector is still coming soon (custom connector for now), there are no official SDKs, and webhooks are an automation-workflow action rather than a subscription API.
Omnisend API FAQ
Does Omnisend have a public API?+
What auth does the Omnisend API use?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Sources
- Omnisend official site: https://www.omnisend.com/
- API docs: https://api-docs.omnisend.com/
- MCP server: https://mcp.omnisend.com/mcp
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.