Omnisend
Omnisend is a Lithuanian-headquartered email and SMS marketing automation platform purpose-built for ecommerce, with first-class integrations into Shopify, BigCommerce, WooCommerce, Magento, Wix, Square Online, and other storefronts. The platform unifies automation workflows, campaign builders, segmentation, popups and forms, web push, product recommendations, A/B testing, and reporting to drive customer engagement and revenue. Omnisend's REST API exposes contacts, events, products, product categories, segments, campaigns, batches, email templates, email content, universal layouts, images, brands, and analytics reports. Authentication uses an API key passed via the `X-API-KEY` header, or OAuth 2.0 authorization-code flow with resource-scoped permissions for app-based integrations on the Omnisend App Market.
Reference-quality API operations across every facet — a rich contract, published governance, transparent operations, and machine-readable commercial terms.
API Evangelist profiles Omnisend the way a machine reads it — 58 machine-readable artifacts across 13 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Omnisend scores 72.5/100 (exemplar), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Omnisend
Each block below is one kind of artifact we hold for Omnisend. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 13
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Omnisend Analytics API
The Analytics API from Omnisend — 2 operation(s) for analytics.
Omnisend Batches API
The Batches API from Omnisend — 3 operation(s) for batches.
Omnisend Brands API
The Brands API from Omnisend — 1 operation(s) for brands.
Omnisend Campaigns API
The Campaigns API from Omnisend — 5 operation(s) for campaigns.
Omnisend Contacts API
The Contacts API from Omnisend — 3 operation(s) for contacts.
Omnisend EmailContent API
The EmailContent API from Omnisend — 2 operation(s) for emailcontent.
Omnisend EmailTemplates API
The EmailTemplates API from Omnisend — 4 operation(s) for emailtemplates.
Omnisend EmailUniversalLayouts API
The EmailUniversalLayouts API from Omnisend — 2 operation(s) for emailuniversallayouts.
Omnisend Events API
The Events API from Omnisend — 1 operation(s) for events.
Omnisend Images API
The Images API from Omnisend — 3 operation(s) for images.
Omnisend ProductCategories API
The ProductCategories API from Omnisend — 2 operation(s) for productcategories.
Omnisend Products API
The Products API from Omnisend — 2 operation(s) for products.
Omnisend Segments API
The Segments API from Omnisend — 3 operation(s) for segments.
Scroll within the panel for all 13 ·
Postman Collections 1
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Omnisend REST API
POSTMANOpen Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Omnisend REST API
OPEN COLLECTIONArazzo Workflows 13
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
Omnisend Copy and Send Campaign
Copy an existing campaign, read the copy to confirm, then queue it for sending.
ARAZZOOmnisend Create and Send Campaign
Create a campaign, read it back to confirm, then queue it for sending.
ARAZZOOmnisend Create and Verify Product Category
Create a product category, then read it back by id to confirm it was stored.
ARAZZOOmnisend Create and Verify Contact
Create or update a contact, then read it back by id to confirm the write.
ARAZZOOmnisend Create and Verify Product
Create a product, then read it back by id to confirm it was stored.
ARAZZOOmnisend Create Segment and Read Statistics
Create a segment, read it back to confirm, then pull its membership statistics.
ARAZZOOmnisend Refresh Product Catalog Entry
Read a product by id, then replace it with an updated representation.
ARAZZOOmnisend Subscribe and Trigger Welcome
Create or update a subscriber, then send a subscribed event to trigger the welcome automation.
ARAZZOOmnisend Create and Tag Contact
Create or update a contact, then apply tags to it for segmentation.
ARAZZOOmnisend Track Added-to-Cart Event
Create or update the shopper contact, then send an added-to-cart customer event for them.
ARAZZOOmnisend Track Placed Order Event
Create or update the buyer contact, then send a placed-order customer event for them.
ARAZZOOmnisend Upsert a Contact
Look up a contact by id and update it if it exists, otherwise create or update it by email.
ARAZZOScroll within the panel for all 13 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Omnisend Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Omnisend Finops
FINOPSFeatures 18
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 18 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Omnisend Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Omnisend API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Omnisend Contact
JSON SCHEMAOmnisend Customer Event
JSON SCHEMASecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Omnisend — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 13
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 13 ·
Build 8
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 8 ·
Access & Security 6
Authentication, authorization, and security posture
Operate 6
Status, limits, changes, and where to get help
Commercial 5
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/omnisend · machine-readable index on apis.io