What we do
Tools
Industries
Department
How we workLet's talk →
Home/Omnisend
Omnisend

The Omnisend API Has a New Version, and v5 Code Has Until June 30, 2027

The contact sync written against Omnisend's v5 API still runs. Omnisend has marked v5 deprecated, though, and the current version, 2026-03-15, moves the base URL, swaps the auth header and reshapes contacts. Some of the changes fail loudly. Others, like how tags are saved, change your data without an error. Omnisend itself is email, SMS and push marketing for online stores, and the API is how a system without a native app sends it contacts, products and store activity.

Where Omnisend stops

It sends the campaign without knowing what's in stock, a customer's loyalty tier or their support history.

Stuck on Omnisend? Let's solve it →
An Omnisend API request now

Base URL: https://api.omnisend.com/api/, with the header Omnisend-Version: 2026-03-15 on every request.

Auth: Authorization: Omnisend-API-Key followed by your key. Keys are created in the API keys section of your Omnisend account. OAuth 2.0 with a Bearer token is supported too.

Lists: paged with cursors, not full next and previous URLs.

v5: still answers at /v5/ with the X-API-KEY header, but it's deprecated and goes away on June 30, 2027.

Omnisend v5 beside version 2026-03-15

From Omnisend's own migration guide. Products, categories, batches and events move to the new base URL too.

Deprecated

v5

  • https://api.omnisend.com/v5/ and an X-API-KEY header.
  • No version header.
  • Paging through paging.next and paging.previous links.
  • Errors shaped as error plus fields.
  • Contacts carry top-level email, phone and status, keyed by contactID.
Current

2026-03-15

  • https://api.omnisend.com/api/ and Authorization: Omnisend-API-Key.
  • Omnisend-Version: 2026-03-15 required.
  • paging.cursors.after and before, with hasMore telling you there's more.
  • RFC 9457 problem details: type, title, status, detail and an errors array.
  • Contacts carry an identifiers array, keyed by id.

Code that only reads campaigns needs a header change and new paging. Code that writes contacts needs real rework.

What a straight port from v5 gets wrong

The URL and header swap is the easy part. These are the changes that don't throw an error.

Tags disappear from contacts

How you'll know: A contact had five tags. After one update it has the one tag your code sent.

Fix: tags now replaces the list rather than adding to it, and an empty array clears every tag. Send the full list, or add and remove tags with POST and DELETE /api/contacts/tags.

The same shopper shows up twice

How you'll know: Contacts captured by phone number appear again after the next sync.

Fix: POST /api/contacts always creates a contact unless the email matches one that exists. Keep the Omnisend id you get back, and update known contacts with PATCH /api/contacts/{id}.

Welcome messages you meant to skip

How you'll know: Imported customers get a welcome email or SMS.

Fix: sendWelcomeEmail is gone. Set sendWelcomeMessage on each identifier instead.

Contacts rejected over the address

How you'll know: Requests fail on the state field for contacts that went through fine on v5.

Fix: Send state as an ISO 3166-2 code.

A sync that stops after the first page

How you'll know: Only the first batch of contacts or campaigns is ever processed.

Fix: Loop on paging.cursors.after while hasMore is true. The old paging.next URL isn't there to follow.

Failures nobody sees

How you'll know: Your error handler reads error and fields, finds nothing and logs a blank.

Fix: Parse the problem-details shape. Omnisend's v5 docs also note that most failed POST requests are logged in the app under Store Settings, API, API Issues, so look there when a call fails without explanation.

A pet supplies store whose restock emails ran ahead of the shelf

Pet supplies store · Omnisend flows on WooCommerce

Before

Back-in-stock and low-stock emails went out based on the last sync, so some of them promised items that had already sold through.

After

Those automations now check real inventory levels before they send.

Customers only hear about stock that's actually there.

Store data the Omnisend apps leave behind

Omnisend's store apps bring in orders, customers and products from the platforms it supports. What they can't bring is anything held outside the store: the stock count in an inventory system, a loyalty tier, a wholesale flag in the CRM, an open support ticket.

Through the API, that information becomes product records, contact fields and tags Omnisend's segments and automations can use. n-frames builds those feeds on the current API version, written against the contact rules above so tags and welcome messages behave. For which platforms connect natively and how events reach workflows, see Omnisend integrations.

Omnisend, the API and the platform around it

What is Omnisend used for?

Email, SMS and push marketing for online stores: campaigns plus automations such as cart abandonment, welcome series, post-purchase follow-up and order updates. It's aimed mainly at Shopify, WooCommerce and BigCommerce merchants.

How much does Omnisend cost, and is there a free plan?

There's a free plan for a small number of contacts and sends. Paid plans scale with contacts and add more automation and reporting. Prices change, so check omnisend.com/pricing. Whichever plan you're on, the API is how n-frames connects Omnisend to the systems beyond your store.

Does Omnisend have a subject line tester?

Yes, a free one on Omnisend's website. It scores a subject line on length, words likely to trip spam filters and emoji use. Treat it as a sanity check, and still test against your own list.

Is Omnisend good for Shopify stores specifically?

Shopify is where Omnisend fits most naturally. The app syncs orders, customers and products, and the automation templates assume that data is there. A Shopify store rarely needs the API for the basics; it's for data from outside the store.

Omnisend vs Mailchimp: what's the real difference?

Mailchimp began as general email marketing and added store features later. Omnisend started with online stores, so its templates, segments and SMS lean on store data from the outset. For a Shopify or WooCommerce shop, that usually means a useful automation is running sooner.

Omnisend vs Klaviyo: how do they really compare?

Both are built for online stores, start free and handle email and SMS. They differ in how they bill as a list grows and how far segmentation goes. Omnisend vs Klaviyo sets the two side by side.

How does Omnisend handle ecommerce marketing automation?

On its own, for anything that starts with an order, a cart or a product view on a connected store. Automations that should react to something outside the store, a support ticket, a loyalty change, a subscription renewal, need that data sent through the API, and n-frames builds those connections.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.