Status

This page is the single source of truth for the status of every MEP API.

All MEP APIs are deprecated, as Batch main product is now the CEP. They are no longer evolving, and some of them stop working after 31 December 2026.

What "deprecated" means

A deprecated API is still a supported API. Concretely:

• It keeps working and stays documented. Your existing integration does not break.
• We fix critical bugs and security issues, and nothing else.
• It will never gain a new endpoint, a new field or a new capability. New Batch features (new channels, new profile data, new orchestration types) are only exposed through the CEP APIs.
• Some deprecated APIs also have an end-of-life date. After that date they stop responding and their documentation is archived. The table below tells you which ones.

The two statuses used on this page

Status	What it means for you
Deprecated	The API keeps working, with critical fixes only. No end-of-life date is planned. You can keep calling it, including after your project has migrated to the CEP.
Deprecated, end of life on <date>	The API keeps working until that date. After it, the API is no longer supported and is shut down: calls are rejected and the documentation is archived. You need to migrate before the date.

Status of each API

API	Status	End of life	Recommended replacement
Transactional	Deprecated	None planned	CEP Profile API + Trigger Automations
Push Campaigns	Deprecated	31 December 2026	CEP Campaigns API
In-App Campaigns	Deprecated	31 December 2026	No API equivalent. In-App messages are built from the dashboard, in Orchestrations.
Custom Audience	Deprecated	31 December 2026	CEP Audiences API
App Data	Deprecated	31 December 2026	CEP Catalogs API
Webhooks	Deprecated	31 December 2026	CEP Export API
Custom Data	Deprecated	None planned	CEP Profile API
GDPR	Not deprecated	None planned	-
Export	Deprecated	None planned	CEP Exports API
Trigger Events	Deprecated	None planned	CEP Profile API

After 31 December 2026

The five APIs marked 31 December 2026 above are no longer supported after that date. They are shut down: calls are rejected and their documentation is archived.

The other MEP APIs listed above keep working, including after your project has migrated to the CEP. There is no plan to shut them down in 2027. They remain deprecated: they will not receive new capabilities, and we recommend moving to the CEP equivalent when one exists.

Migrating to the CEP

The CEP APIs are documented under API - Customer Engagement Platform. The main differences with the MEP APIs (authentication header, project key, endpoint structure) are described in Differences with v1 APIs.

Step-by-step migration guides are available in MEP to CEP migration.