Omnisend API
API v3 removal
Stops workingSubscribe to Omnisend APIShare
Omnisend will sunset its v3 API on December 31, 2027. This removal affects all calls to /v3/* endpoints. After this date, requests to these endpoints will fail.
Calls it hits
/v3/*
What to use instead of these calls
Move to the v2026-03-15 API using the base path api.omnisend.com/api/ for contacts, products, categories, batches, and events. Requests require the Authorization header with Omnisend-API-Key and an Omnisend-Version header set to 2026-03-15.
In Omnisend API's words
The v3 API is deprecated and will be sunset on December 31, 2027 .
Facts
- API
- Omnisend API
api.omnisend.com - Kind
- Removal
- Takes effect
- December 31, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Omnisend API's own pages
Questions
When does this change take effect?
Calls to /v3/* on Omnisend API stop working on December 31, 2027.
What happens to calls after December 31, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Omnisend API 1
-
/v5/*Removal Stops workingin 236 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before December 31, 2027.