> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/developer/api/mep/status.md). # 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 \** | 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](https://doc.batch.com/developer/api/mep/transactional) | Deprecated | None planned | [CEP Profile API + Trigger Automations](https://doc.batch.com/getting-started/other/implementation-guides/mep-to-cep-migration/how-to-switch-from-the-transactional-api-to-the-profile-api) | | [Push Campaigns](https://doc.batch.com/developer/api/mep/campaigns) | Deprecated | **31 December 2026** | [CEP Campaigns API](https://doc.batch.com/developer/api/cep/campaigns) | | [In-App Campaigns](https://doc.batch.com/developer/api/mep/in-app-campaigns-api) | Deprecated | **31 December 2026** | No API equivalent. In-App messages are built from the dashboard, in [Orchestrations](https://doc.batch.com/getting-started/features/customer-engagement-platform/orchestration/trigger-automations). | | [Custom Audience](https://doc.batch.com/developer/api/mep/custom-audience) | Deprecated | **31 December 2026** | [CEP Audiences API](https://doc.batch.com/developer/api/cep/audiences) | | [App Data](https://doc.batch.com/developer/api/mep/app-data) | Deprecated | **31 December 2026** | [CEP Catalogs API](https://doc.batch.com/developer/api/cep/catalogs) | | [Webhooks](https://doc.batch.com/developer/api/mep/webhooks) | Deprecated | **31 December 2026** | [CEP Export API](https://doc.batch.com/developer/api/cep/exports) | | [Custom Data](https://doc.batch.com/developer/api/mep/custom-data-api) | Deprecated | None planned | [CEP Profile API](https://doc.batch.com/developer/api/cep/profiles/update) | | [GDPR](https://doc.batch.com/developer/api/mep/gdpr) | Not deprecated | None planned | - | | [Export](https://doc.batch.com/developer/api/mep/export) | Deprecated | None planned | [CEP Exports API](https://doc.batch.com/developer/api/cep/exports) | | [Trigger Events](https://doc.batch.com/developer/api/mep/trigger-events-api) | Deprecated | None planned | [CEP Profile API](https://doc.batch.com/developer/api/cep/profiles) | ### 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](https://doc.batch.com/developer/api/cep). The main differences with the MEP APIs (authentication header, project key, endpoint structure) are described in [Differences with v1 APIs](https://doc.batch.com/developer/api/cep#differences-with-v1-apis). Step-by-step migration guides are available in [MEP to CEP migration](https://doc.batch.com/getting-started/other/implementation-guides/mep-to-cep-migration). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://doc.batch.com/developer/api/mep/status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.