canonical: https://jentic.com/apis/omnisend.com/omnisend

# Omnisend API

Jentic publishes the only available OpenAPI specification for Omnisend API, keeping it validated and agent-ready. The Omnisend v5 API is the integration layer for Omnisend's email and SMS marketing platform aimed at e-commerce brands. It exposes 12 endpoints covering contact management, custom event tracking, campaign listing, product catalogue sync, order ingestion, and cart updates - the data signals Omnisend uses to build automations like cart abandonment and post-purchase flows. Authentication uses bearer tokens issued from the Omnisend store settings.

## For AI agents

Sync e-commerce contacts, products, orders, and carts into Omnisend and track custom events that trigger email and SMS automations.

## Scope

Does not handle template editing, automation-flow design, or paid-media buying - use for contact, event, order, cart, and product data sync only.

## Capabilities

- Create or update contacts with consent status, tags, and custom fields
- Track custom events that fire Omnisend automation flows
- Push order data into Omnisend to feed post-purchase and reorder flows
- Update cart records to drive abandoned-cart automation
- Sync product catalogue records used in email content blocks
- List and retrieve campaigns to monitor scheduled and sent campaigns
- Read individual contacts by ID for personalisation lookups

## Use cases

### E-Commerce Contact Sync

Stores sync new and returning customers into Omnisend via POST /contacts (which creates or updates by email/phone). The endpoint accepts consent status, tags, and custom fields, so a single call fully describes the subscriber state for downstream segmentation.

Example prompt: POST /contacts with email, consent=subscribed, and tags=['new-customer'] for every order placed in the last hour.

### Cart Abandonment Automation

When a shopper adds items but doesn't check out, POST /carts records the cart state. Omnisend uses the cart events to trigger its abandoned-cart automation, which sends a recovery email or SMS after a configurable delay. Update the cart with a new POST when items change so the recovery message reflects the latest contents.

Example prompt: POST /carts with the contact's email, the cart ID, and an array of cart items so Omnisend's abandoned-cart flow can target the contact.

### Custom Event Tracking

POST /events records arbitrary custom events (browse_product, completed_quiz, downloaded_guide) that can be referenced as triggers inside Omnisend's automation builder. This lets marketers build flows that fire on product behaviour beyond the built-in cart and order events.

Example prompt: POST /events with eventType='product_viewed', the contact email, and a properties object containing productId and productName.

### AI Agent Marketing Operations

An AI agent integrated through Jentic can take a CSV of new sign-ups and a list of recent orders, and sync both into Omnisend in one go - calling POST /contacts and POST /orders behind the scenes. Jentic stores the bearer token encrypted, so the agent never sees the raw credential.

Example prompt: Search Jentic for 'create omnisend contact', load POST /contacts, and execute it for 250 sign-ups; then call POST /orders for each order placed today.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contacts` | Create or update a contact |
| POST | `/events` | Track a custom event |
| POST | `/orders` | Create an order record |
| POST | `/carts` | Create or update a cart |
| POST | `/products` | Create a product catalogue entry |
| GET | `/campaigns` | List campaigns |

## Key resources

- **Contacts** — Create or update contacts; retrieve and patch a contact by ID.
- **Events** — Track custom events that fire automation flows.
- **Campaigns** — List campaigns and retrieve a campaign by ID.
- **Products** — List products and create product catalogue entries.
- **Orders** — List orders and create order records that drive post-purchase flows.
- **Carts** — Create or update cart records to drive cart-abandonment automation.

## Why Jentic

- **Setup:** Wiring the Omnisend API by hand means managing its bearer token and building each contact, event, order, cart, and product call against api.omnisend.com/v5 yourself. Through Jentic you install once, import the Omnisend API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Omnisend takes its contact, event, order, and product data in the request body rather than the URL path, so you limit the agent to the operations it needs, such as creating a contact or tracking an event. Reading campaigns or writing orders are excluded unless you add those operations to the allowed set.
- **Credential handling:** Your Omnisend token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an omnisend contact' or 'track an omnisend event', and Jentic returns the matching Omnisend operation (POST /contacts or POST /events) with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Klaviyo API** — Email and SMS marketing platform with deeper segmentation and more complex flows.
- **Mailchimp Marketing API** — General-purpose email marketing platform with broad SMB reach.
- **Shopify Admin API** — E-commerce platform that sources orders, customers, and products for Omnisend.

## FAQ

### Why is there no official OpenAPI spec for Omnisend API?

Omnisend does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Omnisend API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Omnisend API use?

Omnisend uses bearer tokens (Authorization: Bearer ...) generated from the Omnisend store settings. Jentic stores this token encrypted in its vault and attaches it to each request, so agents reference only a credential handle.

### Can I trigger Omnisend's abandoned-cart automation through the API?

Yes. POST /carts with the contact email, cart ID, and item array creates or updates the cart record. Omnisend's abandoned-cart flow uses these cart updates as triggers, so timely POSTs drive the automation.

### What are the rate limits for the Omnisend API?

Omnisend applies a per-second request limit at the v5 API level (typically around 400 requests per minute per store). Watch for HTTP 429 responses and back off; batch contact sync into POST /contacts calls rather than parallel-spamming.

### How do I track a custom event for an automation flow through Jentic?

Search Jentic for 'track omnisend custom event', and the SDK returns POST /events. Provide the contact identifier and the eventType plus a properties object - Omnisend's automation builder can reference this event as a trigger.

### Does the Omnisend API send transactional emails directly?

The v5 API exposes campaigns, contacts, events, and e-commerce data - it does not include a direct transactional-send endpoint. Transactional emails are configured as automation flows inside Omnisend, triggered by events you POST to /events.

### Can I limit what my agent is allowed to do with the Omnisend API?

Yes. Jentic One is self-hosted, so you run your own instance and your own rules decide which Omnisend operations and credentials the agent may use. You can allow just the calls a task needs, such as creating a contact with POST /contacts or tracking an event with POST /events, while excluding writing orders with POST /orders or listing campaigns with GET /campaigns. Because Omnisend takes its contact, event, order, and product data in the request body rather than the URL path, the allowed operation set is what bounds the agent's access.