The Channels API supports many of the features of Line; however, due to the omni-channel nature of the API, there may be some differences between the Channels API message and the native Line API.To send a Line message, you must have an active Line channel and perform an HTTP request to the following endpoint with a valid access key
When sending outbound messages as well as setting the receiver information you must set message body field in all cases
You can send messages to users who have added your LINE Official Account as a friend or in group chats and multi-person chats that your LINE Official Account has joined. Additionally, you can send messages to users who have sent a message to your LINE Official Account within the past seven days.
The Channels API supports many of the features of Line; however, due to the omni-channel nature of the API, there may be some differences between the Channels API message and the native Line API. Here is an overview of the Line message types and Channels API message types:
To include an emoji in a text message, specify the product ID and emoji ID within the text message object. Set the index, productId, and emojiId properties, as shown in the example below. These properties can be found in text.metadata.line.emoji.items. Refer to the official documentation for detailed LINE emoji definitions.
You can send any outbound message as a reply to a previous message by setting the replyTo object as shown below. The replyTo.id should be set to the id of a received message and the replyTo.type should be set to "message".
A reference to the message. This can be used to identify the message in the channel.
Example: my-own-identifier
templateobject | nullable
metaobject
replyToobject
bodyMessageBody
notificationChannelNotification
capFrequencyboolean
If set to true, the frequency capping settings of the platform will be used
to either allow or reject the message to a contact. Can only be set to true
if the message is sent to a contact and .meta.extraInformation.useCase is marketing.
enableLinkTrackingboolean
If set to true and message is a test/campaign message, web tracking parameters will be appended to the links in the message.
ignoreQuietHoursboolean
If set to true, quiet hours settings will be ignored and the message will be sent as soon as possible.
ignoreGlobalHoldoutboolean
Do not check if the recipient is part of global holdout. To be used to send transactional messages.
tagsstring · min: 1 · max: 50[]
Tags to associate with the message. Tags are converted to lower case and tags
that do not exist are automatically created. You can view your created tags
in the UI. You can specify up to 10 tags per message.
shortLinksobject | nullable
SMS link shortening options. When using templates, please refer to
the template level shortLinks instead.
scheduledForstring · date-time
Scheduled time to send message at. Must be formated as RFC3339 timestamp. When
set, the message status will be scheduled until it's sent. Messages scheduled
for a time in the past or within 10 minutes of the request may be sent
immediately. Messages scheduled farther than 35 days will be rejected.
validityinteger
Validity determines for how many seconds a message is valid. If none is provided, the channel message type will be used to determine it.
A promotional, conversational or transactional channel message is valid for 36 hours (129600 seconds). A message sent from a 2FA channel is valid for 10 minutes (600 seconds).
