How to: batch mep cep five api field map

Use this local guide before 2026-12-31. Re-check official vendor documentation for authoritative dates. This site does not call vendor APIs or store tokens.

1. Step 1. Confirm Dec 31 2026 EOL for Push Campaigns, In-App, Custom Audience, App Data, and Webhooks on MEP status
2. Step 2. List integrations still calling those five MEP bases or literals
3. Step 3. Map Push Campaigns → CEP Campaigns API; Custom Audience → Audiences; App Data → Catalogs; Webhooks → Export
4. Step 4. Treat In-App as no API equivalent — rebuild via Orchestrations in the dashboard
5. Step 5. Switch authentication to Bearer token plus X-Batch-Project header per CEP differences
6. Step 6. Leave Transactional/Custom Data/GDPR notes aside when they have no EOL on the same table
7. Step 7. Update Postman/CI contract tests to expect rejection after EOL
8. Step 8. Export Markdown field map with status + migration-prep URLs into the ticket

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates. Export your Markdown pack into the change ticket with the official URLs listed on the home page.

Context for operators: Batch MEP Push/In-App/Custom Audience/App Data/Webhooks EOL Dec 31 2026 → CEP Campaigns/Audiences/Catalogs/Export (messaging API domain). The gap this wedge fills: 官方 status 有表；缺可交互五 API 对照 + In-App 无等价 + 鉴权头笔记。不做 Batch 控制台 SaaS。 Keep owners assigned on every residue row so nothing silently slips past the deadline. When in doubt, re-open the official source pages rather than trusting a cached screenshot.