# News: Articles for #Messaging API

Channel access token v2.1 released

We released the latest version of the channel access token. This new version lets the user specify the expiration date and also provides security enhancements by switching to using a JSON Web Token (JWT) instead of the channel secret.

We recommend using the latest version of the channel access token.

Generate a JWT

You can use any JWT library or write your own code from scratch to Generate a JWT from your Assertion Signing Key. This is a necessary step in the Issue channel access token v2.1 API.

# New APIs

To learn the difference between the currently available channel access tokens, read Channel access tokens in the Messaging API documentation.

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.

For more information, see the Sticker section of the Messaging API reference.

LINE Beacon no longer supported on several LINE versions

As announced on March 10, 2020, LINE Beacon is no longer supported on the following LINE versions:

  • Japan: Any version before LINE 8.17.0
  • Taiwan: Any version before LINE 9.14.0
  • Thailand: Any version before LINE 9.8.0
  • Indonesia: Any version before LINE 9.8.0 (no change)

# Influence

Users that use these versions of LINE will not be detected when they enter or exit the reception area of a beacon.

  • Webhook beacon events are not sent to bot apps.
  • The beacon banner is not displayed for the corresponding user.

For more information about LINE Beacon, see Using Beacons.

We apologize for any inconvenience this may have caused. LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.

LINE URL scheme of 'line://' is deprecated

line:// is deprecated because it allows a takeover attack of the LINE URL scheme. Use https://line.me/R/ or https://liff.line.me/ instead.

A line:// takeover attack is an attack in which a user clicks on a URL following line://, a non-LINE app may start regardless of the intention of the LINE user. This attack is only established under certain conditions.

line:// may be discontinued in the future. If this is decided, an announcement will be made here.

For more information on LINE URL scheme, see "Using LINE features with the LINE URL scheme".

Reminder: Notice of domain name change for certain endpoints (Domain names must be updated by April 30, 2020)

As announced on November 8, 2019, the domain name of certain Messaging API endpoints has been changed from api.line.me to api-data.line.me.

# Target endpoint

# Influence

If you are using the above endpoints, please change your domain during the transition period.

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

We apologize for any inconvenience this may case. Thank you for your understanding.

# Transition period

November 8, 2019 - April 30, 2020

You can now change the icon and display name of your LINE Official Account

The push/reply API request extension of the Messaging API to change icon and display name of LINE Official Account is now generally available. This was previously an optional feature for corporate users.

As shown by a green frame, you can specify icon or display name when sending a message from LINE Official Account.

Change icon and display name

For more information, see Change icon and display name.

# Properties added to Messaging API

sender.iconUrl for specifying icon and sender.name for specifying display name have been added to Messaging API. The properties can be specified in all the message objects.

For more information about each property, see “Change icon and display name” section of the Messaging API reference documentation.

LINE Beacon no longer supported on several LINE versions from March 25, 2020

LINE Beacon will no longer be supported on the following LINE versions:

  • Japan: Any version before LINE 8.17.0
  • Taiwan: Any version before LINE 9.14.0
  • Thailand: Any version before LINE 9.8.0
  • Indonesia: Any version before LINE 9.8.0 (no change)

This change will take effect from March 25, 2020 to March 26, 2020.

# Influence

Users that use these versions of LINE will not be detected when they enter or exit the reception area of a beacon.

  • Webhook beacon events are not sent to bot apps.
  • The beacon banner is not displayed for the corresponding user.

For more information about LINE Beacon, see Using Beacons.

We apologize for any inconvenience this may have caused. LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.

All Narrowcast and Audience Management documentation now available in English

All documentation about sending narrowcast messages and managing audiences with Messaging API is now available in English.

Newly translated content:

Previously translated content (see news for February 19, 2020):

For previous announcements about the Narrowcast and Audience Management features, see these past news posts:

English documentation for Messaging API narrowcast features published

The documentation about sending narrowcast messages and managing audiences with Messaging API is now (partially) available in English:

Some content still remains in Japanese, but will be translated to English soon:

For the original announcements of the above Messaging API features, see these past news posts:

Audience sharing now available

You can now use audiences created with the Messaging API in LINE Official Account Manager and LINE Ads.

Audiences help with advanced advertisement targeting. By using audiences, you can send messages to users who have opened a previous message or clicked on a message URL.

Audiences created earlier now automatically appear in LINE Official Account Manager and LINE Ads. You don't need to change any settings.

For more information about audiences, see Using audiences in the Messaging API documentation (English version coming soon).

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.

[Updated] Make sure the provider name is correct

Added on January 9, 2020

This specification change was scheduled to take place on January 9, 2020, but has been postponed to January 16, 2020.

Starting January 16, 2020, LINE Official Accounts using the Messaging API will display the provider name registered by the developer at the bottom of the profile.

Corporate LINE Official Accounts may also have personal names registered as provider names. Make sure that the correct name is registered. The provider name can be changed from the LINE Developers Console.

Profile

*The provider name is displayed in the red frame

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.

Problem with channel statistics in console (resolved)

There was an issue with the Statistics tab for Messaging API channels on the LINE Developers console. Due to an inconsistency in how the system handled timezones, the tab appeared to show different data for certain days than the TSV file that you can generate by clicking Download as TSV.

This problem only affected users outside the JST timezone, and only affected the presentation of the data. No data was deleted or damaged. you'll be able to retrieve and display all data as normal.

# Issue time

Issue inception: November 26, 2019

Issue solved: December 18, 2019

The issue has now been resolved, so you may retrieve and display all data as normal. We apologize for any inconvenience this may have caused.

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.

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.

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

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.

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.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: October 4, 2019

Time:

9:00-9:02 JST (GMT+9)

10:04 JST (GMT+9)

11:00-11:08 JST (GMT+9)

12:02-12:08 JST (GMT+9)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

The API returned status code 500 for some requests.

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

Notice about system maintenance

We're performing system maintenance at the below time. We apologize for any inconvenience.

# Scheduled maintenance time

September 26, 2019 16:20-16:50 JST (+9 GMT)

The maintenance will only last a few seconds and will take place somewhere in this time window.

# Impact

Messaging API, LINE Login, and LIFF operations may result in errors. Specifically, the following events can occur:

  • Messaging API (https://api.line.me/v2/bot/*) returns an error with status code 500.
  • An error with status code 500 is returned when a user logs in with LINE Login or starts a LIFF app.

Try out Messaging API calls in your browser

We've added a Try button to these sections of the Messaging API reference documentation:

Clicking Try reveals a form that enables you to test the API call right then and there. You'll need to enter some required information, such as your channel access token (found in the console). Depending on the call, there are also other fields to fill in.

For now, this feature is only enabled for a small number of operations. We plan to increase the number in future releases to cover more Messaging API functionality.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: September 11, 2019 Time: 17:00–18:30 JST (GMT+9)

Date: September 12, 2019 Time: 13:00–13:30 JST (GMT+9)

# Cause

Server outage due to heavy load.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

The API returned status code 500 for some requests. Also, the "Send reply message" endpoint (https://api.line.me/v2/bot/message/reply) returned error codes in the 400 range, even for correct requests.

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

Flex Message Simulator Update 1 (β) 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

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

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.

We encountered problems during the planned migration of accounts from the deprecated Developer Trial plan to the new free plan, which started on June 11, 2019. The problems have now been resolved. We sincerely apologize for the inconvenience this caused.

# Date and time of outage

From: June 11, 2019
Until: June 18, 2019 14:33 JST(GMT+9)

# Cause

In Japan and Thailand, accounts that were migrated from the old Developer Trial plan to the new free plan incorrectly retained their old limit on number of friends (50).

# Details

When a user tried to befriend an account that had reached the limit of 50 friends, this error was displayed:

Sorry, the account you are trying to add cannot accept any more friends.

We have now removed the limit on the number of friends.

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

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 14, 2019 Time: 10:35–12:19 JST (GMT+9)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

The API returned status code 500 for some requests.

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

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: June 5, 2019 Time: 14:41–15:05 JST (GMT+9)

(Most errors were solved by 14:55.)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*) and webhook.

# Details

The API returned status code 403 or 500 error for some requests. Also, webhook events were not successfully sent.

We will continue to improve the quality of our services. Thank you for your understanding.

Changes associated with the integration of LINE@ accounts into LINE Official Accounts

With the consolidation of LINE@ account plans into LINE official plans, we changed the functionality of the LINE Developers console and the Messaging API as follows:

# Changes in the LINE Developers console

# Type of created accounts

When you create a Messaging API channel in the LINE Developers console, a LINE Official Account is created instead of a LINE@ account.

For more information, see Migration of LINE@ accounts. Existing LINE@ accounts will be migrated to LINE Official Accounts sequentially.

# Privacy policy and terms of use

Now you can set your own privacy policy and terms of use for your app in your LINE Login and Messaging API channels.

In the future, we will add links to your privacy policy and terms of use for your app in the user consent screen of LINE Login or your LINE Official Account.

# Enhanced Messaging API features

Bots associated with new or migrated LINE Official Accounts can 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.

Migrating your LINE@ account under the Developer Trial plan

We will consolidate the LINE@ account plans into the new LINE Official Account plans.

From April 18, 2019, when you create a Messaging API channel in the LINE Developers console, a LINE Official Account will be created instead of a LINE@ account.

After mid-June, 2019, we will migrate the existing LINE@ accounts under the Developer Trial plan to LINE Official Accounts. The free plan will be applied to the migrated LINE Official Accounts.

Learn more from Migration of LINE Developer Trial plan on the LINE Engineering Blog.

Messaging API: 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.

Notice about service outage for Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • Date: February 26, 2019
  • Time: Approximately 11:15-13:00 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when the following API endpoints were accessed:

  • Get content API: https://api.line.me/v2/bot/message/{messageId}/content
  • Rich menu API: https://api.line.me/v2/bot/richmenu/*

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • Date: February 20, 2019
  • Time: Approximately 18:45-19:02 and 19:10-19:26 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

The Messaging API experienced errors with error code 403 or 500 during the outage.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Console: We changed how to check the number of your bot's friends

We moved information related to the number of your bot's friends from the LINE Developers console to the official account management tools. We removed this information from the "Number of friends" tab on the "Statistics" tab of the Messaging API channels.

To view the number of your bot's friends, click the Account Manager Official Site button in the "Number of friends" tab. LINE Official Account Manager or LINE@ Manager will open according to your account plan.

To use the official account management tools, you need separate access permission. If you cannot access these tools, please contact the tool administrators of your organization.

We will remove the "Number of friends" tab from the LINE Developers console on March 26, 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:

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • Date: January 12, 2019
  • Time: 16:59-18:30 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

The Messaging API experienced errors with status code 5xx for approximately one minute around 17:00 on January 12, 2019. Also, webhook events were not successfully sent until 18:30 on the same day.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

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.

[Update] Change to the imagemap message

We decided not to make the specification change of the imagemap message that we announced on November 14, 2018, for compatibility. We apologize for any inconveniences caused and appreciate your understanding.

You can continue to send imagemap messages even if you set actions in the area that does not fit the width and height of the image specified by the baseSize property.

However, the layout of such imagemap messages might be broken on the user device. We recommend setting actions within the area that fits the width and height of the image specified by the baseSize property.

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:

Change to the imagemap message is scheduled

We'd like to inform you that we will change the specification of the imagemap message.

After the specification change, if the method of setting actions in imagemap messages is incorrect as below, an error occurs and you cannot send imagemap messages.

The current specification: You can send imagemap messages even if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

In this case, the layout of the imagemap displayed on the user device might be broken.

The new specification: You cannot send imagemap messages because the API request fails if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

This specification change will be released on November 27th.

Correction to documentation

There were errors in the description of the new destination property added to webhook events released yesterday. We correct it as below:

【Incorrect】The destination property includes the MID of a bot that should reeive the webhook events. The property value is a string that matches the regular expression, "u[0-9a-f]{32}".

【Correct】The destination property includes the user ID of a bot that should reeive the webhook events. The property value is a string that matches the regular expression, "U[0-9a-f]{32}".

For more information, see Request body.

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.

Note that this change doesn't include the validation of action areas of imagemap messages announced on October 24. We will inform you once we decide on our schedule.

# New properties are added to webhook events

  • The body of webhook events now includes 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.

Correction on November 9, 2018 : MID -> user ID

# 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.

Change to the imagemap message is scheduled

We'd like to inform you that we will change the specification of the imagemap message.

After the specification change, if the method of setting actions in imagemap messages is incorrect as below, an error occurs and you cannot send imagemap messages.

The current specification: You can send imagemap messages even if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

In this case, the layout of the imagemap displayed on the user device might be broken.

The new specification: You cannot send imagemap messages because the API request fails if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

This specification change will be released in the week starting November 5th.

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.

[Update] Discontinuation of the long-lived channel access token

We'd like to inform you of the change in the discontinuation of the long-lived channel access token that we announced in August.

We have concluded that discontinuing the long-lived channel access token by November can cause difficulty to many developers. Therefore, we will continue to support the long-lived channel access token and find alternative ways in the future that will not affect our developers.

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 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.

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.

Long-term channel access token to be discontinued

We'd like to inform you that we will discontinue the long-lived channel access token used with the Messaging API.

The discontinuation is scheduled in November 2018 with the removal of the endpoints of the Messaging API v1.

Note that the long-lived channel access token is issued only from the console. The following endpoint to issue a short-lived channel access token will not be affected.

https://api.line.me/v2/oauth/accessToken

We will provide further details for a replacement method soon.

Flex Message is now available on your desktop

Flex Message is now available on your desktop.

The feature is supported on LINE 5.9.0 for macOS and 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:

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.

Quick reply sample

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

For more information, see Using quick replies.

An important message for our users in Thailand, Taiwan, and Indonesia

Important notice concerning LINE Official Accounts, LINE@ accounts, Business Connect accounts, and Customer Connect accounts The following message applies to our users in Thailand, Taiwan, and Indonesia. LINE Corporation will be collecting information from LINE Official Accounts, LINE@ accounts, Business Connect accounts, and Customer Connect accounts (OAs) in order to improve our services. You must agree to these terms by September 2, 2018.

Log in to LINE@ Manager

With these revised terms, we will work on improving services requested by OA users, such as visualization of delivery performance through message views, click counts, video views, etc. and targeting delivery based on user response logs to messages.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date of recovery

Date: June 27, 2018 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

When the Messaging API was called to unlink a rich menu from a user that was not in a chat with the bot, the rich menu was not unlinked from the user. This issue occured only to users with LINE 8.7.0 or later for iOS and rich menus configured at admin-official.line.me.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

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 Message samples

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

For more information, see Sending Flex Messages.

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.

Account link feature released

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. We will let you know when English documents become available.

LINE Bot Designer released

LINE Bot Designer lets you prototype LINE bots faster and easier without any programming knowledge. You can freely design chatbots in a desired scenario.

LINE Bot Designer free for use. Download it now. Anyone with a LINE account can use it.

For more information, see the LINE Bot Designer page.

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 and later for iOS.

For more information, see the updated reference documentation below.

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.

Community SDK section released

We have released a community SDK section to our Messaging API SDKs page with Messaging API SDKs developed by our developer community. We currently have a C# (.NET) SDK and are looking to add more resources.

If you have developed a SDK or library for the Messaging API, see our Community contribution guidelines for information on how to submit your project to us for review.

New article on sharing bots

We've added a new article on how you can gain more friends and expand the reach of your bot. For example, you can use a QR code, add an "Add friend" button, or link your bot with a LINE Login channel.

Check out the article at Sharing your bot with users.

New options for template message images

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

LINE URL scheme information released

We've added an article about the LINE URL scheme to our LINE Login and Messaging API documentation. You can use the URL schemes to help your users navigate to specific content such as the camera, location, or settings screens in LINE. The LINE URL scheme can be used in your bot (Messaging API) from within LINE or in your native or web apps to automatically open LINE.

See the new articles below.

Link your bot to your LINE Login channel

We've added an option to display a prompt to let you display an option for users to add your bot as a friend when logging in to your app with LINE Login. To do this, first, link a bot to your LINE Login account from the new "Bot linked to this channel" item in the LINE Developers console, then include the bot_prompt query parameter in the authorization URL for LINE Login.

For more information on this feature, see Linking a bot with your LINE Login channel.

In addition, we've released a new resource for the Social API which lets you get the friendship status between your bot and a user. Send a GET request to https://api.line.me/friendship/v1/status to see if the user has added your bot as a friend or not.

To see the API reference for this resource, go to Get friendship status.

Note: This feature is not currently available to enterprise users. If you are an enterprise user and would like to use this feature, please contact your LINE representative.

LINE Login and Messaging API glossaries

To help you better understand the terms and concepts used in our documentation, we've added glossaries for both LINE Login and Messaging API.

Check them out using the links below.

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.

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.

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. 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 LINE 7.14.0 and later for Android and iOS.

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

Changes to the user consent process and data retrieved in webhooks

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 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 below 7.5.0.

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.

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.

Messaging API released and LINE Developers documentation updated

We've made some updates to the LINE Developers website. We've added new documentation together with the release of the Messaging API. Our API reference documentation has also been updated and redesigned. And we've made a couple of branding changes as well.

For more detailed information about the changes, see below:

  • Added "Overview", "Getting started", and API reference documentation for the Messaging API. For more information, see Messaging API.
  • Changed the look of the API reference documentation. See the new documentation here: API reference.
  • Made the following branding changes:
    • Web API includes the APIs used for integrating Web Login with your websites.
    • Social REST API includes REST APIs that you can call from your applications.
    • LINE Login, LINE SDK for Android, LINE SDK for iOS, Web API, and Social REST API are included in Social API
  • Added information on LINE Official Accounts and LINE@ accounts in "Account types".

Sending rich messages section updated

The "Sending rich messages" section of the LINE Developers site has been updated to include information about the "sendMessage" feature of rich messages.

For more information, go to https://developers.line.me/bot-api/api-reference.

Useful links have been added for BOT API Trial

We have added useful links to accelerate your development on BOT API Trial.

See all the links added from below.

Messaging API links

List of stickers updated

Sticker images have been added to the sticker list which will allow developers to easily recognize the sticker ID.

Method for calling APIs for BOT API Trial changed

You are no longer required to register the IP address of your server to call APIs for BOT API Trial. If you register an IP address on the whitelist, API calls will be limited to that IP address. You can use the whitelist for security purposes.

Let's Encrypt and StartSSL CA has been added

SSL CA root certificates for Let's Encrypt and StartSSL have been added for BOT API callback URL.

See the "Note" in the Registering a callback URL section to find a link to the full list of authorized CAs.