DocsICP FilingConsole
Documentation
Home Page Enterprise Mobile Application Studio Mobile Push Product Overview Product overview Updates to third-party push specifications

Updates to third-party push specifications

Updated at:
Copy as MD
Product
My Favorites

This document summarizes the latest compliance requirements, mandatory changes, and effective dates for the push service from major vendors such as Huawei, Xiaomi, OPPO, and vivo. Developers should review this document regularly to prevent service disruptions, such as throttling, miscategorization, or feature failures, that can result from non-compliance.

Latest updates

  • 2026-12-31: Deadline for Xiaomi private message template integration.

  • 2026-07-01: New rules for Xiaomi message template pushes take effect.

  • 2026-01-01: vivo local notification classification controls take effect.

  • 2025-12-31: Migration deadline for OPPO private message templates for existing users.

Xiaomi

New rules for message template pushes

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 introduced new rules for message template pushes. These rules affect all applications that send push notifications to Xiaomi devices:

  • Private message delivery requirements: All private messages must be sent with both a channel_id and a template ID. Send only message variables to the Xiaomi push service for message assembly.

  • Template parameter descriptions:

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

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

    • You must pass the Xiaomi channel with a template ID, and the template ID with any template parameters.

  • For applications that already use private messages: You must plan and complete the migration to the new template system by December 31, 2026, to avoid disrupting the delivery of private messages.

  • For applications that do not yet use private messages: We recommend first planning your message classification, then applying for a channel and a private message template on the Xiaomi Push platform.

  • Official announcement: Update Notice on New Rules for Message Template Push

vivo

Local notification classification controls

Effective date

January 1, 2026

Requirements

Starting on this date, vivo will enforce local notification classification controls. Developers must use the vivo push console to perform classification reporting for local notifications that use the NotificationChannel created by the client.

  • Consequences of not reporting: By default, vivo classifies unreported notifications as an "operational message", which may affect their delivery rate.

  • Instructions: vivo Local Notification Integration Guide

  • Official Announcement: View

OPPO

OPUSH private message specifications

Migration deadline

December 31, 2025 (for existing users)

Requirements

OPPO has released new specifications for the OPUSH private message feature:

Previous：TermsNext：Billing