Omnisend API
API v5 removal
Stops workingSubscribe to Omnisend APIShare
On June 30, 2027, the Omnisend API will shut down its v5 version. All requests to /v5/* endpoints will fail after this date. Omnisend API has deprecated this version and scheduled it for sunset.
Calls it hits
/v5/*
What to use instead of these calls
Migrate your calls to the v2026-03-15 API. This transition requires using the base path api.omnisend.com/api/ for contacts, products, categories, batches, and events, alongside an Authorization header with your key and an Omnisend-Version header set to 2026-03-15 on every request.
In Omnisend API's words
The v5 API is deprecated and will be sunset on June 30, 2027 .
Facts
- API
- Omnisend API
api.omnisend.com - Kind
- Removal
- Takes effect
- June 30, 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 /v5/* on Omnisend API stop working on June 30, 2027.
What happens to calls after June 30, 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
-
/v3/*Removal Stops workingin 420 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 June 30, 2027.