# Release notes

2020/10/08

# Flex Message Update 2 has been released for the Messaging API

Added October 22, 2020

Flex message's play animated images feature has been temporarily disabled due to a technical issue. As of current, regardless of the value of the animated property in the image component, animated images cannot be played.

We sincerely apologize for any inconvenience this may have caused. We will notify you through this news article once the issue is fixed and the feature has been enabled again.

Flex Message Update 2 includes these improvements:

# Changed the maximum number of bubbles that can be included in a carousel

We changed the maximum number of bubbles that can be included as child elements of a carousel container. This table provides a side-by-side comparison of values before and after the change.

# Added more component alignment options

We added the justifyContent and alignItems properties to Flex Message box components. These properties let you specify how child elements and free space should be arranged; for example, you can choose to evenly distribute the child elements or keep them all centered.

flex-start flex-center flex-end space-between space-around space-evenly

For more information, see Arranging a box's child elements and free space in the Messaging API documentation.

# Allowed gradients to be used as a box's background image

You can use a linear gradient as the background image for a box component by setting its background.type property equal to linearGradient.

Linear gradient at 0 degrees Linear gradient at 45 degrees Linear gradient at 90 degrees

For more information, see Linear gradient backgrounds in the Messaging API documentation.

# Allowed an empty array to be specified as the value of a box's contents property

You can now specify an empty array as the value of a box component's contents property.

  • Box component

    Item Before After
    contents property Empty arrays can't be specified Empty arrays can be specified
    When would it be helpful to specify an empty array?

    When using box components for decoration like the four squares shown below, it used to be necessary to add filler components as child elements to each of the boxes. Starting with Flex Message Update 2, you only need to specify an empty array.

    offset property example 1

    Let's compare the JSON data for the yellow box component on the left before and after this change:

    • Before
    {
        "type": "box",
        "layout": "vertical",
        "contents": [
            {
            "type": "filler"
            }
        ],
        "width": "30px",
        "height": "30px",
        "backgroundColor": "#FFFF7F"
    }
    
    • After
    {
        "type": "box",
        "layout": "vertical",
        "contents": [],
        "width": "30px",
        "height": "30px",
        "backgroundColor": "#FFFF7F"
    }
    

# Added support for animated images

Added October 22, 2020

Flex message's play animated images feature has been temporarily disabled due to a technical issue. As of current, regardless of the value of the animated property in the image component, animated images cannot be played.

We sincerely apologize for any inconvenience this may have caused. We will notify you through this news article once the issue is fixed and the feature has been enabled again.

It is now possible to specify animated images (APNG) in the image component of Flex Message.

For more information, see the Image component in the Messaging API Reference.

# Changed how sizes are specified

We changed how you specify a component's size. This table provides a side-by-side comparison of values before and after the change.

# Allowed text to automatically shrink to fit a component's width

We added the adjustMode property to text and button components. If you specify a value of shrink-to-fit for this adjustMode property, the text's font size will automatically shrink to fit the width of the component.

Automatically shrink fonts to fit

For more information, see the Text and Button components in the Messaging API reference.

# Spacer has been discontinued

The spacer component, which was previously deprecated, has been discontinued. We recommend setting the padding of the box without using a spacer from now on.

For more information, see Box padding in the Messaging API documentation.

# Added support for Update 2 in the Flex Message Simulator

Flex Message Simulator now supports the new properties and objects introduced in Flex Message Update 2, as well.

Using Flex Message Simulator, you can easily generate JSON data for Flex Messages and visually examine how they're laid out.

Caveats

Flex Message Simulator doesn't make any guarantees about the layout of a Flex Message. A Flex Message's appearance may vary from one device to the next. In addition to the version of the LINE app being used, a device's operating system, resolution, language settings, and fonts may affect how messages are rendered.

2020/10/06

# [Updated] TLS 1.0 and TLS 1.1 support by the webhook notification source will be discontinued at the end of January 2021

Added on November 5, 2020

You can now also confirm communication from the environment after migration in verification method 2.

The following updates are planned for the LINE Platform, the source of webhook notifications for the Messaging API.

If you are using a webhook, please confirm communication from the new environment during the transition period.

What is a webhook?

A webhook is one of the features of LINE's Messaging API. It's a system in which the LINE Platform notifies the bot server of the provider (corporate or developer) of events such as adding friends and sending messages via HTTPS POST requests.

You can specify the bot server to which you want to be notified of webhooks by specifying the webhook URL in the LINE Developers Console. For more information on webhooks, see Receiving messages (webhooks) in the Messaging API documentation.

# Supported SSL/TLS protocol versions

We no longer support TLS 1.0 and TLS 1.1.

See the table below for the differences before and after the transition.

Protocol version Before transition After transition
TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3.0
SSL 2.0

# Supported HTTP versions

See the table below for differences before and after the transition.

HTTP version Before transition After transition
HTTP/2
HTTP/1.1
HTTP/1.0

# Supported root certification authorities

Webhook URLs (the bot server to which webhooks are notified) must be configured with an SSL/TLS certificate issued by a trusted certification authority. Self-signed certificates aren't allowed.

See the table below for differences before and after the transition.

Before transition After transition
Available SSL/TLS Certificates An SSL/TLS certificate issued by a "Certificate authority trusted by LINE" SSL/TLS certificates issued by a root certification authority that's widely trusted by most browsers

The "Certificate authority trusted by LINE" list will be removed at the end of the transition period.

# Transition period

October 6, 2020 - January 31, 2021 JST (GMT+9)

# Impact

If you're using Messaging API webhooks, we recommend that you use one of the following methods during the migration period to verify that the new LINE Platform can be used to communicate with the bot server.

# Verification method 1: Verify with an endpoint for webhook URL validation

Please verify the connection by using the endpoint for webhook URL test.

Return status code 200 for the communication request
  • The LINE Platform sends an HTTP POST request that doesn't include a webhook event to the webhook URL (bot server) to confirm communication. Design your bot server to return status code 200.

    Example HTTP POST request without a webhook event:

    {
        "destination": "xxxxxxxxxx",
        "events": []
    }
    

# Verification method 2: Use the webhook URL's "Verify" button in the LINE Developers Console

In the LINE Developers Console, click the Webhook URL's "Verify" button to perform the verification.

send target

LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

2020/10/06

# Messaging API update for October 2020

We added new endpoints to the Messaging API.

This is a summary of each new endpoint. For details, see each endpoint in the Messaging API reference.

# Get bot info

Gets basic information about the bot, such as:

  • Bot's user ID
  • Bot's basic ID
  • Bot's premium ID
  • Bot's display name
  • Profile image URL
  • Bot response mode ("Chat" or "Bot")
  • If the bot is set to automatically read messages

For more information, see Get bot info in the Messaging API reference.

# Get webhook endpoint information

Gets this information about the webhook endpoint:

  • Webhook URL
  • Webhook usage status (enabled or disabled)

For more information, see Get webhook endpoint information in the Messaging API reference.

# Set webhook endpoint URL

Sets the webhook endpoint URL. It may take up to 1 minute for changes to take place due to caching.

For more information, see Set webhook endpoint URL in the Messaging API reference.

# Test webhook endpoint

Checks if the configured webhook endpoint can receive a test webhook event.

For more information, see Test webhook endpoint in the Messaging API reference.

2020/09/15

# Redelivery object has been added to the criteria for narrowing down the narrowcast message target

Redelivery object has been added to the criteria for narrowing down the narrowcast message target in the Messaging API. Using the redelivery object, you can send a message conditioned on users who have previously received a narrowcast message.

# Redelivery object was added

Narrowcast messages are usually sent to all users who added a specific LINE Official Account as a friend. However, by specifying the demographic filter object when you send a narrowcast message, you can narrow down the target of your message based on certain conditions.

narrowcast message

To narrow down the target by a recipient object, in addition to the existing audience object, you can now specify the redelivery object.

By specifying the request ID in the redelivery object, you can send a message to users who have previously received a narrowcast message.

Conditions for specifying the request ID

The request ID specified in the requestId property must satisfy all of these conditions:

  • The request ID was issued by the delivering a narrowcast message
  • The narrowcast message was delivered within the past seven days
  • The delivery process is completed (The value of the phase property is succeeded in the response of the Get narrowcast message status endpoint)

For more information on redelivery object, see:

# Specify the target using the operator object (AND, OR, NOT)

Similar to existing audience objects, you can specify the target based on complex conditions using operators (AND, OR, NOT) with the redelivery object.

Below is an example of a recipient object with users with a specific chat tag and (AND) users who received a narrowcast message previously delivered set as the target:

send target

"recipient": {
    "type": "operator",
    "and": [
        {
            "type": "audience",
            "audienceGroupId": 5614991017776
        },
        {
            "type": "redelivery",
            "requestId": "5b59509c-c57b-11e9-aa8c-2a2ae2dbcce4"
        }
    ]
}

For more information about narrowing down the narrowcast message target, see these:

2020/09/01

# We've added new features to the Messaging API.

These are the features added in this update:

# Narrowcast messages can now be sent within the maximum number of messages that can be delivered

The limit.upToRemainingQuota property has been added to narrowcast messages.

By specifying this property when delivering a narrowcast message, you can send the message within the maximum number of messages that can be delivered.

What is the benefit of using the limit.upToRemainingQuota property?

If you try to send narrowcast messages that exceed the maximum number of messages that can be delivered, the delivery will fail.

For this reason, it was necessary to specify the maximum number of messages to send before sending narrowcast messages.

For example, if you can send up to 750 messages in a month, you'll send them with the limit.max property set to 750.

However, if you set the limit.upToRemainingQuota property to true, even if the number of messages to be sent exceeds the maximum number of messages that can be sent, the message won't fail and will automatically be sent within the limit.

The advantage of this property is that it automatically delivers within the maximum number of targets without having to check how many messages you can still send.

The distribution targets will be randomly selected.

For more information, see the limit.upToRemainingQuota property in the Send narrowcast message section of the Messaging API reference.

For more information on the maximum number of messages that can be delivered, see Messaging API pricing.

# The maximum size of JSON data that defines a bubble is 30 KB

The maximum size of JSON data that defines a bubble in Flex Messages has changed.

Subject Before change After change
Maximum size 10KB 30KB

For more information about Flex Message bubble containers, see Bubble in the Messaging API reference.

2020/08/26

# Certificate authority that can be used in the Webhook URL added

The webhook URL must use HTTPS and have an SSL certificate issued by a certificate authority trusted by LINE.

The following certificate authorities have been added to the list of certificate authorities trusted by LINE.

CN=TWCA Global Root CA, OU=Root CA, O=TAIWAN-CA, C=TW

For more information on configuring Webhook URL settings, see Webhook URL settings.

August 5, 2020

# The endpoint to get statistics is now available in Indonesia (ID)

Before, LINE Official Accounts created by Indonesian (ID) users weren't able to obtain this statistic.

This update has removed this restriction.

August 4, 2020

# We've added new webhook events and an API endpoint to the Messaging API

These are the features added in this update:

# Unsend event has been added

In addition to existing webhook events, such as join, leave, and send messages, a new "Unsend event" has been added, which indicates that the message has been cancelled.

# Video viewing complete event has been added

A new "Video viewing complete event" has been added. This event occurs when a user finishes watching a video with a trackingId property for video identification.

# The audiences property is now optional instead of required for a certain endpoint

The audiences property has been changed from required to optional for the following endpoint.

This spec change allows you to prepare an audience by creating an audience with no recipient specified first, and then adding user IDs or IFAs to the audience later.

# Recipients of an audience can be now specified by file

These endpoints will be available soon

These endpoints will be available soon. We will let you know in this release note when they become available.

You can now specify the recipients of an audience by file.

May 12, 2020

# Messaging API update

We made several improvements to the Messaging API.

# Message character limit and media file usage conditions have been changed

The character limit for text messages and the conditions for media files that can be used have changed.

See News for May 12, 2020 for a comparison of the previous and current situation.

# Emojis property has been added to the webhook event

LINE emoji information has been added to the webhook message event object. If the text containing a LINE emoji is sent by users, the emojis property will contain information about the used LINE emoji as a LINE emoji object.

For details, see the Text section in Messaging API reference.

# A request header has been added to safely retry the same request

You can safely retry the same request by adding a retry key (X-Line-Retry-Key) to the HTTP request header. No matter how many times the API request containing the same value of a retry key is executed, it is always accepted only once, preventing the same process from being duplicated.

For details, see Retrying a failed API request.

March 30, 2020

# New "message sticker" resource type added to sticker message webhook event

Following the release of Message Stickers (stickers with a customizable text), we have added PER_STICKER_TEXT to the stickerResourceType property of the webhook event that notifies you when a sticker message is sent.

If a LINE user sends a message sticker to your LINE Official Account, you will receive a webhook event object containing stickerResourceType of PER_STICKER_TEXT.

Learn more from the Sticker section of the Messaging API reference.

Jan 15, 2020

# New Messaging API endpoint for sending narrowcast messages

An endpoint for sending narrowcast messages has been added to the Messaging API.

This endpoint lets you send push messages to multiple users at any time.

You can specify the recipient using certain attributes (gender, age, OS type, region, etc.) and retargeting (audience).

For more information, see Send messages to multiple users using attribute information and retargeting.

Documentation available in Japanese only. English coming soon.

December 17, 2019

# mode property added to Messaging API Webhook events

We've added the mode property to all Messaging API webhook events.

The mode property is necessary for the channel multiplexing feature (under development). Now, all existing webhook events contain "mode": "active".

The mode property's value can change to standby if the channel administrator starts using channel multiplexing. The value of mode never automatically changes to standby.

Learn more about the mode property by reading about the Common properties of webhook events in the Messaging API reference.

December 6, 2019

# A stay event was added to beacon event

In the Messaging API beacon event, a stay event has been added to indicate that the user is staying in the covered area of the beacon.

If you wish to use the stay event, please contact us at LINE for Business (opens new window).

December 5, 2019

# New property added to "sticker message" webhook event

We added a new stickerResourceType property to the webhook event that notifies you when a sticker message is sent.

Use this property to see what type of sticker was sent (still image, animated sticker, sticker with sound, etc.).

Learn more from the Sticker section of the Messaging API reference.

November 8, 2019

# Notice of domain name change for certain endpoints

The domain name of certain Messaging API endpoints has been changed from api.line.me to api-data.line.me. There is no maintenance associated with this.

# Target endpoint

# Influence

If you are using the above endpoints, please change your domain during the transition period. We apologize for any inconvenience this may case. Thank you for your understanding.

Once the transition period ends, accessing an endpoint of the old domain will return a 404 status code.

# Transition period

Today - April 30, 2020

October 30, 2019

# Endpoint for obtaining user statistics now available in Thailand (TH)

Previously, the following Messaging API endpoint didn't allow LINE Official Accounts created in Thailand (TH) to get user activity statistics. Today, we've made it available.

This endpoint returns the same data as on the Insight tab in the LINE Official Account manager (opens new window).

October 16, 2019

# New Messaging API endpoint for friend statistics

We added a new Messaging API endpoint that returns information about how users interact with broadcast messages sent from your LINE Official Account.

This endpoint returns the same data as on the Insight tab in the LINE Official Account manager (opens new window).

August 30, 2019

# Flex Message Simulator Update 1 (beta) released

We released Flex Message Simulator Update 1 (β). This version contains sample Flex Messages with more sophisticated layouts based on the new features of Flex Message Update 1.

Limitations

We can't guarantee that the appearance of a Flex Message in Flex Message Simulator Update 1 (β) exactly matches the rendering on a target device. A single Flex Message may be rendered differently from device to device. Factors that affect rendering include OS, LINE version, screen resolution, language setting, and fonts.

Flex Message Simulator Update 1 (β)

Flex Message Update 1 examples

August 28, 2019

# Flex Message Update 1 released

We've added new Flex Message properties. As a result, you can use the rich expressive power of HTML and CSS in Flex Messages. For details, see Sending Flex Messages.

Flex Message example

July 8, 2019

# New Messaging API endpoints for friend statistics

We're happy to announce that we've added 3 new Messaging API endpoints that enable you to get detailed information about the friends of your LINE Official Account:

The data returned by these endpoints is the same data displayed on the Insight tab in the LINE Official Account Manager (opens new window).

April 18, 2019

# Enhanced Messaging API features

Bots associated with new or migrated LINE Official Accounts can now use the following features regardless of applied plans:

Bots associated with LINE@ accounts cannot use these features depending on applied plans.

For more information, see the Messaging API reference.

March 28, 2019

# You can configure the rich menu setting for multiple users at a time

We added endpoints for the following rich menu operations:

For more information on how to use the rich menu features, see the following pages.

January 17, 2019

# New endpoints added to Messaging API

We added new endpoints to the Messaging API. Use these endpoints to get the number of messages sent from your channel.

Learn more from these sections of the Messaging API reference:

December 18, 2018

# Specification change for the Messaging API

# The image and icon

Now you can specify any aspect ratio of images and icons within a certain range.

For more information, see the updated reference documentation below.

# URI action

Now you can set different action URLs for PC users (LINE for macOS and Windows) and smartphone users (LINE for iOS and Android).

For more information, see URI action.

November 15, 2018

# New webhook events are added for the Messaging API

We have added two webhook events: Member join event and member leave event.

For more information, see the following sections:

Specification change for the Messaging API

# You can play videos in imagemap messages

Now you can play videos in imagemap messages.

For more information, see Imagemap message.

# New properties are added to webhook events

  • The body of webhook events now include the user ID (destination) of a bot that should receive the webhook events. For more information, see Request body.
  • New information is available in message objects for image, video, and audio messages. For more information, see Image, Video, and Audio.

# Flex Messages can now be multicast

Now you can send Flex Messages with the /v2/bot/message/multicast endpoint.

For the /v2/bot/message/multicast endpoint, see Send multicast message in the Messaging API reference.

October 3, 2018

# The scheme of the picture URL returned when getting a user profile has been changed

Now we support https as the scheme of the pictureUrl property. The response to the GET https://api.line.me/v2/bot/profile/{userId} request includes this property.

September 19, 2018

# Default rich menu can now be configured with the Messaging API

Now you can configure the default rich menu with the Messaging API.

Both default rich menus created using LINE@ Manager (opens new window) and the Messaging API are supported and can be used at the same time.

For more information on how to use the rich menu features, see the following pages.

September 11, 2018

# More stickers are available for your bot

We have increased the number of sticker types available for bots from 342 to 462. You can create a smarter, more expressive bot with various new stickers.

For more information, see Sticker message and the sticker list.

August 6, 2018

# Flex Message is now viewable on your desktop

Flex Message is now viewable on your desktop.

The feature is supported on 5.9.0 for both LINE for macOS and LINE for Windows.

In addition, we have added the following new Flex Message properties so that you can create messages in a more flexible way.

  • action property of the box
  • maxLines property of the text

For more information, see the following pages.

July 31, 2018

# Quick reply released

We have released the quick reply feature for messages sent through the Messaging API. When a user receives a message that contains quick reply buttons, those buttons appear at the bottom of the chat screen. The user can simply tap one of the buttons to reply to your bot.

The quick reply feature is supported on 8.11.0 or later for both LINE for iOS and LINE for Android.

For more information, see Using quick replies.

June 12, 2018

# Flex Message released

We have released Flex Message, a new message type for the Messaging API. Flex Messages are messages with a customizable layout. You can customize the layout freely by combining multiple elements.

Flex Messages are only supported on 6.7.0 or later for both LINE for iOS and LINE for Android.

For more information, see Sending Flex Messages.

April 18, 2018

# The maximum number of rich menus has been increased

Now you can set up to 1000 rich menus for one bot with the Messaging API. The previous maximum number was was 10.

For more information about rich menus, see Using rich menus.

March 29, 2018

You will now be able to securely link the user account for your existing service with the LINE account of the user if they have friended your bot. This will allow you to utilize the user information you already have and use LINE bots to provide even better services.

For more information, see Linking user accounts.

February 22, 2018

# Property for accessibility released

Now you can specify text to be spoken using the label property for imagemap messages and rich menus when the accessibility feature is enabled on the client device. This feature is supported on LINE 8.2.0 or later for iOS.

For more information, see the updated reference documentation below.

February 8, 2018

# New properties for template messages and postback actions released

# Default actions can now be set for template messages

The defaultAction property has been added to the column object for buttons and carousel template messages. As a result, you can indicate a single action to be executed when a user taps anywhere in the image, title, or text area.

For more information, see the updated reference documentation below.

# displayText property for postback actions released

We have released the displayText property and have deprecated the text property for postback actions. We recommend using displayText instead of the text property. Note that the dislayText and text properties cannot both be used at the same time.

For more information, see the Postback action reference documentation.

November 31, 2017

# New options for template message images

We have released imageAspectRatio, imageSize, and imageBackgroundColor properties for Buttons and Carousel template messages. Using these properties, you can configure the aspect ratio, size, and background color for images used in template messages. For more information, see the reference documentation below.

November 8, 2017

# Specification change for rich menu resources

We've made changes to the response of the rich menu resources of the Messaging API listed below. When sending a request to delete or upload a rich menu or to link or unlink a rich menu for a user, the LINE Platform will now return a 200 status code and an empty JSON object on success instead of returning only a 200 status code.

See the updated API reference documentation below.

October 30, 2017

# Column objects for template messages increased

We've increased the number of column objects that you can include in your carousel and image carousel template messages from 5 to 10 objects.

For more information, see the updated reference documentation below.

October 23, 2017

# Rich menu features for Messaging API released

We've released rich menu features for the Messaging API which lets you display different rich menus to different users. By using the newly released rich menu endpoints, you can create, link, and manage your rich menus programmatically via the API instead of using LINE@ Manager (opens new window). The rich menu endpoints provide greater freedom in designing rich menus and the ability to set postback actions to specified areas.

In addition to the current rich menu size of 2500x1686 on LINE@ Manager, you can now create smaller rich menus that are 2500x843 with the Messaging API. This smaller rich menu size lets you display more of the chat screen while still providing an interactive menu for the user.

Both rich menus created using LINE@ Manager and the Messaging API are supported and can be used at the same time.

Note

These rich menu features are only supported on 7.14.0 or later for both LINE for Android and LINE for iOS.

For more information on how to use the new rich menu features, see the following pages.

September 1, 2017

# New template message features released

We have released the following features for the Messaging API.

The image carousel template lets you send multiple images in a single message that users can cycle through like a carousel. You can then set template actions for when an image is tapped.

For more information, see the image carousel reference.

# Datetime picker action

With the datetime picker template action, you can provide an easy way for users to pick a date and time without having to type it in manually. The datetime picker action can be used in any type of template message and returns a postback event when the action is tapped.

Note

The datetime picker action is supported on LINE 7.9.0 and later for iOS and 7.12.0 and later for Android.

For more information, see the datetime picker action reference.

July 27, 2017

# Get user IDs and profiles of group and room members

We’ve released resources for the Messaging API which lets you get the user IDs and LINE user profiles of the members of a group or room that your bot is in.

For more information on how to use these resources, see the API reference items below.

May 31, 2017

The user consent process and the data included in certain webhooks will change from LINE version 7.5.0 (iOS and Android). The details of the changes are shown below.

  1. Changes to the user consent process

    The way that users give consent to bots (LINE@ accounts and LINE Official Accounts) will change with the release of LINE version 7.5.0. Instead of requiring users to agree to a consent screen for every bot they want to add as a friend or start a chat with, from version 7.5.0, users will provide consent to all bots at once through a new consent screen (called the “Official Accounts Terms of Use”). After users have agreed to this screen once, they will be able to add other bots as friends and add them to chats in a single action.

    For more information on the user consent process, see User consent.

  2. Changes to the Messaging API specifications

    Webhooks will include the user ID of users who send messages in a group or a room if the user has agreed to the “Official Accounts Terms of Use”. Note that the user ID will not be included in the webhook if the user is using a version of LINE earlier than 7.5.0.

    For more information about the changes, see the updated API reference and JSON examples at source group and source room.

May 12, 2017

# Messaging API SDK for Node.js released

We have released the Messaging API SDK for Node.js. This makes it easier for you to to build a bot on LINE with Node.js using the Messaging API.

See the Messaging API SDK repository below:

For more information on how to use the Messaging API SDK for Node.js, see the documentation (opens new window).

January 23, 2017

# Multicast feature released

We've released the multicast feature which lets you send messages to multiple users at any time.

See the updated documentation in the API reference below.

We will continue to provide improvements so that developers can code more easily.