PushTask-阿里云帮助中心

Parameter	Type	Description	Example
	object	Push task object
Action	string	The push method. This is an optional parameter. The default value is `PUSH_IMMEDIATELY` (immediate push). Important The `MassPushV2` batch push API supports only the following push methods: `PUSH_IMMEDIATELY` (immediate push) `SCHEDULED_PUSH` (scheduled push)	PUSH_IMMEDIATELY
Target	object	The target object for the message push. This parameter is optional when the `Action` operation type is `CREATE_CONTINUOUS_PUSH` (create a continuous push task).
Type	string	The push target type. Important The `MassPushV2` batch push API and `CONTINUOUS_PUSH` continuous push support only the following three target types: `DEVICE` `ACCOUNT` `ALIAS`	DEVICE
Value	string	Set the push target based on `Target.Type`. Separate multiple targets with commas. The target types and their values are described as follows: Note `DEVICE`: Device ID, such as deviceid1,deviceid2. You can specify up to 1,000 device IDs. `ACCOUNT`: Account ID, such as account1,account2. You can specify up to 1,000 account IDs. `ALIAS`: Alias, such as alias1,alias2. You can specify up to 1,000 aliases. `TAG`: Supports one or more tags. For more information about the format, see Tag format specifications. `ALL`: Push to all devices. You do not need to set a value. Pushing to all devices may increase costs. Use this feature with caution.	value
Platform	string	The platform type. This is an optional parameter.	IOS
Message	object	The pass-through message data sent to the device. The total length cannot exceed 4,000 bytes. Note Length calculation The length is calculated based on the byte length of the UTF-8 encoded string after the Message object is serialized into JSON. A Chinese character typically occupies 3 bytes in UTF-8 encoding.
Title	string	The title of the message to send.	title
Body	string	The content of the message to send.	{"key": "value"}
Notification	object	The vendor notification data sent to the device. Important If you set both `Message` and `Notification`, the device receives only one. The sending rules are as follows: If the device is online, pass-through message data is sent. If the device is offline, a system notification is sent.
Title	string	The title of the push notification. Note The length limits are as follows: For iOS/HarmonyOS, the byte length cannot exceed 200. For Android, the character length cannot exceed 50.	您有一条新消息
Body	string	The content of the push notification. Note The length limits are as follows: For iOS, HarmonyOS, and Android, the character length cannot exceed 200.	尊敬的客户，您好！您的预约订单已取消成功。
Ios	object	iOS notification configuration
Subtitle	string	The subtitle of the iOS notification.	请查收订单。
Music	string	The iOS notification sound. Specify the name of the audio file stored in the app bundle or the sandbox Library/Sounds directory. For more information, see How to set the notification sound for iOS push. Note If you specify an empty string (""), the notification is silent. If this parameter is not set, the default value is `default`, which is the system prompt sound.	default
Badge	integer	The iOS application badge.	1
BadgeAutoIncrement	boolean	Specifies whether to enable the badge auto-increment feature. This is an optional parameter. The default value is false. Note This parameter cannot be used with the badge setting parameter. The badge auto-increment feature is maintained by the Alibaba Cloud push server, which counts the badges for each device. You must use SDK version 1.9.5 or later and actively sync the badge number to the server through the SDK.	false
Silent	boolean	Controls whether to enable silent push mode. Note When you send a silent notification, you can leave the `title` and `body` parameters empty.	false
Mutable	boolean	Enables extended notifications and controls whether iOS notifications support processing by the Notification Service Extension. Note This must be set to true when you send a silent notification. The extension processing time cannot exceed 30 seconds. A timeout causes the notification to display the original content. You must add a Notification Service Extension to your application.	true
Category	string	Specifies the category identifier for an iOS notification. This defines the notification's interactive behavior and display style. Note The category must be pre-registered in the app to take effect. Different categories can define different sets of actions.	MESSAGE_REPLY
CollapseId	string	A unique identifier that controls notification merging. Notifications with the same identifier are overwritten.	order_status_update_12345
ThreadId	string	The thread identifier for iOS notification grouping. It is used to classify and collapse related notifications. Note Notifications with the same thread-id are automatically grouped. Multiple related notifications are collapsed into one notification group. Users can expand the group to view all notifications within it.	news_category_tech
InterruptionLevel	string	The interruption level. This is an optional parameter. Valid values are: `passive`: The system adds the notification to the notification list without lighting up the screen or playing a sound. `active`: The system displays the notification immediately, lights up the screen, and can play a sound. `time-sensitive`: The system presents the notification immediately, lights up the screen, and can play a sound, but does not override system notification controls. `critical`: The system displays the notification immediately, lights up the screen, and plays a sound, bypassing the mute switch.	active
RelevanceScore	number	The relevance score of the notification message. It is used to control the priority and display policy of the notification.	0.5
ExtParameters	string	Custom extension properties for iOS notifications. Note The parameter must be passed in a standard JSON Map format. An incorrect format causes parsing to fail.	{"attachment": "https://xxxx.xxx/notification_pic.png"}
LiveActivity	object	Live Activities parameter object. Important Live Activities push only supports pushing to a single device of the `DEVICE` type. When you push to Live Activities, you can leave the title and body parameters empty.
Id	string	The unique identifier for a Live Activity. It associates the activity instance on the device with the push target on the server. Important This `ID` must be the same as the `forActivityId` parameter of the `registerLiveActivityPushToken` method in the client SDK. The server uses this `ID` to locate the specific activity instance during a push.	FOOD_DELIVERY_ORD20231201001
Event	string	Starts, updates, or ends a Live Activity.	start
AttributesType	string	The type of Live Activity to start. Note This is required when `Event` is `start`.	OrderActivityAttributes
Attributes	string	Static pass-through parameters for iOS Live Activities push. They are used to transmit immutable business identification information. Note This is required when `Event` is `start`.	{ "orderId": "ORD20231201001", "restaurantName": "美味餐厅", "customerAddress": "xx区xx路xx号", "orderType": "delivery" }
ContentState	string	Dynamic pass-through parameters for a Live Activity. They contain real-time updatable status information and changing data. Note Avoid overly frequent updates. An interval of 5 seconds or more is recommended. Update multiple fields in a batch to reduce the number of pushes. Consider the user experience and avoid screen flickering. Must be a valid JSON string.	{ "status": "delivering", "estimatedTime": "10分钟", "progress": 80, "driverName": "李师傅", "currentStep": "配送员正在路上"} }
DismissalDate	integer	Sets the retention period for a finished Live Activity on the lock screen. This lets users view information after the activity has ended. It is a Unix timestamp in seconds.	1701439800
StaleDate	integer	Sets the expiration timestamp for the content of an iOS Live Activity. It is a Unix timestamp in seconds. Note After the specified time is reached, the system automatically marks the activity as expired. Expired activities are removed from the Live Activity and the lock screen. This prevents outdated information from occupying the user interface for a long time.	1701425400
ApnsEnv	string	iOS notifications are sent through the Apple Push Notification service (APNs) center. You must specify the environment information. This is an optional parameter. The default is the production environment. DEV: Development environment, for applications installed and tested directly from Xcode. PRODUCT: Production environment, for applications distributed through the App Store, TestFlight, Ad Hoc, and enterprise channels.	DEV
Hmos	object	HarmonyOS notification configuration.
Category	string	The notification message category. This is an optional parameter. The default category is `MARKETING`. Note After you apply for the right to self-classify notification messages, this parameter is used to identify the message type. Different notification message types affect how messages are displayed and how users are reminded. For more information, see Notification.category on the official HarmonyOS website.	IM
SlotType	string	Uses the specified type of notification channel. Note This is only valid for Alibaba Cloud's proprietary channels. For more information, see SlotType on the official HarmonyOS website.	SOCIAL_COMMUNICATION
NotifyId	integer	Specifies the unique identifier (notifyId) for each message when it is displayed in the notification bar. If not provided, the push service automatically generates a unique identifier. Different notification messages can use the same notifyId to allow new messages to overwrite old ones. For more information, see Notification.notifyId on the official HarmonyOS website.	123456
Action	string	Specifies the action corresponding to the ability of an in-app page. Note For more information, see ClickAction.action on the official HarmonyOS website.	com.example.action
Uri	string	The URI corresponding to the ability of an in-app page. Note If there are multiple abilities, specify the action and URI for each ability separately. The system prioritizes using the action to find the corresponding in-app page. For more information, see ClickAction.uri on the official HarmonyOS website.	https://www.example.com:8080/push/example
RenderStyle	string	The notification message style. This is an optional parameter. The default is a normal notification.	NORMAL
ImageUrl	string	The URL for the large icon on the right side of the notification. The URL must use the HTTPS protocol. Note Supported image formats are png, jpg, jpeg, heif, gif, and bmp. The image dimensions (length × width) must be less than 25,000 pixels. For more information, see Notification.image on the official HarmonyOS website.	https://example.com/xxx.png
InboxContent	array	When `RenderStyle` is `MULTI_LINE`, you must fill in this field to define the content for the multi-line text style. It supports up to 3 lines of content.
	string	Text.	1. 您有一个事项待处理
ExtParameters	string	Sets custom extension properties for the notification message. This is used to pass additional business data. Note The parameter must be passed in a standard JSON Map format. An incorrect format causes parsing to fail.	{"key": "value"}
TestMessage	boolean	Enables test messages. Note For more information, see the HarmonyOS push parameter TestMessage.	true
ReceiptId	string	The receipt ID for the HarmonyOS channel. This ID can be found in the receipt parameter settings on the HarmonyOS channel push operations platform. Note If the default receipt configuration on the HarmonyOS channel push operations platform is the Alibaba Cloud receipt, you do not need to provide this. If not, we recommend that you first configure the default HarmonyOS channel receipt ID in the Alibaba Cloud EMAS Mobile Push console. For more information, see pushOptions.receiptId on the official HarmonyOS website.	RCPB***DFD5
ExtensionPush	boolean	Enables the HarmonyOS notification extension. Note You must first apply for permission on the official HarmonyOS website to send notification extension messages. For related content, see the HarmonyOS documentation on sending notification extension messages. This is supported starting from HarmonyOS SDK 1.2.0.	false
ExtensionExtraData	string	Extra data for the notification extension message. Note This is valid when sending a HarmonyOS notification extension message. It is conceptually equivalent to the extraData field of a HarmonyOS notification extension message. For a specific definition, see the HarmonyOS ExtensionPayload description. This is supported starting from HarmonyOS SDK 1.2.0.	text
BadgeSetNum	integer	The HarmonyOS application badge number setting. Note See the description of the setNum field for HarmonyOS badges. This is supported starting from HarmonyOS SDK 1.2.0.	1
BadgeAddNum	integer	The HarmonyOS application badge cumulative number. Note This is supported starting from HarmonyOS SDK 1.2.0. See the description of the addNum field for HarmonyOS badges.	1
LiveViewPayload	string	The JSON string of the HarmonyOS Live Window data structure LiveViewPayload. For developer integration, see the document HarmonyOS Live Window Push Guide.	{ "activityId": 1, "operation": 0, "event": "TAXI", "status": "DRIVER_ON_THE_WAY", "activityData": { "notificationData": { "type": 3 } } }
Sound	string	The HarmonyOS custom ringtone file name.	music.mp3
SoundDuration	integer	The duration of the custom message notification ringtone in seconds. The range is [1, 60]. If the ringtone duration is too short, it will loop.	2
Android	object	Android notification configuration
VendorChannelActivity	string	Specifies the Activity to open after the notification is clicked. Warning You must fill in this option when you use an Android vendor channel.	com.alibaba.cloudpushdemo.bizactivity
ChannelId	string	Sets the channelId for the Android app. It must correspond to the channelId in the vendor's app. Note Because the channel_id for OPPO's private message notification channel is the same as the app's channelId, the channel_id takes this value when pushing through the OPPO channel. For pushes through Huawei, FCM, and Alibaba Cloud's proprietary channels, the channel_id takes this value. For specific uses, see the FAQ: Notifications not received on Android 8.0 and later devices.	8.0up
RenderStyle	string	The notification style. Valid values are: `0`: Standard mode (default) `1`: Long text mode (supported by Huawei, Honor, Xiaomi, OPPO, Meizu, and proprietary channels) `2`: Large image mode (supported by proprietary channels) `3`: List mode (supported by Huawei, Honor, Xiaomi, OPPO, and proprietary channels)	0
PictureUrl	string	The image URL in large image mode. Currently supported by: proprietary channels with Android SDK 3.6.0 and later.	https://imag.example.com/image.png
ImageUrl	string	The URL for the icon on the right. Currently supported by: `Huawei EMUI` (only applicable in long text mode and Inbox mode). `Honor Magic UI` (only applicable in long text mode). `Proprietary channels` (Android SDK 3.5.0 and later).	https://imag.example.com/image.png
InboxContent	array	The body text in Inbox mode. The content is a valid JSON Array with no more than 5 elements. Currently supported by: Huawei: EMUI 9 and later Honor: Magic UI 4.0 and later Xiaomi: MIUI 10 and later OPPO: ColorOS 5.0 and later Proprietary channels: Android SDK 3.6.0 and later
	string	Body text	1. 第一条待处理事项
NotifyId	integer	The unique identifier for an Android notification bar message. It controls the overwriting and replacement behavior of notifications. A new notification with the same NotifyId automatically overwrites the old one.	233856727
GroupId	string	Message grouping. For messages in the same group, only the latest one and the total number of messages received in that group are displayed in the notification bar. Not all messages are displayed, and they cannot be expanded. Currently supported by: Huawei vendor channel Honor vendor channel Proprietary channels with Android SDK 3.9.1 and earlier Note This parameter is no longer supported by proprietary channels in Android SDK 3.9.2 and later versions.	group-1
ExtParameters	string	Custom extension properties for Android notifications. Note The parameter must be passed in a standard JSON Map format. An incorrect format causes parsing to fail.	{"key1":"value1"}
Music	string	The Huawei vendor channel notification sound. Specify the name of the audio file stored in the `app/src/main/res/raw/` directory of the client project, without the file format suffix. If not set, the default ringtone is used.	alicloud_notification_sound
BadgeSetNum	integer	Sets a fixed value for the badge number. The value range is [1, 99]. Note For vendor channel pushes, this is only effective for Huawei and Honor channels. When pushing through Alibaba Cloud's proprietary channel, this is only effective on Huawei, Honor, and vivo models.	4
BadgeAddNum	integer	Sets a cumulative value for the badge, which is added to the original badge number. Note This is supported by `Huawei` and `Honor` channels. If both `BadgeAddNum` and `BadgeSetNum` are present, the latter takes precedence.	1
BadgeActivity	string	The full class name of the application entry Activity for badge settings. Note This is only valid when pushing through the Huawei or Honor vendor channel.	com.alibaba.cloudpushdemo.bizactivity
TestMessage	boolean	Sets the vendor channel notification type: `false`: Formal notification (default). `true`: Test notification. Note Currently supported by: Huawei channel, Honor channel, vivo channel, and OPPO Fluid Cloud.	false
Options	object	Detailed channel configuration.
Accs	object	Alibaba Cloud proprietary configuration Note This is only valid when using Alibaba Cloud's proprietary channel.
CustomStyle	integer	The custom Android notification bar style. The value can be from 1 to 100. Note The client must complete the style preset configuration. For more information, see the Custom Notification Style API document.	1
Priority	integer	The priority of the Android notification's position in the notification bar. Valid values: -2, -1, 0, 1, 2.	0
ThreadId	string	Message grouping. Messages in the same group are displayed collapsed in the notification bar and can be expanded. Different groups of notifications are displayed separately. Note This is for Android SDK 3.9.2 and later.	order_ORD20231201001
OpenType	string	The action to take after the notification is clicked. Valid values: `APPLICATION`: Open the application (default). `ACTIVITY`: Open the specified page `OpenActivity`. `URL`: Open a URL. `NONE`: No action.	APPLICATION
OpenActivity	string	Sets the activity to open when the notification is clicked. This is valid when `OpenType` is `ACTIVITY`.	com.alibaba.cloudpushdemo.bizactivity
OpenUrl	string	After an Android device receives a push, clicking the notification opens the corresponding URL. This is valid when `OpenType` is `URL`.	www.example.com
NotifyType	string	The notification reminder method. Valid values: `VIBRATE`: Vibrate (default) `SOUND`: Sound `BOTH`: Sound and vibration `NONE`: Silent	NONE
Huawei	object	Huawei configuration
ReceiptId	string	The receipt ID for the Huawei channel. This ID can be found in the receipt parameter settings on the Huawei channel push operations platform. Note If the default receipt configuration on the Huawei channel push operations platform is the Alibaba Cloud receipt, you do not need to provide this. If not, we recommend that you first configure the default Huawei channel receipt ID in the Alibaba Cloud EMAS Mobile Push console.	RCP4C123456
Category	string	Function 1: After you apply for self-classification rights, this is used to identify the message type and determine the message reminder method. It speeds up the sending of specific types of messages. For valid values, see the message classification standards in the official Huawei Push documentation. Fill in the "Cloud notification category value" or "Local notification category value" from the document's table. Function 2: After applying for special permissions, this is used to identify high-priority pass-through scenarios. Valid values are: `VOIP`: Video call `PLAY_VOICE`: Voice playback Note For "Cloud notification category value" that is "Not applicable," all messages go through Alibaba Cloud's proprietary channel. For "Local notification category value" that is "Not applicable," all messages go through the Huawei channel.	VOIP
Urgency	string	The Huawei channel notification delivery priority. Valid values are: `HIGH` `NORMAL` You must apply for permission. For more information, see: Application link.	NORMAL
Importance	integer	Sets the importance parameter for Huawei notification message classification, which determines the notification behavior on the user's device. Valid values are: `0`: Marketing message `1`: Service and communication message Note We recommend using `Category` for notification classification. You must apply for this on the Huawei platform. Application link.	0
BusinessType	integer	Sets the Huawei quick notification parameters. 0: Send a normal Huawei notification (default). 1: Send a Huawei quick notification.	1
LiveNotificationPayload	string	The JSON string of the Huawei Android Live Window data structure LiveNotificationPayload. For developer integration, see the document Huawei Live Window Push Guide.	{ "activityId": 1, "operation": 1, "event": "TAXI", "activityData": { "notificationData": { "type": 3 } } }
Honor	object	Honor configuration
Importance	integer	Sets the importance parameter for Honor notification message classification, which determines the notification behavior on the user's device. Valid values are: `0`: Marketing message `1`: Service and communication message You must apply for this on the Honor platform. Application link.	0
Xiaomi	object	Xiaomi configuration
Channel	string	Sets the channelId for the Xiaomi notification type. You must apply for this on the Xiaomi platform. For more information, see: Application link. Note A single application can apply for a maximum of 8 channels on the Xiaomi channel. Plan accordingly.	michannel
FocusParam	string	The JSON string of the Xiaomi Super Island data structure miui.focus.param. For developer integration, see the document Xiaomi Super Island Push Guide.
FocusPics	string	The JSON string of the Xiaomi Super Island data image miui.focus.pic_xxx. For developer integration, see the document Xiaomi Super Island Push Guide.
Vivo	object	vivo configuration
Category	string	vivo classifies messages into two categories for management: system messages and operational messages. System messages: IM: Instant messages ACCOUNT: Account and asset TODO: To-do list DEVICE_REMINDER: Device information ORDER: Order and logistics SUBSCRIPTION: Subscription reminder Operational messages: NEWS: News CONTENT: Content recommendation MARKETING: Operational activity SOCIAL: Social dynamics For more information, see vivo classification description.	MARKETING
ReceiptId	string	The message receipt identifier for the vivo vendor push channel. It is used to receive push result callback notifications. Note Location: vivo Open Platform → Push Service → Application Information → Receipt Configuration Recommendation: First, configure the default receipt ID in the Alibaba Cloud EMAS console. Condition: This must be configured only if the default receipt on the vivo platform is not the Alibaba Cloud receipt.	1232221
Importance	integer	Sets the vivo notification message classification. Valid values are: `0`: Operational message (default) `1`: System message Note We recommend using `Category` for notification classification. You must apply for this on the vivo platform. For more information, see: Application link.	0
LiveMessage	string	The JSON string of the vivo Atomic Island data structure liveMessage. For developer integration, see the document vivo Atomic Island Push Guide.	{ "operation": 0, "scene": "HEALTH_REGISTER", "templateType": 1, "showNotify": true, "changeRecord": 999, "capsuleData": { "bgColor": "#32d4d4" } }
Oppo	object	OPPO configuration
Category	string	OPPO classifies messages into two categories for management: communication and services, and content and marketing. Communication and services (requires permission application): IM: Instant messages ACCOUNT: Account and asset TODO: To-do list DEVICE_REMINDER: Device information ORDER: Order and logistics SUBSCRIPTION: Subscription reminder Content and marketing: NEWS: News CONTENT: Content recommendation MARKETING: Operational activity SOCIAL: Social dynamics For more information, see vivo classification description.	NEWS
NotifyLevel	integer	The OPPO channel notification bar message reminder level. Valid values are: `1`: Notification bar `2`: Notification bar, lock screen, ringtone, vibration (default notification level for communication and service messages) `16`: Notification bar, lock screen, ringtone, vibration, banner (requires permission application) Note When you use the `NotifyLevel` parameter, you must also pass the `Category` parameter.	1
PrivateMsgTemplateId	string	The OPPO private message template ID.	687557242b1634hzefs3d5013
PrivateTitleParameters	string	The OPPO private message template title parameters.	{"name": "张三"}
PrivateContentParameters	string	The OPPO private message template content parameters.	{ "key1": "value1", "key2": "value2" }
IntelligentIntent	string	The JSON string of the OPPO Fluid Cloud's intent sharing data structure IntelligentIntent. For developer integration, see the document OPPO Fluid Cloud Push Guide.	{ "intentName": "Example.Progress", "identifier": "d71ebd3119877b12ecdb6c4fe96b068e", "timestamp": 1729485000989, "serviceId": { "launcher": "999800001", "fluidCloud": "999900001" }, "intentAction": { "actionStatus": 0 }, "intentEntity": { "entityName": "TAXI" } }
DeleteIntentData	string	The JSON string of the OPPO Fluid Cloud's intent deletion data structure data. This parameter is invalid if the AndroidOppoIntelligentIntent parameter is already filled. For developer integration, see the document OPPO Fluid Cloud Push Guide.	{ "intentName": "Example.Progress", "entityIds": [ "A580202509130712" ], "serviceId": { "launcher": "999800001", "fluidCloud": "999900001" } }
Meizu	object	Meizu configuration
NoticeMsgType	integer	The Meizu message type. 0 Public message (default) 1 Private message	0
Options	object	Push options
UseChannels	string	Specifies the sending channel. Valid values are: `accs`: Alibaba Cloud proprietary channel `huawei`: Huawei channel `honor`: Honor channel `xiaomi`: Xiaomi channel `oppo`: OPPO channel `vivo`: vivo channel `meizu`: Meizu channel `fcm`: Google Firebase channel (HTTP v1 API) `apns`: APNs channel `harmony`: HarmonyOS channel Note If this parameter is not configured, all channels can be used. If this parameter is configured, only the channels specified in the parameter are used. If the configured channel conflicts with the sending policy (for example, iOS notifications only go through the APNs channel, but this parameter does not include `apns`), the message is not sent.	accs,apns
PushTime	string	Specifies the sending time of the message, up to 7 days in the future. This is only valid when the `Action` parameter is `SCHEDULED_PUSH`. Note This uses the ISO 8601 standard and UTC time. The format is yyyy-MM-ddTHH:mm:ssZ.	2025-06-19T12:00:00Z
ExpireTime	string	Sets the expiration time of the message. After this time, the message will no longer be sent. The maximum retention period is 72 hours. Note This uses the ISO 8601 standard and UTC time. The format is YYYY-MM-DDThh:mm:ssZ. The expiration time must satisfy: ExpireTime > PushTime + 3 seconds (3 seconds is a buffer for network and system delays). Recommendation: The expiration time for a single push should be at least 1 minute. For a push to all or a batch push, it should be at least 10 minutes. Important For pass-through messages, if you do not set an expiration time, the message is only sent to online devices. If the device is offline, the message is discarded.	2025-06-21T12:00:00Z
JobKey	string	A custom identifier for the push task. If JobKey is not empty, this field will be included in the receipt log. To view receipt logs, see Receipt logs.	jobkey1727749697913
Trim	boolean	Specifies whether to automatically truncate oversized titles and content. Note This is only supported for vendor channels that have explicit limits on title and content length. It does not apply to channels like APNs, Huawei, and Honor, which do not limit title and content length but only the total request body size.	false
Sms	object	Resends the message as a text message. Note Currently, this is only supported for `Android` and `HarmonyOS` devices.
TemplateName	string	The SMS template name. You can get this from the SMS template management interface. It is the name assigned by the system, not the name set by the developer.	SMS_123456789
SignName	string	The SMS signature.	某某科技
Params	string	Key-value pairs for the variables in the SMS template.	key1=value1&key2=value2
DelaySecs	integer	The delay time to trigger the text message, in seconds. This must be set if you use SMS filter interaction. We recommend setting it to 15 seconds or more, with a maximum of 3 days, to avoid duplicate text messages and pushes. Note When you use SMS filter interaction, the ExpireTime parameter is invalid. The notification expiration time is calculated based on the DelaySecs parameter. The expiration time is the current time plus the DelaySecs time.	150
SendPolicy	string	The SMS sending policy.	PUSH_NOT_RECEIVED
MessageId	integer	A unique ID used to identify the message. This is only valid when the `Action` parameter is `CONTINUOUS_PUSH`.	1174754033128****

object

Push task object

Action

string

The push method. This is an optional parameter. The default value is PUSH_IMMEDIATELY (immediate push).

Important

The MassPushV2 batch push API supports only the following push methods:

PUSH_IMMEDIATELY (immediate push)
SCHEDULED_PUSH (scheduled push)

PUSH_IMMEDIATELY

Target

object

The target object for the message push. This parameter is optional when the Action operation type is CREATE_CONTINUOUS_PUSH (create a continuous push task).

Type

string

The push target type.

Important

The MassPushV2 batch push API and CONTINUOUS_PUSH continuous push support only the following three target types:

DEVICE
ACCOUNT
ALIAS

DEVICE

Value

string

Set the push target based on Target.Type. Separate multiple targets with commas. The target types and their values are described as follows:

Note

DEVICE: Device ID, such as deviceid1,deviceid2. You can specify up to 1,000 device IDs.
ACCOUNT: Account ID, such as account1,account2. You can specify up to 1,000 account IDs.
ALIAS: Alias, such as alias1,alias2. You can specify up to 1,000 aliases.
TAG: Supports one or more tags. For more information about the format, see Tag format specifications.
ALL: Push to all devices. You do not need to set a value. Pushing to all devices may increase costs. Use this feature with caution.

value

Platform

string

The platform type. This is an optional parameter.

IOS

Message

object

The pass-through message data sent to the device. The total length cannot exceed 4,000 bytes.

Note

Length calculation

The length is calculated based on the byte length of the UTF-8 encoded string after the Message object is serialized into JSON.
A Chinese character typically occupies 3 bytes in UTF-8 encoding.

Title

string

The title of the message to send.

title

Body

string

The content of the message to send.

{"key": "value"}

Notification

object

The vendor notification data sent to the device.

Important

If you set both Message and Notification, the device receives only one. The sending rules are as follows:

If the device is online, pass-through message data is sent.
If the device is offline, a system notification is sent.

Title

string

The title of the push notification.

Note

The length limits are as follows:

For iOS/HarmonyOS, the byte length cannot exceed 200.
For Android, the character length cannot exceed 50.

您有一条新消息

Body

string

The content of the push notification.

Note

The length limits are as follows:

For iOS, HarmonyOS, and Android, the character length cannot exceed 200.

尊敬的客户，您好！您的预约订单已取消成功。

Ios

object

iOS notification configuration

Subtitle

string

The subtitle of the iOS notification.

请查收订单。

Music

string

The iOS notification sound. Specify the name of the audio file stored in the app bundle or the sandbox Library/Sounds directory. For more information, see How to set the notification sound for iOS push.

Note

If you specify an empty string (""), the notification is silent.
If this parameter is not set, the default value is `default`, which is the system prompt sound.

default

Badge

integer

The iOS application badge.

1

BadgeAutoIncrement

boolean

Specifies whether to enable the badge auto-increment feature. This is an optional parameter. The default value is false.

Note

This parameter cannot be used with the badge setting parameter.
The badge auto-increment feature is maintained by the Alibaba Cloud push server, which counts the badges for each device. You must use SDK version 1.9.5 or later and actively sync the badge number to the server through the SDK.

false

Silent

boolean

Controls whether to enable silent push mode.

Note

When you send a silent notification, you can leave the title and body parameters empty.

false

Mutable

boolean

Enables extended notifications and controls whether iOS notifications support processing by the Notification Service Extension.

Note

This must be set to true when you send a silent notification.
The extension processing time cannot exceed 30 seconds.
A timeout causes the notification to display the original content.
You must add a Notification Service Extension to your application.

true

Category

string

Specifies the category identifier for an iOS notification. This defines the notification's interactive behavior and display style.

Note

The category must be pre-registered in the app to take effect.
Different categories can define different sets of actions.

MESSAGE_REPLY

CollapseId

string

A unique identifier that controls notification merging. Notifications with the same identifier are overwritten.

order_status_update_12345

ThreadId

string

The thread identifier for iOS notification grouping. It is used to classify and collapse related notifications.

Note

Notifications with the same thread-id are automatically grouped.
Multiple related notifications are collapsed into one notification group.
Users can expand the group to view all notifications within it.

news_category_tech

InterruptionLevel

string

The interruption level. This is an optional parameter. Valid values are:

passive: The system adds the notification to the notification list without lighting up the screen or playing a sound.
active: The system displays the notification immediately, lights up the screen, and can play a sound.
time-sensitive: The system presents the notification immediately, lights up the screen, and can play a sound, but does not override system notification controls.
critical: The system displays the notification immediately, lights up the screen, and plays a sound, bypassing the mute switch.

active

RelevanceScore

number

The relevance score of the notification message. It is used to control the priority and display policy of the notification.

0.5

ExtParameters

string

Custom extension properties for iOS notifications.

Note

The parameter must be passed in a standard JSON Map format. An incorrect format causes parsing to fail.

{"attachment": "https://xxxx.xxx/notification_pic.png"}

LiveActivity

object

Live Activities parameter object.

Important

Live Activities push only supports pushing to a single device of the DEVICE type.
When you push to Live Activities, you can leave the title and body parameters empty.

Id

string

The unique identifier for a Live Activity. It associates the activity instance on the device with the push target on the server.

Important

This ID must be the same as the forActivityId parameter of the registerLiveActivityPushToken method in the client SDK.
The server uses this ID to locate the specific activity instance during a push.

FOOD_DELIVERY_ORD20231201001

Event

string

Starts, updates, or ends a Live Activity.

start

AttributesType

string

The type of Live Activity to start.

Note

This is required when Event is `start`.

OrderActivityAttributes

Attributes

string

Static pass-through parameters for iOS Live Activities push. They are used to transmit immutable business identification information.

Note

This is required when Event is `start`.

{ "orderId": "ORD20231201001", "restaurantName": "美味餐厅", "customerAddress": "xx区xx路xx号", "orderType": "delivery" }

ContentState

string

Dynamic pass-through parameters for a Live Activity. They contain real-time updatable status information and changing data.

Note

Avoid overly frequent updates. An interval of 5 seconds or more is recommended.
Update multiple fields in a batch to reduce the number of pushes.
Consider the user experience and avoid screen flickering.
Must be a valid JSON string.

{ "status": "delivering", "estimatedTime": "10分钟", "progress": 80, "driverName": "李师傅", "currentStep": "配送员正在路上"} }

DismissalDate

integer

Sets the retention period for a finished Live Activity on the lock screen. This lets users view information after the activity has ended. It is a Unix timestamp in seconds.

1701439800

StaleDate

integer

Sets the expiration timestamp for the content of an iOS Live Activity. It is a Unix timestamp in seconds.

Note

After the specified time is reached, the system automatically marks the activity as expired.
Expired activities are removed from the Live Activity and the lock screen.
This prevents outdated information from occupying the user interface for a long time.

1701425400

ApnsEnv

string

iOS notifications are sent through the Apple Push Notification service (APNs) center. You must specify the environment information. This is an optional parameter. The default is the production environment.

DEV: Development environment, for applications installed and tested directly from Xcode.
PRODUCT: Production environment, for applications distributed through the App Store, TestFlight, Ad Hoc, and enterprise channels.

DEV

Hmos

object

HarmonyOS notification configuration.

Category

string

The notification message category. This is an optional parameter. The default category is MARKETING.

Note

After you apply for the right to self-classify notification messages, this parameter is used to identify the message type. Different notification message types affect how messages are displayed and how users are reminded. For more information, see Notification.category on the official HarmonyOS website.

IM

SlotType

string

Uses the specified type of notification channel.

Note

This is only valid for Alibaba Cloud's proprietary channels.
For more information, see SlotType on the official HarmonyOS website.

SOCIAL_COMMUNICATION

NotifyId

integer

Specifies the unique identifier (notifyId) for each message when it is displayed in the notification bar. If not provided, the push service automatically generates a unique identifier. Different notification messages can use the same notifyId to allow new messages to overwrite old ones. For more information, see Notification.notifyId on the official HarmonyOS website.

123456

Action

string

Specifies the action corresponding to the ability of an in-app page.

Note

For more information, see ClickAction.action on the official HarmonyOS website.

com.example.action

Uri

string

The URI corresponding to the ability of an in-app page.

Note

If there are multiple abilities, specify the action and URI for each ability separately. The system prioritizes using the action to find the corresponding in-app page.
For more information, see ClickAction.uri on the official HarmonyOS website.

https://www.example.com:8080/push/example

RenderStyle

string

The notification message style. This is an optional parameter. The default is a normal notification.

NORMAL

ImageUrl

string

The URL for the large icon on the right side of the notification. The URL must use the HTTPS protocol.

Note

Supported image formats are png, jpg, jpeg, heif, gif, and bmp. The image dimensions (length × width) must be less than 25,000 pixels.
For more information, see Notification.image on the official HarmonyOS website.

https://example.com/xxx.png

InboxContent

array

When RenderStyle is MULTI_LINE, you must fill in this field to define the content for the multi-line text style. It supports up to 3 lines of content.

string

Text.

1. 您有一个事项待处理

ExtParameters

string

Sets custom extension properties for the notification message. This is used to pass additional business data.

Note

The parameter must be passed in a standard JSON Map format. An incorrect format causes parsing to fail.

{"key": "value"}

TestMessage

boolean

Enables test messages.

Note

For more information, see the HarmonyOS push parameter TestMessage.

true

ReceiptId

string

The receipt ID for the HarmonyOS channel. This ID can be found in the receipt parameter settings on the HarmonyOS channel push operations platform.

Note

If the default receipt configuration on the HarmonyOS channel push operations platform is the Alibaba Cloud receipt, you do not need to provide this. If not, we recommend that you first configure the default HarmonyOS channel receipt ID in the Alibaba Cloud EMAS Mobile Push console.
For more information, see pushOptions.receiptId on the official HarmonyOS website.

RCPB***DFD5

ExtensionPush

boolean

Enables the HarmonyOS notification extension.

Note

You must first apply for permission on the official HarmonyOS website to send notification extension messages. For related content, see the HarmonyOS documentation on sending notification extension messages.
This is supported starting from HarmonyOS SDK 1.2.0.

false

ExtensionExtraData

string

Extra data for the notification extension message.

Note

This is valid when sending a HarmonyOS notification extension message.
It is conceptually equivalent to the extraData field of a HarmonyOS notification extension message. For a specific definition, see the HarmonyOS ExtensionPayload description.
This is supported starting from HarmonyOS SDK 1.2.0.

text

BadgeSetNum

integer

The HarmonyOS application badge number setting.

Note

See the description of the setNum field for HarmonyOS badges.
This is supported starting from HarmonyOS SDK 1.2.0.

1

BadgeAddNum

integer

The HarmonyOS application badge cumulative number.

Note

This is supported starting from HarmonyOS SDK 1.2.0.
See the description of the addNum field for HarmonyOS badges.

1

LiveViewPayload

string

The JSON string of the HarmonyOS Live Window data structure LiveViewPayload. For developer integration, see the document HarmonyOS Live Window Push Guide.

{ "activityId": 1, "operation": 0, "event": "TAXI", "status": "DRIVER_ON_THE_WAY", "activityData": { "notificationData": { "type": 3 } } }

Sound

string

The HarmonyOS custom ringtone file name.

music.mp3

SoundDuration

integer

The duration of the custom message notification ringtone in seconds. The range is [1, 60]. If the ringtone duration is too short, it will loop.

2

Android

object

Android notification configuration

VendorChannelActivity

string

Specifies the Activity to open after the notification is clicked.

Warning You must fill in this option when you use an Android vendor channel.

com.alibaba.cloudpushdemo.bizactivity

ChannelId

string

Sets the channelId for the Android app. It must correspond to the channelId in the vendor's app.

Note

Because the channel_id for OPPO's private message notification channel is the same as the app's channelId, the channel_id takes this value when pushing through the OPPO channel.
For pushes through Huawei, FCM, and Alibaba Cloud's proprietary channels, the channel_id takes this value.
For specific uses, see the FAQ: Notifications not received on Android 8.0 and later devices.

8.0up

RenderStyle

string

The notification style. Valid values are:

0: Standard mode (default)
1: Long text mode (supported by Huawei, Honor, Xiaomi, OPPO, Meizu, and proprietary channels)
2: Large image mode (supported by proprietary channels)
3: List mode (supported by Huawei, Honor, Xiaomi, OPPO, and proprietary channels)

0

PictureUrl

string

The image URL in large image mode. Currently supported by: proprietary channels with Android SDK 3.6.0 and later.

https://imag.example.com/image.png

ImageUrl

string

The URL for the icon on the right. Currently supported by:

Huawei EMUI (only applicable in long text mode and Inbox mode).
Honor Magic UI (only applicable in long text mode).
Proprietary channels (Android SDK 3.5.0 and later).

https://imag.example.com/image.png

InboxContent

array

The body text in Inbox mode. The content is a valid JSON Array with no more than 5 elements. Currently supported by:

Huawei: EMUI 9 and later
Honor: Magic UI 4.0 and later
Xiaomi: MIUI 10 and later
OPPO: ColorOS 5.0 and later
Proprietary channels: Android SDK 3.6.0 and later

string

Body text

1. 第一条待处理事项

NotifyId

integer

The unique identifier for an Android notification bar message. It controls the overwriting and replacement behavior of notifications. A new notification with the same NotifyId automatically overwrites the old one.

233856727

GroupId

string

Message grouping. For messages in the same group, only the latest one and the total number of messages received in that group are displayed in the notification bar. Not all messages are displayed, and they cannot be expanded. Currently supported by:

Huawei vendor channel
Honor vendor channel
Proprietary channels with Android SDK 3.9.1 and earlier

Note

This parameter is no longer supported by proprietary channels in Android SDK 3.9.2 and later versions.

group-1

ExtParameters

string

Custom extension properties for Android notifications.

Note

The parameter must be passed in a standard JSON Map format. An incorrect format causes parsing to fail.

{"key1":"value1"}

Music

string

The Huawei vendor channel notification sound. Specify the name of the audio file stored in the app/src/main/res/raw/ directory of the client project, without the file format suffix. If not set, the default ringtone is used.

alicloud_notification_sound

BadgeSetNum

integer

Sets a fixed value for the badge number. The value range is [1, 99].

Note

For vendor channel pushes, this is only effective for Huawei and Honor channels.
When pushing through Alibaba Cloud's proprietary channel, this is only effective on Huawei, Honor, and vivo models.

4

BadgeAddNum

integer

Sets a cumulative value for the badge, which is added to the original badge number.

Note

This is supported by Huawei and Honor channels.
If both BadgeAddNum and BadgeSetNum are present, the latter takes precedence.

1

BadgeActivity

string

The full class name of the application entry Activity for badge settings.

Note

This is only valid when pushing through the Huawei or Honor vendor channel.

com.alibaba.cloudpushdemo.bizactivity

TestMessage

boolean

Sets the vendor channel notification type:

false: Formal notification (default).
true: Test notification.

Note

Currently supported by: Huawei channel, Honor channel, vivo channel, and OPPO Fluid Cloud.

false

Options

object

Detailed channel configuration.

Accs

object

Alibaba Cloud proprietary configuration

Note

This is only valid when using Alibaba Cloud's proprietary channel.

CustomStyle

integer

The custom Android notification bar style. The value can be from 1 to 100.

Note

The client must complete the style preset configuration. For more information, see the Custom Notification Style API document.

1

Priority

integer

The priority of the Android notification's position in the notification bar. Valid values: -2, -1, 0, 1, 2.

0

ThreadId

string

Message grouping. Messages in the same group are displayed collapsed in the notification bar and can be expanded. Different groups of notifications are displayed separately.

Note

This is for Android SDK 3.9.2 and later.

order_ORD20231201001

OpenType

string

The action to take after the notification is clicked. Valid values:

APPLICATION: Open the application (default).
ACTIVITY: Open the specified page OpenActivity.
URL: Open a URL.
NONE: No action.

APPLICATION

OpenActivity

string

Sets the activity to open when the notification is clicked. This is valid when OpenType is ACTIVITY.

com.alibaba.cloudpushdemo.bizactivity

OpenUrl

string

After an Android device receives a push, clicking the notification opens the corresponding URL. This is valid when OpenType is URL.

www.example.com

NotifyType

string

The notification reminder method. Valid values:

VIBRATE: Vibrate (default)
SOUND: Sound
BOTH: Sound and vibration
NONE: Silent

NONE

Huawei

object

Huawei configuration

ReceiptId

string

The receipt ID for the Huawei channel. This ID can be found in the receipt parameter settings on the Huawei channel push operations platform.

Note

If the default receipt configuration on the Huawei channel push operations platform is the Alibaba Cloud receipt, you do not need to provide this. If not, we recommend that you first configure the default Huawei channel receipt ID in the Alibaba Cloud EMAS Mobile Push console.

RCP4C123456

Category

string

Function 1: After you apply for self-classification rights, this is used to identify the message type and determine the message reminder method. It speeds up the sending of specific types of messages. For valid values, see the message classification standards in the official Huawei Push documentation. Fill in the "Cloud notification category value" or "Local notification category value" from the document's table.

Function 2: After applying for special permissions, this is used to identify high-priority pass-through scenarios. Valid values are:

VOIP: Video call
PLAY_VOICE: Voice playback

Note

For "Cloud notification category value" that is "Not applicable," all messages go through Alibaba Cloud's proprietary channel.
For "Local notification category value" that is "Not applicable," all messages go through the Huawei channel.

VOIP

Urgency

string

The Huawei channel notification delivery priority. Valid values are:

HIGH
NORMAL

You must apply for permission. For more information, see: Application link.

NORMAL

Importance

integer

Sets the importance parameter for Huawei notification message classification, which determines the notification behavior on the user's device. Valid values are:

0: Marketing message
1: Service and communication message

Note

We recommend using Category for notification classification. You must apply for this on the Huawei platform. Application link.

0

BusinessType

integer

Sets the Huawei quick notification parameters.

0: Send a normal Huawei notification (default).
1: Send a Huawei quick notification.

1

LiveNotificationPayload

string

The JSON string of the Huawei Android Live Window data structure LiveNotificationPayload. For developer integration, see the document Huawei Live Window Push Guide.

{ "activityId": 1, "operation": 1, "event": "TAXI", "activityData": { "notificationData": { "type": 3 } } }

Honor

object

Honor configuration

Importance

integer

Sets the importance parameter for Honor notification message classification, which determines the notification behavior on the user's device. Valid values are:

0: Marketing message
1: Service and communication message

You must apply for this on the Honor platform. Application link.

0

Xiaomi

object

Xiaomi configuration

Channel

string

Sets the channelId for the Xiaomi notification type. You must apply for this on the Xiaomi platform. For more information, see: Application link.

Note

A single application can apply for a maximum of 8 channels on the Xiaomi channel. Plan accordingly.

michannel

FocusParam

string

The JSON string of the Xiaomi Super Island data structure miui.focus.param. For developer integration, see the document Xiaomi Super Island Push Guide.

FocusPics

string

The JSON string of the Xiaomi Super Island data image miui.focus.pic_xxx. For developer integration, see the document Xiaomi Super Island Push Guide.

Vivo

object

vivo configuration

Category

string

vivo classifies messages into two categories for management: system messages and operational messages.

System messages:

IM: Instant messages
ACCOUNT: Account and asset
TODO: To-do list
DEVICE_REMINDER: Device information
ORDER: Order and logistics
SUBSCRIPTION: Subscription reminder

Operational messages:

NEWS: News
CONTENT: Content recommendation
MARKETING: Operational activity
SOCIAL: Social dynamics

For more information, see vivo classification description.

MARKETING

ReceiptId

string

The message receipt identifier for the vivo vendor push channel. It is used to receive push result callback notifications.

Note

Location: vivo Open Platform → Push Service → Application Information → Receipt Configuration
Recommendation: First, configure the default receipt ID in the Alibaba Cloud EMAS console.
Condition: This must be configured only if the default receipt on the vivo platform is not the Alibaba Cloud receipt.

1232221

Importance

integer

Sets the vivo notification message classification. Valid values are:

0: Operational message (default)
1: System message

Note

We recommend using Category for notification classification. You must apply for this on the vivo platform. For more information, see: Application link.

0

LiveMessage

string

The JSON string of the vivo Atomic Island data structure liveMessage. For developer integration, see the document vivo Atomic Island Push Guide.

{ "operation": 0, "scene": "HEALTH_REGISTER", "templateType": 1, "showNotify": true, "changeRecord": 999, "capsuleData": { "bgColor": "#32d4d4" } }

Oppo

object

OPPO configuration

Category

string

OPPO classifies messages into two categories for management: communication and services, and content and marketing.

Communication and services (requires permission application):

IM: Instant messages
ACCOUNT: Account and asset
TODO: To-do list
DEVICE_REMINDER: Device information
ORDER: Order and logistics
SUBSCRIPTION: Subscription reminder

Content and marketing:

NEWS: News
CONTENT: Content recommendation
MARKETING: Operational activity
SOCIAL: Social dynamics

For more information, see vivo classification description.

NEWS

NotifyLevel

integer

The OPPO channel notification bar message reminder level. Valid values are:

1: Notification bar
2: Notification bar, lock screen, ringtone, vibration (default notification level for communication and service messages)
16: Notification bar, lock screen, ringtone, vibration, banner (requires permission application)

Note

When you use the NotifyLevel parameter, you must also pass the Category parameter.

1

PrivateMsgTemplateId

string

The OPPO private message template ID.

687557242b1634hzefs3d5013

PrivateTitleParameters

string

The OPPO private message template title parameters.

{"name": "张三"}

PrivateContentParameters

string

The OPPO private message template content parameters.

{ "key1": "value1", "key2": "value2" }

IntelligentIntent

string

The JSON string of the OPPO Fluid Cloud's intent sharing data structure IntelligentIntent. For developer integration, see the document OPPO Fluid Cloud Push Guide.

{ "intentName": "Example.Progress", "identifier": "d71ebd3119877b12ecdb6c4fe96b068e", "timestamp": 1729485000989, "serviceId": { "launcher": "999800001", "fluidCloud": "999900001" }, "intentAction": { "actionStatus": 0 }, "intentEntity": { "entityName": "TAXI" } }

DeleteIntentData

string

The JSON string of the OPPO Fluid Cloud's intent deletion data structure data. This parameter is invalid if the AndroidOppoIntelligentIntent parameter is already filled. For developer integration, see the document OPPO Fluid Cloud Push Guide.

{ "intentName": "Example.Progress", "entityIds": [ "A580202509130712" ], "serviceId": { "launcher": "999800001", "fluidCloud": "999900001" } }

Meizu

object

Meizu configuration

NoticeMsgType

integer

The Meizu message type.

0 Public message (default)
1 Private message

0

Options

object

Push options

UseChannels

string

Specifies the sending channel. Valid values are:

accs: Alibaba Cloud proprietary channel
huawei: Huawei channel
honor: Honor channel
xiaomi: Xiaomi channel
oppo: OPPO channel
vivo: vivo channel
meizu: Meizu channel
fcm: Google Firebase channel (HTTP v1 API)
apns: APNs channel
harmony: HarmonyOS channel

Note

If this parameter is not configured, all channels can be used.
If this parameter is configured, only the channels specified in the parameter are used.
If the configured channel conflicts with the sending policy (for example, iOS notifications only go through the APNs channel, but this parameter does not include `apns`), the message is not sent.

accs,apns

PushTime

string

Specifies the sending time of the message, up to 7 days in the future. This is only valid when the Action parameter is SCHEDULED_PUSH.

Note

This uses the ISO 8601 standard and UTC time. The format is yyyy-MM-ddTHH:mm:ssZ.

2025-06-19T12:00:00Z

ExpireTime

string

Sets the expiration time of the message. After this time, the message will no longer be sent. The maximum retention period is 72 hours.

Note

This uses the ISO 8601 standard and UTC time. The format is YYYY-MM-DDThh:mm:ssZ.
The expiration time must satisfy: ExpireTime > PushTime + 3 seconds (3 seconds is a buffer for network and system delays).
Recommendation: The expiration time for a single push should be at least 1 minute. For a push to all or a batch push, it should be at least 10 minutes.

Important For pass-through messages, if you do not set an expiration time, the message is only sent to online devices. If the device is offline, the message is discarded.

2025-06-21T12:00:00Z

JobKey

string

A custom identifier for the push task. If JobKey is not empty, this field will be included in the receipt log. To view receipt logs, see Receipt logs.

jobkey1727749697913

Trim

boolean

Specifies whether to automatically truncate oversized titles and content.

Note

This is only supported for vendor channels that have explicit limits on title and content length. It does not apply to channels like APNs, Huawei, and Honor, which do not limit title and content length but only the total request body size.

false

Sms

object

Resends the message as a text message.

Note

Currently, this is only supported for Android and HarmonyOS devices.

TemplateName

string

The SMS template name. You can get this from the SMS template management interface. It is the name assigned by the system, not the name set by the developer.

SMS_123456789

SignName

string

The SMS signature.

某某科技

Params

string

Key-value pairs for the variables in the SMS template.

key1=value1&key2=value2

DelaySecs

integer

The delay time to trigger the text message, in seconds.

This must be set if you use SMS filter interaction. We recommend setting it to 15 seconds or more, with a maximum of 3 days, to avoid duplicate text messages and pushes.

Note

When you use SMS filter interaction, the ExpireTime parameter is invalid. The notification expiration time is calculated based on the DelaySecs parameter. The expiration time is the current time plus the DelaySecs time.

150

SendPolicy

string

The SMS sending policy.

PUSH_NOT_RECEIVED

MessageId

integer

A unique ID used to identify the message. This is only valid when the Action parameter is CONTINUOUS_PUSH.

1174754033128****