Send One-to-One Template Message

Users within the app can send one-to-one template messages to others. Custom templates allow you to send different content to multiple users simultaneously. For instance, the app can notify users about their earned points.

Send to up to 1000 users at once.
Differentiate offline push notification content for each user via template fields. Define pushContent individually based on the toUserId list if needed.
By default, messages sent via this interface aren’t synced to the sender’s client or stored in their message history. Use the isIncludeSender parameter for synchronization.

How to Configure and Use Message Templates

Message templates use field content templates (with placeholders) and recipient-defined placeholders to send different content to multiple recipients at once.

Define Content Templates

When sending a message, pass field content with placeholders in content, pushContent, and pushData fields. For example:

"toUserId":["21","22","23"],
"content":"{\"content\":\"{c}{d}\",\"extra\":\"bb\"}",
"pushContent":["hello {c}","hello {c}","hello {c}"],

Here, {c} and {d} are custom placeholders.

Supported fields: content, pushContent, pushData.
The content field supports only one template, shared by all recipients.
The pushContent and pushData fields are arrays and must define templates individually for each user ID in toUserId. Even if no placeholders are used or all recipients receive the same content, define pushContent and pushData for each user ID in toUserId.

Specify Placeholder Values

Define placeholders in the values field based on the recipient list (toUserId), specifying personalized content for each recipient.

"values":[
    {
    "{c}":"Tom",
    "{d}":"：2"
    },
    {
    "{c}":"Jerry",
    "{d}":"：5"},
    {
    "{c}":"Rose",
    "{d}":"：10"}
    ],

In this example, each recipient receives the following message content:

User ID 21: Tom：2
User ID 22: Jerry：5
User ID 23: Rose：10

If offline, the push notification content (pushContent) received will also differ: Hello Tom, Hello Jerry, and Hello Rose.

tip

If {d} is defined in content, set its value in values; otherwise, {d} will be sent as text.

Request Method

POST: https://Data Center Domain/message/private/publish_template.json

Rate Limit: 6000 messages per minute. Sending to 1000 users counts as 1000 messages.

Signature Rule: All server API requests require rule verification. See API Request Signature for details.

Body Parameters

The HTTP request body data format is application/json, containing a JSON object with the following structure:

Parameter	Type	Required	Description
fromUserId	String	Yes	Sender user ID. Note: The user ID must have obtained a user token; otherwise, the sender’s information won’t display correctly in offline push notifications.
toUserId	String[]	Yes	Recipient user ID. Send to up to 1000 users.
objectName	String	Yes	Message type, accepting built-in or custom message types. Note: Custom message types must not start with "RC:" and must be ≤32 characters. The SDK must have registered the custom message type.
values	Array of objects	Yes	Provides values for placeholders in `content`, `pushContent`, and `pushData`.
content	String	Yes	Message content, max 128k per message. Built-in message types: Serialize the message content body JSON object into a JSON string and pass it in. See User Content Message Format for details. Custom message types: Customize the format, not limited to JSON.
pushContent	String[]	Yes	Specifies the notification content for offline push notifications. For built-in message types, this field overrides the default push content. For custom message types requiring offline push, this field must be filled; otherwise, no push notification will be sent. For custom message types not requiring offline push, pass an empty value to disable offline push.
pushData	String[]	No	APNs push data for iOS or `appData` for Android.
isIncludeSender	Int	No	Whether to sync the sent message to the sender client. `1` for sync, default `0`. Note: Additional services may be required for synchronization.
verifyBlacklist	Int	No	Whether to filter the sender’s blacklist. `0` for no filtering, `1` for filtering, default `0`.
isPersisted	Int	No	Whether to store this message in the cloud history message storage service for the recipient. `0` for no storage; `1` for storage. Default `1`.
contentAvailable	Int	No	iOS only. Enables silent push notifications. `1` for enable, `0` for disable, default `0`.
expansion	Boolean	No	Whether the message is expandable. Default `false`.
disablePush	Boolean	No	Whether the message is silent. Default `false`.
pushExt	Object	No	Configures push notifications, such as the title. Invalid if `disablePush` is `true`.
disableUpdateLastMsg	Boolean	No	Prevents updating the last message in the conversation. `false` updates; `true` doesn’t.

pushExt Parameter Details

pushExt supports setting push notification titles, content templates, forced notifications, and ChannelID. Escape pushExt JSON structures when required.

pushExt Parameter	Type	Required	Description
title	String	No	Notification title, max 50 characters. Defaults to user name for one-to-one chats and group name for group chats.
templateId	String	No	Push template ID. Matches template language content based on the user’s SDK language setting. Default content used if no match. Set template content in "Console - Custom Push Copy".
forceShowPushContent	Number	No	Forces display of notification content (`pushContent`) in push notifications, overriding client settings. `0` for no force, `1` for force.
pushConfigs	Array	No	Sets push properties by vendor. Supported channels: `MI` (Xiaomi), `HONOR` (Honor), `HW` (Huawei), `OPPO`, `VIVO`, `APNs`, `FCM`.
pushConfigs.HONOR.importance	String	No	Honor notification priority: `NORMAL` (service/communication), `LOW` (marketing).
pushConfigs.HONOR.image	String	No	Honor notification large icon URL. HTTPS required, max 512KB, recommended size 40dp x 40dp.
pushConfigs.HW.channelId	String	No	Huawei push notification channel ID.
pushConfigs.HW.importance	String	No	Huawei notification priority: `NORMAL` (default), `LOW`.
pushConfigs.HW.image	String	No	Huawei notification large icon URL. HTTPS required, max 512KB, recommended size 40dp x 40dp.
pushConfigs.MI.channelId	String	No	Xiaomi push notification channel ID.
pushConfigs.MI.large_icon_uri	String	No	Xiaomi notification large icon URL. Domestic MIUI12+ only, international supported. Image requirements: 120x120px, PNG or JPG.
pushConfigs.OPPO.channelId	String	No	OPPO push notification channel ID.
pushConfigs.OPPO.category	String	No	Push content category. See OPUSH Message Classification.
pushConfigs.OPPO.notify_level	Number	No	Notification reminder type: `1` (notification bar), `2` (notification bar + lock screen), `16` (notification bar + lock screen + banner + vibration + sound). Valid only if `category` is set. See OPUSH Message Classification.
pushConfigs.VIVO.classification	Number	No	VIVO push service message category: `0` (operational, default), `1` (system). Overrides the VIVO push channel type configured for the App Key in the console.
pushConfigs.VIVO.category	String	No	VIVO push service message sub-category, e.g., `IM` (instant message). Must match `classification`. Overrides the VIVO push category configured for the App Key in the console.
pushConfigs.APNs.thread-id	String	No	iOS notification group ID. Messages with the same `thread-id` are grouped, and groups with >5 messages are collapsed.
pushConfigs.APNs.apns-collapse-id	String	No	iOS only. Messages with the same ID are merged. iOS 10.0+ only.
pushConfigs.APNs.richMediaUri	String	No	iOS notification large icon URL. App must parse `richMediaUri` for display. iOS 10.0+ only.
pushConfigs.APNs.interruption-level	String	No	iOS 15+. Values: `passive`, `active` (default), `time-sensitive`, `critical`. Helps ensure important notifications (e.g., balance changes) are noticed despite "Scheduled Summary" or "Focus Mode".
pushConfigs.FCM.channelId	String	No	FCM push notification channel ID. The app must create a channel with this ID before receiving notifications with this ID.
pushConfigs.FCM.collapse_key	String	No	Android only. Identifier for a group of messages that can be collapsed, so only the last message is sent when delivery is resumed.
pushConfigs.FCM.imageUrl	String	No	Android notification large icon URL. Max 1MB. Requires FCM push configuration in the console to be Certificate and Notification Message.
pushConfigs.OHOS.category	String	No	HarmonyOS scenario-based push notification category, e.g., IM. After applying for Self-Classification Rights, identifies the notification message type, affecting display and reminder methods. See Request Parameter Description.
pushConfigs.OHOS.image	String	No	Notification large icon URL. HTTPS required. Supported formats: PNG, JPG, JPEG, BMP. Recommended size smaller than 128x128px; images larger than 49152px won’t display.

pushExt Structure Example

{
   "title":"you have a new message.",
   "templateId":"123456",
   "forceShowPushContent":0,
   "pushConfigs": [
       {
           "HW": {
             "channelId": "hw-123",
             "importance": "NORMAL",
             "image":"https://example.com/image.png"
           }
       },
       {
           "MI": {
             "channelId": "mi-123",
             "large_icon_uri":"https://example.com/image.png"
           }
       },
       {
           "OPPO": {
                "channelId": "oppo-123",
                "category": "IM",
                "notify_level": 2
             }
       },
       {
           "VIVO" : {"classification": "0"}
       },
       {
           "APNs": {
               "thread-id": "123",
               "apns-collapse-id":"123456",
               "richMediaUri":"https://example.com/image.png"
           }
       },
       {
           "FCM": {
            "channelId":"rongcloud_channelid",
            "collapse_key":"1234",
            "imageUrl":"https://example.com/image.png"
            }
       },
       {
           "OHOS": {
             "category": "IM",
             "image":"https://example.com/image.png"
           }
       }
   ]
}

Request Example

POST /message/private/publish_template.json HTTP/1.1
Host: api.rong-api.com
App-Key: uwd1c0sxdlx2
Timestamp: 1585127132438
Nonce: 14314
Signature: 45beb7cc7307889a8e711219a47b7cf6a5b000e8
Content-Type: application/json

{
  "fromUserId":"fromuser",
  "objectName":"RC:TxtMsg",
  "content":"{\"content\":\"{c}{d}{e}\",\"extra\":\"bb\"}",
  "toUserId":["21","22"],
  "values":[{"{c}":"1","{d}":"2","{e}":"3"},{"{c}":"4","{d}":"5","{e}":"6"}],
  "pushContent":["push{c}","push{c}"],
  "pushData":["pushdata","{c}{e}"],
  "verifyBlacklist":0,
  "disablePush":false,
  "expansion":false
}

In this example, user ID 21 receives "123", and user ID 22 receives "456".

tip

If {d} is defined in content, set its value in values; otherwise, {d} will be sent as text. Ensure toUserId, values, pushContent, and pushData counts match.

Response

The HTTP response body contains a JSON object with the following structure:

Return Value	Return Type	Description
code	Number	Return code, 200 for success.
messageUIDs	Array	Returns a list of messageUIDs
messageUIDs[i].userId	String	Recipient user ID, corresponding to the `toUserId` in the request
messageUIDs[i].messageUID	String	Unique ID of the message sent to the corresponding recipient

Response Example

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
    "code": 200,
    "messageUIDs": [
        {
            "userId": "2193",
            "messageUID": "XXXX-JJJJ-KKK-LLLL"
        },
        {
            "userId": "2192",
            "messageUID": "XXXX-JJJJ-KKK-LLKL"
        }
    ]
}

/ # Send One-on-One Template Messages

Users within an app can send one-on-one template messages to other users. By using custom templates, you can send different message content to multiple users at once. For example, an app can notify different users about the points they've earned.

Send to up to 1000 users in one go.
Differentiate offline push notification content for each user via template fields. If needed, define push content in pushContent for each user ID in toUserId.
Messages sent via this API won’t sync with the sender’s client or save in their chat history by default. Use the isIncludeSender parameter to enable syncing.

How to Configure and Use Message Templates

Message templates use field content templates (with placeholders) and recipient-specific placeholders to send different content to multiple recipients at once.

Define Content Templates

When sending messages, include placeholders in content, pushContent, and pushData fields, like this:

"toUserId":["21","22","23"],
"content":"{\"content\":\"{c}{d}\",\"extra\":\"bb\"}",
"pushContent":["hello {c}","hello {c}","hello {c}"],

Here, {c} and {d} are custom placeholders.

Supported fields for templates: content, pushContent, pushData.
The content field supports only one template, shared by all recipients.
The pushContent and pushData fields are arrays. Define templates for each user ID in toUserId, even if placeholders aren’t used or all recipients receive the same content.

Assign Values to Placeholders

Provide placeholder values in the values field for each recipient in toUserId.

"values":[
    {
    "{c}":"Tom",
    "{d}":"：2"
    },
    {
    "{c}":"Jerry",
    "{d}":"：5"},
    {
    "{c}":"Rose",
    "{d}":"：10"}
    ],

In this example, recipients receive the following messages:

User ID 21: Tom：2
User ID 22: Jerry：5
User ID 23: Rose：10

If recipients are offline, they’ll receive different push notifications: Hello Tom, Hello Jerry, Hello Rose.

tip

If {d} is defined in content, assign it a value in values. Otherwise, {d} will be sent as plain text.

Request Method

POST: https://Data Center Domain/message/private/publish_template.json

Rate Limit: 6000 messages per minute. Sending to 1000 users counts as 1000 messages.

Signature Rule: All server API requests require signature validation. See API Request Signature.

Body Parameters

The HTTP request body is in application/json format, containing a JSON object with the following structure:

Parameter	Type	Required	Description
fromUserId	String	Yes	Sender’s user ID. Note: The user ID must have obtained a user token; otherwise, offline push notifications won’t display sender info correctly.
toUserId	String[]	Yes	Recipient user IDs. Multiple IDs allow sending to multiple users, up to 1000.
objectName	String	Yes	Message type, accepting built-in types (see Message Type Overview) or custom message type values. Note: Custom message types cannot start with "RC:" to avoid conflicts with built-in types. The type name cannot exceed 32 characters. The SDK must have registered the custom message type; otherwise, it won’t parse the message.
values	Array of objects	Yes	Provides values for placeholders (e.g., `{d}`) in `content`, `pushContent`, and `pushData`.
content	String	Yes	Message content, max 128k per message. Built-in message types: Serialize the message body JSON object into a JSON string. See User Content Message Format or other built-in message type formats. For example, the text message body JSON structure includes a `content` field (key in the JSON structure). Serialize `{"content":"Hello world!"}` and use it as the `content` field value. Custom message types (`objectName` must specify a custom type): The parameter can use any format, not limited to JSON.
pushContent	String[]	Yes	Specifies the notification content for offline recipients. Note: For some message types, this field determines whether a remote push notification is triggered. Supports placeholders, replaced with values from `values`. If the message type (`objectName`) is predefined by the IM service, this field overrides the default push content. For custom message types requiring remote push notifications, this field must be filled; otherwise, offline recipients won’t receive notifications. For custom message types not requiring remote push notifications (e.g., app business layer commands), set this field to an empty array to disable offline pushes.
pushData	String[]	No	iOS platforms can retrieve APNs push data from the payload under the `appData` field (Hint: The `rc` field carries basic message info by default). Android platforms retrieve this data under the `appData` field.
isIncludeSender	Int	No	Whether to sync sent messages with the sender’s client. `1` enables syncing; default is `0`. Note: This parameter alone doesn’t guarantee the sender’s client will receive the message. Additional services may be required. See How to Sync Sent Messages to the Sender’s Client.
verifyBlacklist	Int	No	Whether to filter the sender’s blacklist. `0` disables filtering; `1` enables it. Default is `0`.
isPersisted	Int	No	Whether to store this message in the recipient’s cloud chat history. `0` disables storage; `1` enables it. Default is `1` (requires Cloud Chat History Service). This doesn’t affect offline messages, which are stored when users are offline. Tip: Generally (cases 1 and 2), client message storage doesn’t depend on this parameter. Case 3 is an exception: For built-in message types, the client SDK uses the type’s storage property to decide whether to store it locally. See Message Type Overview. For custom message types, the client SDK uses the storage property registered for that type. For unregistered custom message types (e.g., outdated app versions), the client SDK uses this parameter to decide whether to store the message locally. However, unregistered types can’t be parsed or displayed.
contentAvailable	Int	No	Valid only for iOS devices. A silent push for SDKs in the background, introduced in iOS7. Allows apps to execute code in the background immediately upon receiving the notification. See Knowledge Base Document. `1` enables it; `0` disables it. Default is `0`.
expansion	Boolean	No	Whether the message is expandable. Default is `false`. When `true`, the terminal can extend the message with additional info upon receipt.
disablePush	Boolean	No	Whether the message is silent. Default is `false`. When `true`, offline users won’t receive notification reminders.
pushExt	Object	No	Configures push notifications for the message, such as the notification title. Invalid when `disablePush` is `true`. See `pushExt` Parameter Description below.
disableUpdateLastMsg	Boolean	No	Disables updating the conversation’s last message. When `false`, the sent message appears in the conversation list; when `true`, it doesn’t update the list. Note: This parameter only affects messages stored on the client.

pushExt Parameter Description

The pushExt parameter supports setting the push notification title, push content template, whether to force notifications, and push ChannelID. Escape pushExt when making a JSON structure request.

pushExt Parameter	Type	Required	Description
title	String	No	Notification bar title, max 50 characters. Default: user name for one-on-one chats, group name for group chats.
templateId	String	No	Push template ID. Matches template content based on the recipient’s SDK language setting. Uses default content if no match.
forceShowPushContent	Number	No	Whether to bypass client settings and force display of notification content (`pushContent`). Default `0` disables forcing; `1` enables it. Note: Clients can be set to show only "You have a notification" reminders. Set `forceShowPushContent` to `1` to bypass this and force display of push content.
pushConfigs	Array	No	Set push properties by manufacturer. Supported push channels: `MI` (Xiaomi), `HONOR` (Honor), `HW` (Huawei), `OPPO`, `VIVO`, `APNs`, `FCM`.
pushConfigs.HONOR.importance	String	No	Honor notification bar message priority: NORMAL (service and communication messages) LOW (consulting and marketing messages). Images won’t display for marketing messages.
pushConfigs.HONOR.image	String	No	Honor push custom notification bar message large icon URL. If not set, the icon won’t display. URL must use HTTPS, e.g., `https://example.com/image.png`. Icon file must be under 512KB, recommended size: 40dp x 40dp, corner radius: 8dp. Larger icons may be compressed or not fully displayed.
pushConfigs.HW.channelId	String	No	Huawei push notification channel ID. See Huawei Custom Notification Channel. For more info, see Android Official Documentation.
pushConfigs.HW.importance	String	No	Huawei notification bar message priority: NORMAL (default, important info) LOW
pushConfigs.HW.image	String	No	Huawei push custom notification bar message large icon URL. If not set, the icon won’t display. URL must use HTTPS, e.g., `https://example.com/image.png`. Icon file must be under 512KB, recommended size: 40dp x 40dp, corner radius: 8dp. Larger icons may be compressed or not fully displayed.
pushConfigs.MI.channelId	String	No	Xiaomi push notification channel ID. See Xiaomi Push Message Classification Rules.
pushConfigs.MI.large_icon_uri	String	No	Xiaomi push custom notification bar message large icon URL. If not set, the icon won’t display. Domestic versions only support MIUI12 and above; international versions support all. Image requirements: 120 * 120px, png or jpg format.
pushConfigs.OPPO.channelId	String	No	OPPO push notification channel ID. See OPPO PUSH Channel Upgrade Guide.
pushConfigs.OPPO.category	String	No	Push content category. See OPUSH Message Classification Rules.
pushConfigs.OPPO.notify_level	Number	No	Notification reminder type: 1 (notification bar), 2 (notification bar + lock screen), 16 (notification bar + lock screen + banner + vibration + sound). Valid only if `category` is set. See OPUSH Message Classification Rules.
pushConfigs.VIVO.classification	Number	No	VIVO push service message category. Options: `0` (operational messages, default) and `1` (system messages). Corresponds to the `classification` field in VIVO push service. See VIVO Push Message Classification Guide. This field overrides the VIVO push channel type configured in the console for the App Key.
pushConfigs.VIVO.category	String	No	VIVO push service message subcategory, e.g., `IM` (instant messaging). Corresponds to the `category` field in VIVO push service. See VIVO Push Message Classification Guide. If `category` is specified, the `classification` field must also be set to match the subcategory. Ensure the subcategory (`category`) complies with VIVO’s requirements for system or operational messages. This field overrides the VIVO push category configured in the console for the App Key.
pushConfigs.APNs.thread-id	String	No	iOS notification bar group ID. Messages with the same `thread-id` are grouped. Groups with over 5 messages are collapsed.
pushConfigs.APNs.apns-collapse-id	String	No	For iOS platforms. Messages with the same ID are merged into one. Supported on iOS 10.0 and above.
pushConfigs.APNs.richMediaUri	String	No	For iOS platforms. Custom notification bar message large icon URL. Apps must parse `richMediaUri` and implement display. Supported on iOS 10.0 and above.
pushConfigs.APNs.interruption-level	String	No	For iOS 15 and above. Values: `passive`, `active` (default), `time-sensitive`, or `critical`. See APNs interruption-level. On iOS 15 and above, system features like "Scheduled Summary" and "Focus Mode" may delay important notifications (e.g., balance changes). Consider setting this field.
pushConfigs.FCM.channelId	String	No	FCM push notification channel ID. Apps must create a channel with this ID before receiving notifications. See Android Official Documentation.
pushConfigs.FCM.collapse_key	String	No	For Android platforms. Identifier for a group of messages that can be collapsed, so only the last message is sent when delivery resumes.
pushConfigs.FCM.imageUrl	String	No	For Android platforms. FCM push custom notification bar message large icon URL. If not set, the icon won’t display. Image size limit: 1MB. Requires FCM push configuration in the console to use certificate and notification message mode.
pushConfigs.OHOS.category	String	No	HarmonyOS scenario-based push notification message category, e.g., IM. After completing the Self-Classification Rights Application, this field identifies the notification message type, which affects how messages are displayed and reminded. See Request Parameter Description.
pushConfigs.OHOS.image	String	No	Notification large icon URL. URL must use HTTPS, e.g., `https://example.com/image.png`. Note: Supported image formats: png, jpg, jpeg, bmp. Recommended size: under 128*128 pixels. Images over 49152 pixels won’t display.

pushExt Structure Example

{
   "title":"you have a new message.",
   "templateId":"123456",
   "forceShowPushContent":0,
   "pushConfigs": [
       {
           "HW": {
             "channelId": "hw-123",
             "importance": "NORMAL",
             "image":"https://example.com/image.png"
           }
       },
       {
           "MI": {
             "channelId": "mi-123",
             "large_icon_uri":"https://example.com/image.png"
           }
       },
       {
           "OPPO": {
                "channelId": "oppo-123",
                "category": "IM",
                "notify_level": 2
             }
       },
       {
           "VIVO" : {"classification": "0"}
       },
       {
           "APNs": {
               "thread-id": "123",
               "apns-collapse-id":"123456",
               "richMediaUri":"https://example.com/image.png"
           }
       },
       {
           "FCM": {
            "channelId":"rongcloud_channelid",
            "collapse_key":"1234",
            "imageUrl":"https://example.com/image.png"
            }
       },
       {
           "OHOS": {
             "category": "IM",
             "image":"https://example.com/image.png"
           }
       }
   ]
}

Request Example

POST /message/private/publish_template.json HTTP/1.1
Host: api.rong-api.com
App-Key: uwd1c0sxdlx2
Timestamp: 1585127132438
Nonce: 14314
Signature: 45beb7cc7307889a8e711219a47b7cf6a5b000e8
Content-Type: application/json

{
  "fromUserId":"fromuser",
  "objectName":"RC:TxtMsg",
  "content":"{\"content\":\"{c}{d}{e}\",\"extra\":\"bb\"}",
  "toUserId":["21","22"],
  "values":[{"{c}":"1","{d}":"2","{e}":"3"},{"{c}":"4","{d}":"5","{e}":"6"}],
  "pushContent":["push{c}","push{c}"],
  "pushData":["pushdata","{c}{e}"],
  "verifyBlacklist":0,
  "disablePush":false,
  "expansion":false
}

In this example, user ID 21 receives "123", and user ID 22 receives "456".

tip

If {d} is defined in content, assign it a value in values. Otherwise, {d} will be sent as plain text. The number of toUserId, values, pushContent, and pushData must match.

Response

The HTTP response body contains a JSON object with the following structure:

Return Value	Return Type	Description
code	Number	Return code, 200 for success.
messageUIDs	Array	List of messageUIDs
messageUIDs[i].userId	String	Recipient user ID, corresponding to `toUserId` in the request
messageUIDs[i].messageUID	String	Unique ID of the message sent to the recipient

Response Example

HTTP/1.1 200 OK
Content-Type: application/json; charset=utf-8

{
    "code": 200,
    "messageUIDs": [
        {
            "userId": "2193",
            "messageUID": "XXXX-JJJJ-KKK-LLLL"
        },
        {
            "userId": "2192",
            "messageUID": "XXXX-JJJJ-KKK-LLKL"
        }
    ]
}

IMLib

Global Chat UIKit

push notification

IMLib

Global Chat UIKit

Chat Server

Chat Server SDK

How to Configure and Use Message Templates​

Define Content Templates​

Specify Placeholder Values​

Request Method​

Body Parameters​

Request Example​

Response​

Response Example​

How to Configure and Use Message Templates​

Define Content Templates​

Assign Values to Placeholders​

Request Method​

Body Parameters​

Request Example​

Response​

Response Example​

How to Configure and Use Message Templates

Define Content Templates

Specify Placeholder Values

Request Method

Body Parameters

Request Example

Response

Response Example

How to Configure and Use Message Templates

Define Content Templates

Assign Values to Placeholders

Request Method

Body Parameters

Request Example

Response

Response Example