Vendor push specification updates

Updated at:

This document summarizes the latest compliance requirements, mandatory changes, and effective/deadline dates for push services from major vendors, such as Huawei, Xiaomi, OPPO, and vivo. We recommend that you review this document regularly to prevent throttling, incorrect message categorization, or loss of functionality due to non-compliance.

Latest updates

  • April 1, 2027: vivo to enforce template-based push controls for five system message categories in legacy applications.

  • December 31, 2026: Deadline for Xiaomi private message template integration.

  • July 1, 2026: Xiaomi's new message template policy takes effect.

  • January 1, 2026: vivo's local notification category controls take effect.

  • December 31, 2025: Deadline for OPPO private message template migration for existing users.

Xiaomi

Template-based push rules

Effective date and integration deadline

  • Effective Date: 00:00 on July 1, 2026

  • Integration Deadline: 23:59 on December 31, 2026

Requirements

Xiaomi Push has released new rules for template-based push notifications. These rules apply to all applications that send push messages to Xiaomi devices:

  • Requirement for sending private messages: All private messages must be sent with both a channel_id and a template ID. Transmit only the message variables to the Xiaomi push service for assembly.

  • Template parameter reference:

    • When using the Push and MassPush APIs, pass AndroidNotificationXiaomiChannel and AndroidXiaomiTemplateId. If the template contains variables, pass them as a JSON object string using AndroidXiaomiTemplateParams.

    • When using the PushV2 and MassPushV2 APIs, pass Channel and TemplateId under PushTask.Notification.Android.Options.Xiaomi. If the template contains variables, pass them as a JSON object string using TemplateParams.

    • When passing a template ID, you must also pass the Xiaomi channel. When passing template parameters, you must also pass the template ID.

  • For applications that have already integrated private messages: You must complete the template integration by December 31, 2026. Failure to do so will affect the delivery of private messages.

  • For applications that have not yet integrated private messages: We recommend that you first plan your message categories, and then apply for channel access and private message templates on the Xiaomi Push operations console.

  • Official Announcement: Announcement on new rules for template-based push notifications

vivo

System message template requirements

Enforcement date

Effective April 1, 2027, vivo will enforce template-based push for five categories of system messages in legacy applications: subscription reminders, account and asset updates, schedules and to-dos, device information, and order and logistics updates. After this date, system messages in these categories not sent using a template will fail to be delivered. We recommend completing this integration in advance.

Requirements

  • Scope: Template integration is required for five categories of system messages: subscription reminders, account and asset updates, schedules and to-dos, device information, and order and logistics updates. This requirement does not apply to operational messages or instant messages.

  • Template application and usage: On the vivo push operations console, go to vpush Template Management to select an available official template, or submit a custom template and use it after approval. When sending a notification, include the template ID and the corresponding variable values. The vivo service then uses this information to generate the notification title and content.

  • EMAS API adaptation: Mobile Push now supports sending vivo template notifications through the following APIs:

    • When using the Push and MassPush APIs, set AndroidVivoTemplateId and AndroidVivoTemplateParams. For MassPush, these parameters are located within each task in the PushTask array.

    • When using the PushV2 and MassPushV2 APIs, set TemplateId and TemplateParams under Notification.Android.Options.Vivo for each push task. For PushV2, the task is the PushTask object; for MassPushV2, the tasks are in the PushTasks array.

  • Template parameter format: Template parameters must be a JSON object string. Keys are the variable names defined in the template, and values are the actual content. You must pass all variables that the template defines. When you pass template parameters, you must also pass a template ID.

  • Subscription reminder integration: You must also create and bind a subscription channel and complete the client-side subscription authorization, as described in the vivo integration guide.

  • Official Integration Guide: vpush message template integration guide

  • EMAS Integration Instructions: For the template application process, parameter examples, and usage notes, see the vivo section in Best practices for vendor channel push restrictions and message categorization.

Local notification category controls

Effective date

January 1, 2026

Requirements

Starting on this date, vivo will officially implement category controls for local notifications. Developers must complete the category registration in the vivo push console for the NotificationChannel objects that their application creates for local notifications.

OPPO

New OPUSH private message policy

Migration deadline

December 31, 2025 (for existing users)

Requirements

OPPO has released a new OPUSH private message policy: