LIFF v2.18.1 released
2021/12/21

We've released LIFF v2.18.1.

In LIFF v2.18.1, the following bugs have been fixed.

# Fixed a bug in TypeScript that caused an error when building

We've fixed a bug in LIFF v2.18.0, where using TypeScript to build codes containing URI action in Message objects caused an error.

# Target methods

# How to update to LIFF v2.18.1

If you're using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), you will automatically be updated to v2.18.1.

If you're using an npm package, you can update to v2.18.1 by executing either npm install @line/liff@2.18.1 or yarn add @line/liff@2.18.1.

For more information on integrating the LIFF SDK, see Integrating the LIFF SDK with the LIFF app.

LIFF LINE MINI App
[Resolved] Notice about service outage of the LINE Platform
2021/12/20

We'd like to inform you about a service outage regarding the LINE Platform. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  1. December 19, 2021 around 18:00 - 18:46 (UTC+9)
  2. December 19, 2021 around 21:20 - 22:26 (UTC+9)

# Cause of the outage

Server failure

# Impact

  • Messaging API
  • LINE Login
  • LIFF/LINE MINI App

# Details

In some LINE Official Accounts, adding and unblocking friends using the bot link feature didn't work properly.

Also, some requests for getting friendship status with the LINE Official Account weren't being processed properly and caused errors with status code 5xx.

These are the main impacts per product:

# Messaging API

  • Some requests weren't processed properly, resulting in errors with status code 5xx.

# LINE Login

# LIFF/LINE MINI App


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

Outage Report LINE Platform Messaging API LINE Login LIFF LINE MINI App
LIFF v2.18.0 released
2021/12/09

We've released LIFF v2.18.0.

In LIFF v2.18.0, the following feature has been added.

We've added the liff.permanentLink.createUrlBy() method, through which you can get permanent link of any page in the LIFF app.

With the liff.permanentLink.createUrl() method, you can only get the permanent link of the current page. But with the liff.permanentLink.createUrlBy() method, you can get the permanent link of any page in the LIFF app, in addition to the current page.

In addition, with the liff.permanentLink.createUrl() method, in order to get a permanent link with a query parameter added, you need to have executed the liff.permanentLink.setExtraQueryParam() method in advance. But with the liff.permanentLink.createUrlBy() method, you can specify the query parameter you want to add at the same time that you execute the method. Also, the liff.permanentLink.createUrlBy() method isn't affected by the liff.permanentLink.setExtraQueryParam() method.

liff.permanentLink.createUrl() liff.permanentLink.createUrlBy()
The LIFF app page that the permanent link can be obtained The current page Any page
How to add any query parameter to a permanent link Execute the liff.permanentLink.setExtraQueryParam() method in advance Specify when you execute the liff.permanentLink.createUrlBy() method
Return value String Promise object
// For example, if the endpoint URL of the LIFF app is https://example.com/path1?q1=v1
// and its LIFF ID is 1234567890-AbcdEfgh
liff.permanentLink
  .createUrlBy('https://example.com/path1?q1=v1')
  .then((permanentLink) => {
    // https://liff.line.me/1234567890-AbcdEfgh
    console.log(permanentLink);
  });

liff.permanentLink
  .createUrlBy('https://example.com/path1/path2?q1=v1&q2=v2')
  .then((permanentLink) => {
    // https://liff.line.me/1234567890-AbcdEfgh/path2?q=2=v2
    console.log(permanentLink);
  });
The liff.permanentLink.createUrl() method may be deprecated in the next major version update

Due to technical issues, the liff.permanentLink.createUrl() method may be deprecated in the next major version update. To get the permanent link of the current page, we recommend using liff.permanentLink.createUrlBy() method.

For more information, see liff.permanentLink.createUrlBy() in the LIFF API reference.

LIFF LINE MINI App
Flex Message Simulator usage limited to accounts on the LINE Developers Console
2021/12/07

The Flex Message Simulator will be available for use only by developer accounts created on the LINE Developers Console.

The Flex Message Simulator had previously been available on LINE Business ID (via LINE Accounts or Business Accounts) as well. However, going forward, usage of the feature will be limited to developer accounts created on the LINE Developers Console.

We've come to this decision because new features, such as the recently added Sending test messages from Flex Message Simulator feature, are developed with specifications that are linked to LINE's developer products, requiring a developer account on the LINE Developers Console.

The requirements will differ based on login status, so check the following:

# If you've logged in to the LINE Developers before

If you're using the same account to log in to the Flex Message Simulator and the LINE Developers Console, your developer account will have been created when you first logged in to the LINE Developers Console.

Therefore, you can use the Flex Message Simulator per usual, even after the date of the change.

# If you've never logged in to the LINE Developers

If you've never logged into the LINE Developers Console before and access the Flex Message Simulator after the date of change, you will be redirected to the "Create a developer account" page.

Follow the instructions on the page to create a developer account, and you'll be able to use the Flex Message Simulator.

For more information on the developer account, see Create a developer account (only on first login) in the LINE Developers Console documentation.

# Date of Change

December 7, 2021

LINE will continue to work to further improve its service to our customers. We apologize for any inconvenience that this may have caused, and thank you for your understanding.

Flex Message Simulator LINE Developers Console
"LINE original unicode emojis" of the Messaging API will be discontinued on March 31, 2022
2021/11/30

Currently, there are 3 types of emojis that can be sent via the Messaging API.

  • LINE emojis
  • Unicode emojis
  • LINE original unicode emojis (deprecated)

Among these, "LINE original unicode emojis", which has been deprecated, will be end-of-life on March 31, 2022.

# Scheduled date of discontinuation

March 31, 2022

# Impact

After March 31, 2022, "LINE original unicode emojis" will no longer be displayed sequentially. This change will also be applied to "LINE original unicode emojis" sent before the discontinuation.

Before discontinuation After discontinuation
"LINE original unicode emojis" before discontinuation "LINE original unicode emojis" after discontinuation

# Alternative way

Use "LINE Emoji" with the emojis property. For more information, see List of available LINE emojis in the Messaging API documentation.

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

Messaging API Deprecated End of life
LINE TV will be closed on December 31, 2021
2021/11/29

We will close LINE TV, a premium video streaming service available in Thailand, on December 31, 2021.

The related documentation and API reference will be removed without notice in late December 2021.

# Target products

  • LINE TV applications (iOS, Android, Huawei)
  • LINE TV web sites
  • LINE TV API and Data

# Scheduled date of closing

December 31, 2021

The date of closing is subject to change without notice.

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

LINE TV End of life
The review process for LINE MINI App has changed
2021/11/29
Updated on December 16, 2021

Due to some errors in the explanation of the review process, we've updated Workflow for LINE MINI Apps being published for the first time and Workflow for previously published LINE MINI Apps.

The review process for the LINE MINI App has changed starting November 29, 2021.

Going forward, once your LINE MINI App has been approved, the status of your channel will automatically change to "Approved" and immediately to "Published". Using the Search enable button button from the Workflow tab on the LINE Developers Console, you can publish your LINE MINI App within LINE and commence your service.

# Details of change

Prior to the change, you had to submit a separate request for publication, which had to be approved by LINE before the status of your LINE MINI App Channel changed from "Approved" to "Published". Going forward, there will be no separate process for requesting to publish your LINE MINI App.

# Workflow for LINE MINI Apps being published for the first time

Once your status automatically becomes "Published", users can technically access your LINE MINI App, as your LIFF URL and the "Pin to home tab" feature will be enabled. However, because search hasn't been enabled within LINE, users won't be able to search for your service yet.

When you want to make your service searchable, click the Search enable button from the Workflow tab on the LINE Developers Console and users will be able to immediately search for your LINE MINI App in LINE. However, if Search enable isn't activated within 30 days (including weekends and holidays) after the status becomes "Published", it will automatically be enabled at 9:00 AM JST on the 31st day.

For example, if your LINE MINI App status became "Published" on August 1, the "Search enable" feature will be automatically activated on 9:00 AM of August 31.

# Workflow for previously published LINE MINI Apps

The workflow is slightly different if your LINE MINI App has already been published before.

Once changes to your LINE MINI App have been approved, the status of your channel will change to "Approved". In order to change the status to "Published", you will have to manually change the status of your channel using the Publish changes button from the Workflow tab on the LINE Developers Console.

Once your status becomes "Published", changes made at the time of the review request are updated in the Published channel and LIFF of the Published channel (e.g. LINE MINI App name, Channel settings, LIFF Settings, etc.).

When you want to publish your LINE MINI App, click the Publish changes button and the status will immediately change to "Published". However, if Publish changes isn't activated within 30 days (including weekends and holidays) after status becomes "Approved", the changes will automatically be reflected on 9:00 AM JST on the 31st day.

For example, if your LINE MINI App status became "Approved" on August 1, the new changes will be automatically activated on 9:00 AM of August 31.

There may be a slight delay in status change

Although the status is supposed to be automatically changed at 9:00 AM JST on the 31st day, there may be a 1-2 hour delay. This is applicable for both LINE MINI Apps being published for the first time and previously published LINE MINI Apps.

For more information, see Review process in the LINE MINI App documentation.

LINE MINI App
Blockchain Service channels will now have a "Pending" status if the Service wizard on the LINE Blockchain Developers is incomplete
2021/11/25

To develop a service using the Blockchain service (opens new window), you must create a Blockchain Service channel on the LINE Developers Console, and complete the Service wizard (opens new window) on the LINE Blockchain Developers (opens new window).

Previously, the status when you first created a Blockchain Service channel had been "Developing", whether you completed the LINE Blockchain Developers Service wizard or not. From now on, when you first create a Blockchain Service channel, the default status will be "Pending".

"Developing" Blockchain service channel "Pending" Blockchain service channel
Developing status on blockchain service channel Pending status on blockchain service channel

"Pending" means that the Service wizard on the LINE Blockchain Developers is incomplete. When the status of the Blockchain Service channel is "Pending", the following restrictions apply:

  • The LINE Login feature is unavailable
  • The Messaging API feature is unavailable
  • The channel can't be published

When you complete the LINE Blockchain Developers Service wizard, the status of the Blockchain Service channel will change from "Pending" to "Developing", and the above restrictions will be removed.

The newly-added "Pending" status won't be applied to existing Blockchain Service channels, even if the LINE Blockchain Developers Service wizard has not yet been completed.

For more information on the Blockchain service, see LINE Blockchain Docs (opens new window).

LINE Developers Console LINE Blockchain Platform
Timeline has been revamped as a video platform called "LINE VOOM"
2021/11/25

Timeline has been revamped as a video platform and will be called "LINE VOOM" starting November 25, 2021. For more information about LINE VOOM, see Configuration changes due to renewal (opens new window)(Japanese only).

With the release of LINE VOOM, the name on the LINE Developers site has also been changed from Timeline to LINE VOOM. The LINE URL scheme for opening Timeline is still available in LINE VOOM. For more information, see Using LINE features with the LINE URL scheme.

LINE Platform
LIFF v2.17.0 released
2021/11/11

We've released LIFF v2.17.0.

In LIFF v2.17.0, the following bug has been fixed.

# We've fixed a bug where executing the liff.openWindow() method in LINE for iOS would open URLs with unintended query parameters added to the end of the URL fragment

If the url property doesn't contain a query parameter but contains a URL fragment, executing the liff.openWindow() method in LINE for iOS would open URLs with unintended query parameters added to the end of the URL fragment.

This bug was fixed in LIFF v2.17.0 so that even in the above case, the correct URL would be opened.

# Examples of URL opened when executing the liff.openWindow() method

LIFF SDK version url property URL opened
v2.16.1 https://example.com#URL-fragment https://example.com#URL-fragment?is_liff_external_open_window=false
v2.17.0 https://example.com#URL-fragment https://example.com#URL-fragment

For more information on the liff.openWindow() method, see liff.openWindow() in the LIFF API reference.

LIFF LINE MINI App
Introducing the LIFF features shared during the LIFF sessions at LINE DEVELOPER DAY 2021
2021/11/11

At LINE DEVELOPER DAY 2021, there were two sessions on LIFF.

Here are some references and documentation related to the LIFF features introduced during the sessions. Take a look if there's a feature that you're interested in or thinking about using.

# Features introduced in "Introduction to LIFF/LINE Mini App - Characteristics and Practical Development"

Feature Overview Reference/Documentation
LINE Login integration Performs the login process in the LINE's in-app browser or external browser.
Share Target Picker Displays the target picker and sends the message created by the developer to the selected target.
liff.scanCodeV2 Launch the 2D code reader and obtain string. liff.scanCodeV2()
liff.isApiAvailable Checks whether the specified API is available in the environment where you started the LIFF app. liff.isApiAvailable()
liff.getLineVersion Gets the user's LINE version. liff.getLineVersion()
liff.getOS Gets the environment in which the user is running the LIFF app. liff.getOS()
Simplified user agreement Allows users to skip the consent screen that is displayed when they access the LINE MINI App for the first time. Skipping the channel consent process
liff.referrer query parameter Gets the referrer of the page before LIFF-to-LIFF transition. Get URL from before LIFF-to-LIFF transition
Getting Started with LIFF Development Guide for adding a channel for the LIFF app on the LINE Developers Console and using the LIFF SDK for development.

# Features introduced in "For Improvement of Developer Experience of All LIFF App Developers"

Feature Overview Past announcements
LINE API Status (opens new window) LINE API Status is a site through which you can check the service availability and outage status of APIs and services that LINE provides. Service availability and outage status information is provided in English. LIFF and LINE Login have been added to services covered by LINE API Status
LIFF Playground (opens new window) The LIFF Playground allows you to easily try out the LIFF APIs. New LIFF starter app and LIFF Playground released
LIFF starter app (opens new window) The LIFF starter app is only a demo of the LIFF app initialization to help you understand how to start developing LIFF apps. Same as above.

# LINE DEVELOPER DAY 2021 related links

LIFF LINE MINI App
Messaging API Update (November 2021)
2021/11/09

New features have been added to the Messaging API. These are the features that have been newly added or updated.

# You can now retrieve the text entered by the user in a message sticker

message sticker

You can now retrieve the text entered by the user in a Message sticker.

In the Messaging API, when a user sends a sticker to the LINE Official Account, a webhook event is sent from the LINE Platform to the bot server. For message stickers, a text field has been added to the message object of the sticker included in this webhook, allowing you to retrieve any text entered by the user.

"message": {
    "type": "sticker",
    "id": "123456789012345678",
    "stickerId": "738839",
    "packageId": "12287",
    "stickerResourceType": "MESSAGE",
    "keywords": [
        "Anticipation",
        "Sparkle",
        "Straight face",
        "Staring",
        "Thinking"
    ],
    "text": "Let's\nhang out\nthis weekend!"
}

With this change, the value of the stickerResourceType field, which represents the resource type of the sticker, has also been changed as follows:

Resource type Before change After change (current)
Message sticker PER_STICKER_TEXT MESSAGE
Custom sticker NAME_TEXT CUSTOM

For more information, see Sticker in the Messaging API reference.

# You can now retrieve up to 1000 user IDs of friends

Previously when you attempted to get a list of users who added your LINE Official Account as a friend, only a maximum of 300 user IDs could be retrieved at a time. With this update, you can retrieve up to 1000 user IDs at a time by specifying the number to be retrieved with the limit property.

Before change After change (current)
Max number of user IDs that can be obtained at one time 300 1000

For more information, see Get a list of users who added your LINE Official Account as a friend in the Messaging API reference.

Messaging API
LIFF and LINE Login have been added to services covered by LINE API Status
2021/11/08

LIFF and LINE Login have been added to the LINE API Status (opens new window).

LINE API Status is a site through which you can check the service availability and outage status of APIs and services that LINE provides. Service availability and outage status information is provided in English.

# Services covered by LINE API Status

LINE API Status covers these services:

  • LIFF
  • LINE Login
  • Messaging API
    • API
    • Webhook
  • LINE Developers
    • LINE Developers site
    • LINE Developers Console

Currently, LINE API Status doesn't cover the LINE app and services other than the above (such as LINE MINI App and LINE Pay).

The information available on LINE API Status

LINE will provide information on outage status through LINE API Status, but this doesn't guarantee immediate, accurate, or comprehensive information. We will continue to inform you of the details of the outage, such as the cause and extent of influence, through News on the LINE Developers site.

LINE Platform LIFF LINE Login
[Resolved] Notice about service outage for LINE Platform
2021/11/04

We'd like to inform you about a service outage regarding the LINE Platform. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

November 3, 2021 around 16:55 - around 17:05 (UTC+9)

# Cause of the outage

Server failure

# Impact

  • Messaging API
  • LINE MINI App

# Details

These are the main impacts per product:

# Messaging API

During the stated date and time, the following problem occurred:

  • There were instances where sending webhook events was delayed or didn't work properly.
  • Some requests weren't processed properly, resulting in errors with status code 5xx.
  • Messages may not have been actually sent in some requests to the endpoints that succeeded and returned a status code 200 when making a request to the following endpoints.

Due to this outage, the messages that weren't properly sent even if the API requests succeeded, won't be counted as the LINE Official Account usage fees and the "number of sent messages" that can be confirmed in some way such as the Get number of sent push messages endpoint.

# Retrying a failed API request

In some APIs, you can safely retry a request while preventing the same request from being accepted in duplicate by using a retry key (X-Line-Retry-Key) when an error with status code 5xx occurs or when the request times out.

For more information, see Retrying a failed API request and APIs for which retry keys are available in the LIFF documentation.

# LINE MINI App

  • Some requests to the following endpoint weren't processed properly, resulting in errors with status code 5xx.

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

Outage Report Messaging API Options for corporate customers LINE MINI App
As of November 18, 2021, the rate limit will change for some endpoints in the Messaging API
2021/11/04

In the Messaging API, each endpoint has a rate limit.

The rate limit will change for some endpoints starting November 18, 2021. Refer to this table for the differences between before and after changes.

Endpoint Before Change After Change
2,000 requests per second 100 requests per hour *

* Creating and deleting rich menus using the LINE Official Account Manager is not subject to this restriction.

For APIs other than the above, there are no changes in the rate limits.

# Expected Date of Specification Change

November 18, 2021

The details and date of this specification change are subject to change without notice.

LINE will continue to work to further improve its service to our customers. Thank you for your understanding.

Messaging API
New LIFF starter app and LIFF Playground released
2021/11/02

We've released a new LIFF starter app and LIFF Playground to help developers develop LIFF apps more smoothly.

# LIFF starter app

The new LIFF starter app is much simpler than its previous version.

The previous LIFF starter app was both a demo of the LIFF app initialization and a demo of the LIFF API. The new LIFF starter app is only a demo of the LIFF app initialization to help you understand how to start developing LIFF apps. The LIFF API demo included in the previous LIFF starter app has been separated as the LIFF Playground.

At this time, the new LIFF starter app supports only vanilla JavaScript. We plan to provide support for JavaScript frameworks such as Next.js and Nuxt in the near future.

For more information, see LIFF starter app (opens new window).

# LIFF Playground

With the release of the new LIFF starter app, we have released the LIFF Playground, which allows you to easily try out the LIFF APIs. For example, you can perform the login process on the LIFF Playground and get the environment in which the LIFF app is running.

To try the LIFF Playground in a LIFF browser, open the LIFF Playground in your mobile browser and click the Open In LINE button in the header.

For more information, see LIFF Playground (opens new window).

We'll continue to improve the quality of the LINE Developers site and developer documentation to make it even easier for developers to develop apps using our services.

LIFF LINE MINI App
LINE DEVELOPER DAY 2021 will be held on November 10 and 11
2021/10/28

The tech conference, LINE DEVELOPER DAY 2021, is being held over 2 days, from November 10th until the 11th. All sessions will be delivered in three languages: Japanese, English and Korean.

More than 50 sessions will be delivered during LINE DEVELOPER DAY 2021. Among them, here are the sessions related to LINE API and LINE Developers site.

For more information about how to apply, the time of the event, and the content of the sessions, see LINE DEVELOPER DAY 2021 official website (opens new window).

Docs LINE Platform LIFF LINE MINI App
LIFF v2.16.1 released
2021/10/26

We've released LIFF v2.16.1.

In LIFF v2.16.1, the following bugs have been fixed.

# We've fixed the bug that caused the file size to become enlarged in the CDN version of LIFF v2.14.0 or later

Due to an internal source code change in LIFF v2.14.0, the CDN version of LIFF v2.14.0 or later had a bug that caused the file size to become enlarged. This bug has been fixed in LIFF v2.16.1 so that the file size isn't enlarged.

# We've fixed the bug that caused an error when building a project using webpack v5

Node.js polyfill has been removed from webpack v5. (opens new window) Accordingly, if you use the npm version of LIFF v2.16.0 or earlier in a project using webpack v5, an error will occur during the build and the following message will be displayed.

Module not found: Error: Can't resolve 'crypto' in 'node_modules/js-crypto-env/dist'
 
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
 
If you want to include a polyfill, you need to:
- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
resolve.fallback: { "crypto": false }

This is because the implementation in LIFF v2.16.0 or earlier depended on Node.js polyfill within the LIFF SDK. In LIFF v2.16.1, the implementation doesn't depend on Node.js polyfill, so the above error no longer occurs.

# Using the npm version of LIFF v2.16.0 or earlier in a project using webpack v5

To fix the bug while maintaining the same LIFF SDK version, you need to install Node.js polyfill and configure webpack.config.js.

First, install Node.js polyfill, crypto-browserify and stream-browserify.

# For npm
$ npm install crypto-browserify stream-browserify

# For Yarn
$ yarn add crypto-browserify stream-browserify

Next, set the resolve.fallback of the webpack.config.js as shown below:

module.exports = {
  resolve: {
    fallback: {
      crypto: require.resolve('crypto-browserify'),
      stream: require.resolve('stream-browserify'),
    },
  },
};

# How to update to LIFF v2.16.1

If you're using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), you will automatically be updated to v2.16.1.

If you're using an npm package, you can update to v2.16.1 by executing either npm install @line/liff@2.16.1 or yarn add @line/liff@2.16.1.

For more information on integrating the LIFF SDK, see Integrating the LIFF SDK with the LIFF app.

LIFF LINE MINI App
[Resolved] Notice about service outage for the Messaging API
2021/10/21

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

October 20, 2021 around 17:29 - around 17:41 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

During the stated date and time, some requests may not have been processed properly, resulting in an error with status code 5xx.

# Retrying a failed API request

In some APIs, you can safely retry a request while preventing the same request from being accepted in duplicate by using a retry key (X-Line-Retry-Key) when an error with status code 5xx occurs or when the request times out.

For more information, see Retrying a failed API request and APIs for which retry keys are available in the LIFF documentation.

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

Outage Report Messaging API Options for corporate customers
Docs for LINE Social Plugins has been moved to the LINE Developers site
2021/10/21

In order to consolidate the information for developers and make it easier to find, we have moved the LINE Social Plugins documentation to the LINE Developers site. These are the documents for LINE Social Plugins that have been migrated:

Before transition After transition
LINE Social Plugins
(https://social-plugins.line.me/)		 LINE Social Plugins within the LINE Developers site
(https://developers.line.biz/en/docs/line-social-plugins/)

There is no change to the content of the documentation and API reference. The old site will be removed without notice in the future.

# About LINE Social Plugins

With LINE Social Plugins, you can place three different types of buttons on your website or app. For example, when users visit your website and tap the "Share on LINE" button, they can share information about your website with their friends and groups of LINE.

We'll continue to improve the quality of the LINE Developers site and developer documentation to make it even easier for developers to develop apps using our services.

LINE Social Plugins Docs
[Resolved] Notice of email transmission outage on the LINE Developers Console
2021/10/13

We'd like to inform you about a service outage regarding the LINE Developers Console where various emails couldn't be sent. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of failure

October 12, 2021 around 14:30 - around 16:08 (UTC+9)

# Cause of the failure

Server failure

# Impact

Various emails failed to be sent on the LINE Developers Console and options for corporate customers

# Details

The following failures occurred at different times of the day.

Time Content
around 14:30 - around 16:07
  • Some error notification emails from options for corporate customers weren't sent properly.
around 14:31 - around 16:08
  • Some invitation emails for granting provider and channel access weren't sent properly.
  • Some emails for verifying email address from the LINE Developers Console's Profile > Basic information > Email > Get verification link weren't sent properly.
around 15:40 - around 16:07

The issue is now resolved and notification emails are being sent normally.

Emails that weren't sent properly due to this outage won't be resent, even after the outage has been resolved. We apologize for the inconvenience, but we ask that you repeat the process of granting provider and channel access and verifying email address.

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

LINE Developers Console Options for corporate customers Outage Report
LIFF v2.16.0 released
2021/10/12

We've released LIFF v2.16.0.

In LIFF v2.16.0, the following features have been added.

# The share target picker now has an option to control whether to send to multiple recipients or just one

The isMultiple property has been added to the liff.shareTargetPicker() method. By setting the isMultiple property, the user can now control whether or not to allow selection of multiple message recipients in the target picker.

If you set the isMultiple property to true, the user can select multiple message recipients in the target picker. If you set it to false, the user can select only one friend as the message recipient. The default value is true.

isMultiple value Available target recipients Available number of selection
true Groups, friends, chats Can select multiple recipients
false Friend Can select only 1 recipient
Setting isMultiple to false doesn't guarantee that the message will be sent to only one friend

Even if you set the isMultiple property to false, you can still send a message to multiple users by calling the share target picker multiple times, or by re-sharing the same message to different recipients. To strictly allow a user to send a message to one friend only once, add a restriction when implementing the LIFF app.

Here's an example of sending a message containing a URL and restricting access to the URL.

  1. Give the URL a unique token and send the message.
  2. When the URL in the message is accessed, the server side verifies the token and restricts access by multiple users.
We don't retrieve the number of people to whom a user has sent a message using the share target picker

In order to protect user privacy, we neither collect nor provide information on how many people received a message from a user through the share target picker.

Sample code with the isMultiple property added to the liff.shareTargetPicker() method:

if (liff.isApiAvailable('shareTargetPicker')) {
  liff.shareTargetPicker(
      [
        {
          type: "text",
          text: "Hello, World!",
        },
      ],
      {
        isMultiple: true,
      }
    )
    .then(function (res) {
      if (res) {
        // succeeded in sending a message through TargetPicker
        console.log(`[${res.status}] Message sent!`)
      } else {
        const [majorVer, minorVer] = (liff.getLineVersion() || "").split('.');
        if (parseInt(majorVer) == 10 && parseInt(minorVer) < 11) {
          // LINE 10.3.0 - 10.10.0
          // Old LINE will access here regardless of user's action
          console.log('TargetPicker was opened at least. Whether succeeded to send message is unclear')
        } else {
          // LINE 10.11.0 -
          // sending message canceled
          console.log('TargetPicker was closed!')
        }
      }
    }).catch(function (error) {
      // something went wrong before sending a message
      console.log('something wrong happen')
    })
}

For more information, see liff.shareTargetPicker() in the LIFF API reference.

LIFF LINE MINI App
[Resolved] Notice about service outage for LINE notification messages
2021/10/06

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

Use of LINE notification messages requires an application

LINE notification messages can only be used by corporate users who have submitted the required applications. For more informations, see Overview in the Options for corporate customers documentation.

# Date and time of outage

October 5, 2021 around 10:30 - October 6, 2021 around 12:41 (UTC+9)

# Cause of the outage

Server failure.

# Impact

LINE notification messages

# Details

There were instances where LINE notification messages for some users weren't sent per usual.

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

Outage Report Options for corporate customers
[Resolved] Notice about service outage for LINE Platform
2021/10/01

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

# Date and time of outage

October 1, 2021 around 9:45 - 9:49 (UTC+9)

# Cause of the outage

Network failure.

# Impact

  • Messaging API
  • LINE Login
  • LIFF/LINE MINI App

# Details

These are the main impacts per product:

# Messaging API

  • Some requests weren't processed properly, resulting in errors with status code 5xx.
  • There were instances where sending webhook events was delayed or didn't work properly.
  • Messages may not have been actually sent in some requests to the endpoints that succeeded and returned a status code 200 when making a request to the following endpoints.

Due to this outage, the messages that weren't properly sent even if the API requests succeeded, won't be counted as the LINE Official Account usage fees and the "number of sent messages" that can be confirmed in some way such as the Get number of sent push messages endpoint.

# LINE Login

  • There were instances where LINE Login didn't work per usual.

# LIFF/LINE MINI App

  • There were instances where LIFF/LINE MINI App couldn't be used per usual.
  • There were instances where service messages weren't sent per usual.

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

Outage Report LINE Platform Messaging API LINE Login LIFF LINE MINI App
LIFF v1 has been discontinued on October 1, 2021
2021/10/01

As announced on September 17, 2021, October 1, 2021 marks the end-of-life for LIFF v1.

However, since the Server API is managed on a different schedule than that of LIFF v1, it won't be impacted by this discontinuation.

# Target version

LIFF v1

If you're using LIFF v1, migrate to LIFF v2

For more information on migrating to LIFF v2, see Migrate to LIFF v2 in the news from April 5, 2021.

# Scheduled date of discontinuation

October 1, 2021

# Impact

Gradually, you won't be able to refer to the LIFF SDK URL (https://d.line-scdn.net/liff/1.0/sdk.js) or use the LIFF v1 API.

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

LIFF LINE MINI App End of life
LIFF v2.15.0 released
2021/09/30

We've released LIFF v2.15.0.

In LIFF v2.15.0, the following features have been added.

# The 2D code reader feature has been added

The liff.scanCodeV2() method, which can launch a 2D code reader within a LIFF app, has been added.

Due to technical problems, liff.scanCode() isn't available for use on LINE for iOS version 9.19.0 or later, or on external browsers, but with liff.scanCodeV2(), you can now launch a 2D code reader even on the newest version of LINE for iOS, and on external browsers.

The operation specification of liff.scanCodeV2()

liff.scanCodeV2() internally uses an external library called jsQR (opens new window). Therefore, the 2D code reader to be launched when the liff.scanCodeV2() method is executed depends on the operation specification of jsQR (opens new window). Libraries used may be updated or changed without notice.

liff.scanCode() method deprecated

The traditional liff.scanCode() method has been deprecated. We recommend using the liff.scanCodeV2() method for implementing a 2D code reader.

# Implementing a 2D code reader with liff.scanCodeV2()

Implementing a 2D code reader using liff.scanCodeV2() is the same as that of liff.scanCode(). Turn on Scan QR from the LIFF tab on the LINE Developers Console before following these steps to implement liff.scanCodeV2().


# liff.scanCodeV2() sample code:
liff.scanCodeV2().then(result => {
	// result = { value: '' }
});
2D code reader support on the LINE MINI App is scheduled for October 7, 2021

Using liff.scanCodeV2() to launch a 2D code reader requires turning on Scan QR from the LIFF tab of the LINE Login channel on the LINE Developers Console. The Scan QR setting is scheduled to be added for LINE MINI App channels on October 7, 2021. Currently, as of September 30, 2021, liff.scanCodeV2() isn't available for LINE MINI App channels.

Scan QR

# The operating environment of the liff.scanCodeV2() method

These are the operating environments of the liff.scanCodeV2() method and the 2D code reader that is displayed:

# Operating environments

Due to technical problems, the traditional liff.scanCode() method isn't available for use on LINE for iOS version 9.19.0 or later, or on external browsers. The newly added liff.scanCodeV2() method, however, is available both on the newest version of LINE for iOS and on external browsers.

OS Version LINE app version External browser
9.18.0 or earlier 9.19.0-11.6.x 11.7.0 or later
iOS 11-14.2 ✅ ❌ ❌ ✅ *1
14.3 or later ❌ ❌ ✅ *2 ✅ *1
Android All versions ❌ ❌ ✅ *2 ✅ *1
PC All versions ❌ ❌ ❌ ✅ *1

*1 You can only use web browsers that support WebRTC API (opens new window).

*2 Only available when the screen size of the LIFF browser is Full. For details, see Size of the LIFF browser in the LIFF documentation.

# 2D code reader

For the liff.scanCode() method, Android and iOS each had different 2D code reader screens, but for the liff.scanCodeV2() method, the following same screen is displayed, regardless of OS.

2D code reader screen

If you launch the 2D code reader, a Tall size sub-window will be displayed on the bottom of the Full size LIFF app screen. Also, if you click on the 2D code selection icon located at the bottom-right of the screen, you can select a 2D code to be read from a photo.


For more information on implementing a 2D code reader using liff.scanCodeV2(), see Opening the 2D code reader in the LIFF documentation.

# The option of automatically executing the liff.login() method when initializing LIFF apps in external browsers has been added

The withLoginOnExternalBrowser property has been added to the liff.init() method. Normally, when you access LIFF application on an external browser, you need to explicitly go through the login process using the liff.login() method. By specifying true in the newly added withLoginOnExternalBrowser property, you can automatically execute the liff.login() method when the LIFF app is initialized.

Login

Sample code with the withLoginOnExternalBrowser property added to the liff.init() method:

liff.init({
  liffId: "123456-abcdef",
  withLoginOnExternalBrowser: true, // Enable automatic login process
}).then(() =>
  // Start to use liff's api
});

For more information, see liff.init() in the LIFF API reference.

LIFF LINE MINI App
[Resolved] Notice about service outage for Messaging API
2021/09/24

We'd like to inform you about a service outage regarding the Messaging API. We've released a version of LINE that resolved the issue. We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

September 13, 2021 - September 24, 2021

# Cause

Issue with LINE for iOS and iPadOS.

# Impact

When sending an imagemap message from the LINE Official Account, LINE would be forced to close if a user taps on a specific area in the image.

# Details

LINE would be forced to close when all of the following conditions are met:

  • A user uses LINE for iOS or iPadOS.
  • A user uses LINE version 11.16.0.
  • An imagemap message was sent from the LINE Official Account using the Messaging API.
  • An imagemap URI action object was specified in the actions property of the sent imagemap message.
  • When there were multiple objects in actions, the imagemap URI action object was defined after the other objects.
  • The user tapped the area of the imagemap URI action object.

If all of the above conditions are met, updating user's LINE version to 11.16.1 or later will resolve the issue.

Rich message (opens new window) sent from LINE Official Account Manager (opens new window) are not affected by this outage.

# Example of an affected actions property

"actions": [
    {
        "type": "message",
        "text": "Hello",
        "area": {
            "x": 520,
            "y": 586,
            "width": 520,
            "height": 454
        }
    },
    {
        "type": "uri",
        "linkUri": "https://example.com/",
        "area": {
            "x": 0,
            "y": 586,
            "width": 520,
            "height": 454
        }
    }
]

# Example of an unaffected actions property

"actions": [
    {
        "type": "uri",
        "linkUri": "https://example.com/",
        "area": {
            "x": 0,
            "y": 586,
            "width": 520,
            "height": 454
        }
    },
    {
        "type": "message",
        "text": "Hello",
        "area": {
            "x": 520,
            "y": 586,
            "width": 520,
            "height": 454
        }
    }
]

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

Outage Report Messaging API
A parameter has been added to disable Auto login in LINE Login
2021/09/21

As announced on July 12, 2021, for LINE Login, in environments where both Auto login and Single Sign On (SSO) login are available, Auto login takes precedence.

As of September 21, 2021, if you want users to log in via SSO login instead of Auto login, you can disable Auto login by adding the query parameter disable_auto_login=true to the authorization URL when Authenticating users and making authorization requests.

# Specification

By using the disable_auto_login parameter, even in an environment where both Auto login and SSO login are available, you can explicitly provide SSO login to the user logging in.

explicitly provide SSO login

On iOS, disabling Auto login by adding the disable_ios_auto_login parameter to the authorization URL has already been available, but going forward, the disable_auto_login parameter will also be available on Android and iOS as well.

For more information, see Authenticating users and making authorization requests in the LINE Login documentation.

We recommend using "disable_auto_login"

You can continue using the disable_ios_auto_login parameter, but we recommend using a disable_auto_login parameter that works regardless of OS.

# Use cases of the disable_auto_login parameter

Auto login may fail when private browsing is enabled in web apps that incorporate LINE Login.

In such environments where Auto login fails, if the user who failed LINE Login is prompted to reattempt with an authorization URL where Auto login is enabled, the user will continue to fail at LINE Login repeatedly. In order to prevent continuous login failures, once Auto login fails, you can use the disable_auto_login parameter to prompt the user to reattempt LINE Login with an authorization URL that has Auto login disabled.

Simplified flow diagram when auto-login fails

For more information, see How to handle Auto login failure in the LINE Login documentation.

LINE Login
LIFF v1 will be discontinued on October 1, 2021
2021/09/17

As announced on April 5, 2021, LIFF v1 will be end-of-life on October 1, 2021, which marks the end of its deprecation period.

# Target version

LIFF v1

If you're using LIFF v1, migrate to LIFF v2

For more information on migrating to LIFF v2, see Migrate to LIFF v2 in the news from April 5, 2021.

# Scheduled date of discontinuation

October 1, 2021

# Impact

Gradually after the discontinuation of LIFF v1 on October 1, 2021, you won't be able to refer to the LIFF SDK URL (https://d.line-scdn.net/liff/1.0/sdk.js) or use the LIFF v1 API.

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

LIFF LINE MINI App Deprecated End of life
[Resolved] Notice about service outage for the Messaging API
2021/09/16

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

September 15, 2021 around 9:51 - around 10:22 (UTC+9)

# Cause of the outage

Server failure

# Impact

All APIs provided by the Messaging API

# Details

During the stated date and time, some requests may not have been processed properly, resulting in an error with status code 5xx.

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

Outage Report Messaging API
Requirement reduced for minimum number of users per audience when sending messages
2021/09/14

Narrowcast messages in the Messaging API can specify an audience as a recipient. Previously, there was a minimum requirement of "100 users per audience", but this requirement has been reduced to a minimum of 50 users.

See this table for the differences before and after the update:

Item Before change After change (current)
The number of users per audience Minimum: 100 Minimum: 50

# Target audiences

These are the audiences whose requirement has been reduced:

  • Audience for click-based retargeting
  • Audience for impression-based retargeting
  • Friend path audience
  • Video view audience
  • App event audience
  • Web traffic audience
Exception audiences

User ID upload audiences and chat tag audiences won't be affected by this change, as they originally had no minimum number of users per audience requirement.

Among the audiences whose requirement has been reduced, only click-based retargeting audiences and impression-based retargeting audiences can be created using the Messaging API.

For more information on how to create other audiences, see Managing Audience in the Messaging API reference.

For more information on how to send narrowcast messages, see Sending messages to multiple users via attribute data or retargeting (narrowcast messages) in the Messaging API documentation.

Messaging API
LIFF v2.14.0 released
2021/09/14

We've released LIFF v2.14.0.

This update only includes refactoring of the SDK. There is no change in features.

If you're using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), it will automatically update to v2.14.0.

If you're using the npm package, you can upgrade to v2.14.0 by running npm install @line/liff@2.14.0 or yarn add @line/liff@2.14.0.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

LIFF LINE MINI App
You can now change the order in which services are displayed on the provider page
2021/09/14

You can now change the order in which services are displayed on the Provider page.

The provider page can be configured from the Provider page tab on the LINE Developers Console. From the Provider page tab, drag and drop each service up and down to reflect the order in which they are displayed on the provider page.

You cannot change the order of the service categories: LINE Official Account, LINE MINI App, and LINE Login. You can only change the order in which the services under each category are displayed.

For details, see Provider page in the Options for corporate customers.

LINE Developers Console
We fixed the bug that caused content to be displayed incorrectly when returning to the LIFF app before transitioning between LIFFs
2021/09/08

As announced in the news on May 31, 2021, when users click the back button or return to the previous page after a transition between LIFF apps, the URL returned to the LIFF URL before the transition, but the screen remained the same or was blank. This issue has been fixed in LINE or Safari on iOS 14.7 and Safari 14.1.2 on macOS.

# Temporary support taken in response to this issue

Prior to May 31, 2021, the following issues occured with LINE or Safari on iOS 14.5.x or Safari 14.x on macOS.

Diagram of a blank screen when returning to the LIFF app before the transition between LIFF apps

We used a temporary fix by excluding only the URL fragment from the additional information in the LIFF URL during the redirection.

However, in iOS 14.7 or later and Safari 14.1.2 or later, the issue in Apple WebKit (opens new window) has been fixed so that secondary redirects containing URL fragments are now redirected correctly.

# Continuation of the temporary support

These versions still have the bug, so the temporary support will continue for these versions:

  • iOS: 14.5 - 14.6
  • Safari on macOS: 14.0 - 14.1.1

Redirect behavior for each version:

Environment Behavior LIFF URL Endpoint URL Secondary redirect URL
  • iOS: 14.7 or later
  • Safari: 14.1.2 or later
 ✅ Normal https://liff.line.me/{liffId}
/path?key=value#URL-fragment		 https://example.com https://example.com
/path?key=value#URL-fragment
  • iOS: 14.5 - 14.6
  • Safari: 14.0 - 14.1.1
 ❌ Temporary
support		 https://liff.line.me/{liffId}
/path?key=value#URL-fragment		 https://example.com https://example.com
/path?key=value
  • iOS: 14.4 or ealier
  • Safari: 13.x or earlier
 ✅ Normal https://liff.line.me/{liffId}
/path?key=value#URL-fragment		 https://example.com https://example.com
/path?key=value#URL-fragment
On URL fragments in LIFF URLs

If you have temporarily excluded URL fragments from your LIFF URLs due to the impact of the issue, we recommend that you include URL fragments in your LIFF URLs again.

For more information, see Opening a LIFF app from another LIFF app (LIFF-to-LIFF transition) in the LIFF documentation.

LIFF LINE MINI App
You can now confirm the number of images sent simultaneously through webhooks
2021/09/07

With the Messaging API, when a user sends two images simultaneously, two webhook events are sent from the LINE Platform to the bot server. These fields have been added to the message object of images, which is included in the webhook:

  • imageSet.id: Image set ID
  • imageSet.index: An index starting from 1, indicating the image number in a set of images sent simultaneously
  • imageSet.total: Total number of images sent simultaneously

Previously, there was no way to confirm whether two images were sent simultaneously or consecutively. However, with the addition of these fields, you can now confirm whether a user has sent multiple images simultaneously.

// When two images are sent simultaneously (First image)
"message": {
    "type": "image",
    "id": "354718705033693859",
    "contentProvider": {
        "type": "line"
    },
    "imageSet": {
        "id": "E005D41A7288F41B65593ED38FF6E9834B046AB36A37921A56BC236F13A91855",
        "index": 1,
        "total": 2
    }
}

// When two images are sent simultaneously (Second image)
"message": {
    "type": "image",
    "id": "354718705033693861",
    "contentProvider": {
        "type": "line"
    },
    "imageSet": {
        "id": "E005D41A7288F41B65593ED38FF6E9834B046AB36A37921A56BC236F13A91855",
        "index": 2,
        "total": 2
    }
}

For more information, see Image in the Message event section of the Messaging API reference.

Messaging API
[Resolved] Notice about service outage for LINE Platform
2021/09/06

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

# Date and time of outage

  1. September 4, 2021 around 10:36 (UTC+9)
  2. September 4, 2021 around 10:36 - 10:51 (UTC+9)
  3. September 4, 2021 around 10:50 - 10:51 (UTC+9)

# Cause of the outage

Network failure.

# Impact

  • Messaging API
  • LINE Login
  • LIFF/LINE MINI App

# Details

These are the main impacts per product:

# Messaging API

These problems occurred at the date and time of 1 and 3.

  • Some requests weren't processed properly, resulting in errors with status code 5xx.
  • There were instances where sending webhook events was delayed or didn't work properly.

# LINE Login

This problem occurred at the date and time of 2.

  • There were instances where LINE Login didn't work per usual.

# LIFF/LINE MINI App

These problems occurred at the date and time of 2.

  • There were instances where LIFF/LINE MINI App couldn't be used per usual.
  • There were instances where service messages weren't sent per usual.

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

Outage Report LINE Platform Messaging API LINE Login LIFF LINE MINI App
Header design has changed for the LINE MINI App
2021/09/06

The LINE MINI App header design has changed starting September 06, 2021.

Going forward, the header of the LINE MINI App will have the same design as the size of the LIFF browser Full.

Applying the new design

The new design is automatically applied to all existing LINE MINI Apps. There is no need to take individual action for each LINE MINI App.

# Schedule for the header design change

The transition to the new header design took place according to the following schedule.

Date Details of change
August 24, 2021 The new design is applied to newly-created LINE MINI App channels.
September 06, 2021 The new design is automatically applied to all existing LINE MINI App channels.

# Details of change

The design of the button area on the right side of the LINE MINI App header changed.

The changes are as follows:

Changes

Number Target OS Details of change
1 Only Andorid The icon designs have been changed.
2 iOS / Android The border surrounding the button icons has been removed.
3 iOS / Android The background color within the border has been removed.

The following is a comparison of the old and new header designs based on differences in OS and header color.

# Android

Header color Before design change After design change
white color#FFFFFF design update 1 before Arrow design update 1 after
red color#A9292F design update 2 before Arrow design update 2 after

# iOS

Header color Before design change After design change
white color#FFFFFF design update 3 before Arrow design update 3 after
red color#A9292F design update 4 before Arrow design update 4 after
LINE MINI App
[Resolved] Notice about outage for LINE Login and LIFF
2021/09/02

We'd like to inform you about a service outage regarding LINE Login and LIFF. The issue has now been resolved, but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • September 1, 2021 around 20:05 - around 20:18 (UTC+9)
  • September 1, 2021 around 20:42 - around 20:45 (UTC+9)
  • September 1, 2021 around 21:19 - around 21:20 (UTC+9)

# Cause of the outage

Server failure

# Impact

# LINE Login

# LIFF

# Details

In some LINE Official Accounts, adding as a friend and unblocking them with using the bot link feature didn't work properly.

Also, some requests to get the friendship status with the LINE Official Account weren't being processed properly and cause errors with status code 5xx.


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

Outage Report LINE Login LIFF
LINE Login button design guidelines have been changed
2021/09/01

LINE Login button design guidelines has been updated to reflect the changes to the LINE APP ICON GUIDELINE (opens new window).

Types Before change After change
Base Old LINE Login button for base color Arrow New LINE Login button for base color
Hover Old LINE Login button for hover color Arrow New LINE Login button for hover color
Press Old LINE Login button for press color Arrow New LINE Login button for press color
Disabled Old LINE Login button for disabled color Arrow New LINE Login button for disabled color

If the LINE Login buttons you are already using is outdated or you are implementing LINE Login buttons, see LINE Login button design guidelines in the LINE Login documentation to use the new LINE Login button design.

LINE Login
TLS 1.0 and TLS 1.1 support for LINE API has been discontinued at the end of August 2021
2021/09/01

As announced on May 13, 2021 and August 24, 2021, TLS 1.0 and TLS 1.1 support for LINE API has been discontinued at the end of August 2021.

# Domain names of the target LINE API

  • api.line.me
  • api-data.line.me

This applies to all LINE APIs using the domain names above, not just specific services.

# Supported SSL/TLS protocol versions

We no longer support TLS 1.0 and TLS 1.1.

Protocol version By the end of August 2021 After September 2021
TLS 1.3 ✅ ✅
TLS 1.2 ✅ ✅
TLS 1.1 ✅ ❌
TLS 1.0 ✅ ❌
SSL 3.0 ❌ ❌
SSL 2.0 ❌ ❌

# End-of-support date

August 31, 2021

# Impact

API requests that use TLS 1.0 or TLS 1.1 will sequentially result in error and no longer will be able to use the LINE API. If your environment is TLS 1.1 or lower, please upgrade your OS, OpenSSL, etc. so that your app or server can continue to communicate using TLS 1.2 or higher.

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

LINE Platform SSL/TLS End of life
Reminder: TLS 1.0 and TLS 1.1 support for LINE API will be discontinued at the end of August 2021
2021/08/24

As announced on May 13, 2021, TLS 1.0 and TLS 1.1 support for LINE API will be discontinued at the end of August 2021.

# Domain names of the target LINE API

  • api.line.me
  • api-data.line.me

All APIs using the domain names above are targeted without exception.

# Supported SSL/TLS protocol versions

We no longer support TLS 1.0 and TLS 1.1.

Protocol version By the end of August 2021 After September 2021
TLS 1.3 ✅ ✅
TLS 1.2 ✅ ✅
TLS 1.1 ✅ ❌
TLS 1.0 ✅ ❌
SSL 3.0 ❌ ❌
SSL 2.0 ❌ ❌

# Estimated end-of-support date

August 31, 2021

The date and time are subject to change without notice.

# Impact

If the source of requests to the LINE API does not support TLS 1.2 or higher, you will no longer be able to use the LINE API. If your environment is TLS 1.1 or lower, please upgrade your OS, OpenSSL, etc. so that your app or server can continue to communicate using TLS 1.2 or higher.

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

LINE Platform SSL/TLS End of life
[Resolved] Notice about service outage for the Messaging API
2021/08/23

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

August 22, 2021 around 23:20 - August 23, 2021 around 3:24 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending webhook events

# Details

During the stated date and time, webhook events have been delayed in some channels.

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

Outage Report Messaging API
LINE API emergency maintenance notice
2021/08/17

We will be performing emergency maintenance on LINE APIs as follows. During the maintenance period, some requests using LINE APIs may not be processed properly.

We sincerely apologize for any inconvenience that this may cause.

# Date and time of maintenance

August 18, 2021 4:00 - 4:30 (UTC+9)

Note that the end time of maintenance may change without notice.

# Purpose of maintenance

Handling hardware failures

# Impact for APIs

All LINE APIs provided on the LINE Platform, including these APIs, may be affected:

# Impact of maintenance

For about one to two minutes during the above date and time of maintenance, some LINE API requests may cause an error response with HTTP status code 5xx and may not be processed properly.

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

Maintenance Messaging API LINE Login LIFF LINE MINI App Options for corporate customers
Skip the consent screen with the newly-released "Channel consent simplification" feature
2021/08/12

A new feature, "Channel consent simplification", has been released, enabling users to skip the Consent screen that is displayed when they first access LINE MINI Apps.

Permission consent skipped with the "Channel consent simplification" feature

The only permission consent that can be skipped with the "Channel consent simplification" feature is user ID (openid scope). Permission required to get user profile information (the profile scope) or permission to send messages (the chat_message.write scope) aren't covered by "Channel consent simplification".

# Channel consent simplification feature setup

From your LINE MINI App channel on the LINE Developers Console, locate the Channel consent simplification section under the LIFF tab, and toggle the slider on (right) to enable the "Channel consent simplification" feature.

simplification feature setup

Cautions for using the Channel consent simplification feature
  • "Channel consent simplification" is a feature that can only be configured if the Region is set to "Japan" in the LINE MINI App channel.
  • "Channel consent simplification" can only be enabled for a LINE MINI App channel in the Developing process.
  • The openid scope will automatically be enabled for a channel with "Channel consent simplification" enabled.

# Detailed workflow of LINE MINI App with "Channel consent simplification" enabled

When a user first access a LINE MINI App with "Channel consent simplifcation" enabled, the channel consent screen is displayed, requesting consent regarding the use of User ID.

channel consent screen

Users will have to go through the consent process described above only once, upon which whenever they access another LINE MINI App for the first time, they will be able to skip the consent process and start using the service immediately.

Consent simplification enabled

For more information, see Skipping the consent screen in the LINE MINI App documentation.

LINE MINI App LINE Developers Console
LIFF v2.13.0 released
2021/08/12

We've released LIFF v2.13.0.

In LIFF v2.13.0, the following feature has been added, and bugs have been fixed.

In order to use the "Channel consent simplification" feature released today (August 12, 2021), you need to upgrade your LINE MINI App's LIFF SDK to v.2.13.0.

When you enable the "Channel consent simplification" feature, users can skip the "consent screen" that is displayed when they access a LINE MINI App for the first time.

For more information on usage conditions other than LIFF SDK version, such as behaviors and configuration, see Skipping the consent screen in the LINE MINI App documentation.

# We've fixed bugs in the npm package version of the LIFF SDK

Some bugs inside the npm package version have been fixed.

If you're using the npm package version, we recommend executing npm install @line/liff@2.13.0 or yarn add @line/liff@2.13.0 to upgrade to v2.13.0.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

LIFF LINE MINI App
[Resolved/Updated] Notice about outage for LINE MINI Apps and LINE Login
2021/08/11
Updated on August 12, 2021

As a result of our investigation, we've found out that LINE Login was also affected by this outage. Therefore, we've updated the title of this article, Impact, and Details.

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

# Date and time of outage

August 10, 2021 around 16:38 - around 16:48 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

These are the main impacts per product:

# LINE MINI App

In some LINE MINI Apps, even though requests to the endpoint were successful and status code 200 was returned, the messages may not have actually been sent.

# LINE Login

In some LINE Official Accounts, adding as a friend and unblocking them with using the botlink feature didn't work properly.


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

Outage Report LINE MINI App LINE Login
[Resolved] Notice about service outage for LINE Platform
2021/08/04

We'd like to inform you about a service outage regarding the LINE Platform. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

August 4, 2021 around 17:52 - 18:32 (UTC+9)

# Cause of the outage

System failure

# Impact

  • Messaging API
  • LINE Login
  • LIFF
  • Other general features provided by the LINE Platform

# Details

These are the main impacts per product:

# Messaging API

  • Some requests weren't processed properly, resulting in errors with status code 5xx.
  • There were instances where sending webhook events was significantly delayed or didn't work properly.

# LINE Login

  • There were instances where LINE Login didn't work per usual.

# LIFF/LINE MINI App

  • There were instances where LIFF/LINE MINI App couldn't be used per usual.
  • There were instances where service messages weren't sent per usual.

# LINE Developers Console

  • There were instances where some features of the LINE Developers Console couldn't be used per usual.

LINE will continue to improve the quality of its services to prevent future outages.

Thank you for your understanding.

Outage Report LINE Platform Messaging API LINE Login LIFF LINE MINI App LINE Developers Console
Messaging API Update (August, 2021)
2021/08/03

The following features have been changed in this update of the Messaging API.

# The period for getting "Narrowcast Message Status" has been extended from 7 days to 14 days

You can check the status of a narrowcast message using the Get narrowcast message status endpoint, after making a send request. The period during which you can get this "narrowcast message status" has now been extended.

Refer to the table below for the differences between before and after the change.

Item Before change After change(current)
Acquisition period within 7 days (168 hours) within 14 days (336 hours)

For more information, see Get narrowcast message status in the Messaging API reference.

# The maximum character limit for URLs for images, videos, and audio files has increased from 1000 to 2000

The maximum character limit for URLs for images, videos and audio files in Message objects has increased from 1000 to 2000. These are the target properties.

Message object Target
Message common properties
Image message
  • originalContentUrl property
  • previewImageUrl property
Video message
  • originalContentUrl property
  • previewImageUrl property
Audio message
  • originalContentUrl property
Image map message
  • baseUrl property
  • video.originalContentUrl property
  • video.previewImageUrl property
Template message
Flex Message
  • Image component url property
  • Icon component url property
Messaging API
[Resolved] Notice about service outage for the Messaging API
2021/08/02

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

August 2, 2021 around 16:02 - 16:16 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending webhook events

# Details

During the stated date and time, webhook events have been delayed in some channels.

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

Outage Report Messaging API
LINE Login v2.0 is deprecated
2021/07/28

LINE Login v2.0 is deprecated.

Although the date is yet to be determined, LINE Login v2.0 is scheduled for end-of-life in the future, so we recommend that you use LINE Login v2.1. Once determined, the end-of-life time and date will be announced here.

There will be a certain grace period between the end-of-life announcement and the actual end-of-life. For more information, see LINE Login versions.

LINE Login Deprecated Life cycle
[Resolved] Notice about service outage for the Messaging API
2021/07/26

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

July 26, 2021 around 13:22 - 15:12 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending webhook events

# Details

During the stated date and time, webhook events have been delayed in some channels.

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

Outage Report Messaging API
[Updated] Messaging API maintenance notice
2021/07/20
Updated on August 6, 2021

We've added a note under Getting the number of messages sent on the previous day will be slower than usual.

Maintenance will be performed on the Messaging API. We sincerely apologize for any inconvenience that this may cause and thank you for your understanding.

# Date and time of maintenance

August 5, 2021 1:00 - 3:00 (UTC+9)

Note that the end time of maintenance may change without notice.

# Impact

Updated on July 26, 2021

The following endpoint, which was originally mentioned as part of the scope of impact, won't be affected by the maintenance. You'll retrieve the narrowcast message status as usual during the maintenance.

The maintenance will affect:

  1. Message status won't be updated during maintenance
  2. Getting the number of messages sent on the previous day will be slower than usual

# Getting the number of messages sent on the previous day will be slower than usual

Updated on August 6, 2021

We've completed counting sent messages. Now you can also retrieve the number of sent messages from August 4, 2021 and August 5, 2021.

Updated on August 5, 2021

As of 15:00, August 5, 2021, the "Number of messages sent on the previous day" is not yet available due to the time required for counting after the maintenance. We will notify you again after counting is complete.

The number of messages sent on the previous day will be counted after the maintenance is complete. Therefore, you won't be able to get the number of messages sent on the previous day until several hours after the end of the maintenance.

If the status of the counting process (status property) is unready, message counting is still in progress. Wait a while before making a request again.

Maintenance Messaging API Options for corporate customers
Users can no longer add LIFF apps to Blockchain Service channels
2021/07/20

As announced on 17th June, 2021, after July 20, 2021, users can no longer add LIFF apps to Blockchain Service channels in the LINE Developers Console. LINE Login and LINE MINI App channels aren't affected by this change.

This table shows the channel types to which LIFF apps can be added, before and after the change.

Item Before change After change (Current state)
Channel type

# Date of change

July 20, 2021

# Impact

LIFF apps that have already been added to a Blockchain Service channel will continue to work after the specification change but will be deprecated with these caveats:

  • Unable to support LIFF functional enhancements.
  • Open to the possibility that LIFF apps may not be available in the future.

In order to continue using all the features of LIFF without any restrictions, migrate your LIFF app from the Blockchain Service channel to a LINE Login channel by following the instructions in Migration to LINE Login channel.

# Migration to LINE Login channel

To continue using LIFF apps that have already been added to a Blockchain Service channel without any restrictions, add the LIFF app to a LINE Login channel.

If you add the LIFF app to another channel, the LIFF ID will be reissued. These points must be noted:

  • If you are using LIFF v2, change the LIFF ID specified in liff.init().
  • The LIFF URL for launching LIFF (e.g. https://liff.line.me/1234567890-AbcdEfgh) will change.

For more information, see Adding a LIFF app to your channel in the LIFF documentation.

We appreciate your patience and apologize for any inconvenience this may cause.

LIFF LINE Developers Console LINE Blockchain Platform
List of available LINE emojis with Messaging API has been changed for easier viewing
2021/07/19

The list of available LINE emojis with Messaging API has been changed from a PDF file to a web page for easier viewing. For more information, see List of available LINE emojis in the Messaging API documentation.

Specify the product ID and emoji ID in the text message object

You can send a LINE emoji to a user by specifying the product ID and emoji ID of the LINE emoji you want to use in the emojis.productId and emojis.emojiId properties of the text message object. For details on how to send sticker messages, see Sending messages in the Messaging API documentation.

Messaging API
Auto login will take precedence over SSO login for LINE Login
2021/07/12

From July 15, 2021, auto login will take precedence in an environment where both auto login and Single Sign On login (hereafter called SSO login) are enabled for LINE Login.

# Prioritization of LINE Login authentication methods

For web app integrated LINE Login, users can use one of the following authentication methods:

Authentication method Description
Auto login Log in without user operation. The LINE Login screen or the confirmation screen is not displayed
Log in with email address Log in by entering an email address and password on the LINE Login screen
Log in with QR code Log in by scanning a QR code displayed on the LINE Login screen using the QR code reader on the LINE app for smartphones
Single Sign On (SSO) login Log in by clicking the login button on the confirmation screen with the message "Log in with the following account"

In the past, when users tried to login via LINE Login using LINE's smartphone app, in an environment where both auto login and SSO login were enabled, SSO login took precedence over auto login.

Since it has been confirmed that SSO login fails on some smartphone devices in case an auto login cookie is present, the prioritization of LINE Login authentication methods will be changed as follows:

Item Before change After change
Prioritization SSO login takes precedence Auto login takes precedence

From now on, auto login will take precedence in an environment where both auto login and SSO login are enabled.

# Impact

As a result of this change, when users try to log in via LINE Login using LINE's smartphone app, in an environment where both auto login and SSO login are enabled, the following SSO confirmation screen will not be displayed and users will not be able to select the login user.

SSO confirmation screen will not be displayed and users will not be able to select the login user

If you want to allow users to log in via SSO login instead of auto login, you can disable auto login in iOS by adding a specific query parameter (disable_ios_auto_login) to the authorization URL when Authenticating users and making authorization requests. We are planning to provide the same query parameter for Android in the future. The timing of the provision of this feature will be announced as soon as it is decided.

For more information, see LINE Login authentication methods and User authentication.

# Scheduled date of specification change

July 15, 2021

The content and date of the specification change is subject to change without notice.

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

LINE Login
LIFF v2.12.0 released
2021/07/12

We've released LIFF v2.12.0.

In this update, only the internal behavior of the SDK has been changed. There is no change in functionality.

If you're using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), it will automatically update to v2.12.0.

If you're using the npm package, you can upgrade to v2.12.0 by running npm install @line/liff@2.12.0 or yarn add @line/liff@2.12.0.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

LIFF LINE MINI App
A list of services provided by providers can now be published
2021/07/06

Provider page is a list of the various services offered by the Provider on the LINE Platform. Providers can display the services they offer, such as LINE Official Account (Messaging API), LINE MINI App and LINE Login, on the provider page.

provider page sample

Only certified providers can configure and publish provider pages

Only certified providers can configure and publish provider pages. For more information on certified providers, see Certified provider.

For more information, see Provider page under "Options for corporate customers".

LINE Developers Console
[Resolved] Notice about service outage for the Messaging API
2021/07/06

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

June 30, 2021 from around 12:00 - around 12:12 (UTC+9)

# Cause of the outage

Outage caused by server failures and software malfunctions

# Impact

# Details

During the above time period, messages may not have been actually sent in some requests to the endpoints that succeeded and returned a status code 200.

Due to this outage, the messages that weren't properly sent even if the API requests succeeded, won't be counted as the LINE Official Account usage fees and the "number of sent messages" that can be confirmed in some way such as the Get number of sent push messages endpoint.

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

Outage Report Messaging API
We have set a limit on the number of concurrent endpoint operations for creating audience for uploading user IDs/adding user IDs
2021/07/05

As announced on June 21, 2021, we have set a limit on the number of concurrent endpoint operations for creating audience for uploading User IDs and adding user IDs to an audience, for the Messaging API, effective from July 5, 2021. If you're using the target endpoints, be sure to check the ensuing impact of this limit.

Audience is used to send narrowcast messages

An audience is used to send a narrowcast message. For more information, see Sending messages to multiple users via attribute data or retargeting (narrowcast messages) in the Messaging API documentation.

# Limit on the number of concurrent operations

We have set a limit of 10 concurrent endpoint operations per audience ID (audienceGroupId), for creating an audience for uploading user IDs and adding user IDs to an audience.

Item Before change After change
Maximum number of concurrent operations No limit 10

There is no change on the rate limit of the target endpoints. For more information, see Limit on the number of concurrent operations.

# Target endpoints

The total number of requests processed concurrently by the above endpoints is counted as the number of concurrent operations.

# Impact

Requests that exceed the limit on the number of concurrent operations will return an error with status code 429 Too Many Requests.

If your implementation makes frequent requests to the target endpoint, such as creating an audience for every user ID, change your implementation so that it takes into account the limit on the number of concurrent operations.

If you've received an error, wait a while before making a request again.

You can check the number of requests being processed with the jobs property of the following endpoint response. If the status of a job (jobs[].jobStatus property) is waiting to run (QUEUED) or running (WORKING), it will be counted as an operation.

# Date of specification change

July 5, 2021

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

Messaging API
[Resolved/Updated] Notice about service outage for the Messaging API
2021/07/01
Updated on August 11, 2021

We've updated the Cause of the outage.

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

June 30, 2021 from around 12:00 - around 12:12 (UTC+9)

# Cause of the outage

Outage caused by a connection setting change on our cache server

For more information about details of the cause of the outage and measures to prevent recurrence, see Notice regarding erroneously displayed messages on LINE Official Account (opens new window) in Security & Privacy.

# Impact

This outage affected the sending of only certain messages

Of the endpoints related to sending messages, Send reply message, Send narrowcast message, and Send broadcast message weren't affected by the outage.

Messages sent from the LINE Official Account Manager (opens new window) and the chat function of the LINE Official Account weren't affected either.

# Details

During the above time period, a failure occurred in some requests where messages sent from a specific bot (bot A) were displayed in the chat room of another bot (bot B) of the recipient user's LINE app. The messages weren't sent to anyone other than the recipient user.

We have already unsent the messages that were displayed in error. Canceled messages will not be charged.

unsend message

The number of bots affected by this outage is very limited, and we will be contacting the administrators of the affected bots (bot A and bot B) individually.

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

Outage Report Messaging API
Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification has been deleted
2021/07/01

As announced on 31st May, 2021, Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification has been removed at the end of June 2021.

For more information on the current URL specifications for LIFF apps and LINE MINI Apps, see Opening LIFF apps in the LIFF documentation.

LIFF LINE MINI App
[Resolved] Notice about service outage for the Messaging API
2021/06/29

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

  • June 28, 2021 around 18:07 - around 18:08 (UTC+9)
  • June 28, 2021 around 20:32 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

During the stated date and time, some requests may not have been processed properly, resulting in an error with status code 5xx.

# Retrying a failed API request

In some APIs, you can safely retry a request while preventing the same request from being accepted in duplicate by using a retry key (X-Line-Retry-Key) when an error with status code 5xx occurs or when the request times out.

For more information, see Retrying a failed API request and APIs for which retry keys are available in the LIFF documentation.

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

Outage Report Messaging API
[Resolved] Notice about service outage for the Messaging API
2021/06/24

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

  1. June 24, 2021 around 13:05 - 13:08 (UTC+9)
  2. June 24, 2021 around 13:05 - 13:44 (UTC+9)

# Cause of the outage

Server failure

# Impact

  1. All endpoints provided by the Messaging API
  2. Sending webhook events

# Details

During period 1, requests to the endpoints provided by the Messaging API couldn't be processed properly.

During period 2, webhook events may have been delayed.

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

Outage Report Messaging API
We've released LIFF v2.11.1
2021/06/24

We've released LIFF v2.11.1.

In LIFF v2.11.1, this bug has been fixed.

# We fixed the bug that caused URL fragments to be URL-encoded after the LIFF app is initialized

In LIFF v2.11.0, when you access LIFF URLs containing URL fragments (e.g. #url-fragment), there was a bug that caused the URL fragments to be URL-encoded after the LIFF app is initialized (after liff.init() is executed).

We've fixed this bug in LIFF v2.11.1 so that even after liff.init() URL fragments aren't URL-encoded.

# Example of URL fragment after liff.init()

In the LIFF v2.11.0 example below, the slash (/) in the URL fragment (#url/fragment) is URL-encoded (%2F).

LIFF version LIFF URL URL after liff.init()
v2.11.0 https://liff.line.me/{liffId}#url/fragment https://liff.line.me/{liffId}#url%2Ffragment
v2.11.1 https://liff.line.me/{liffId}#url/fragment https://liff.line.me/{liffId}#url/fragment
We recommend updating to LIFF v2.11.1

In LIFF v2.11.0 of the LIFF app, the bug occurs regardless of browser type (LIFF browser, LINE's in-app browser, external browser). The same bug also occurs when you directly access not only a LIFF URL (e.g. https://liff.line.me/{liffId}/#url/fragment), but also an endpoint URL (e.g. https://example.com/#url/fragment).

If you're using v2.11.0, we recommend that you update to v2.11.1 to avoid unintended behaviors.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app.

LIFF LINE MINI App
Reminder: Mark-as-Read API maintenance notice
2021/06/22

As announced on June 9, 2021, maintenance will be performed on the Mark-as-Read API, which marks messages from users as "Read". We sincerely apologize for any inconvenience that this may cause and thank you for your understanding.

Using the Mark-as-Read API requires an application

Only corporate users who have submitted the required applications can use the Mark-as-Read API.

For more informations, see Overview in the Options for corporate customers documentation.

# Date and time of maintenance

June 24, 2021 0:00 - 7:00 (UTC+9)

Note that the end time of maintenance may change without notice.

# Impact

During the stated period, LINE Official Accounts using the Mark-as-Read API won't be able to mark messages from users as read.

Requests for the Mark-as-Read API will return an error with status code 503. Requests with errors will be marked as read by retrying after maintenance is complete.

Maintenance Options for corporate customers Messaging API
You can now easily switch between multiple rich menus
2021/06/21

A new feature to switch between rich menus has been added to the Messaging API.

Rich menu aliases make it easy to switch between multiple rich menus like switching tabs. For more information, see Switching between multiple rich menus in the Messaging API documentation.

Rich menu aliases make it easy to switch between multiple rich menus like switching tabs.

These new endpoints, actions, and objects have been added along with the feature to switch between rich menus.

# Endpoints

# Other

Messaging API
We'll set a limit on the number of concurrent endpoint operations for creating audience for uploading user IDs/adding user IDs
2021/06/21

We'll set a limit on the number of concurrent endpoint operations for creating audience for uploading User IDs and adding user IDs to an audience, for the Messaging API. If you're using the target endpoints, be sure to check the ensuing impact of this limit.

Audience is used to send narrowcast messages

An audience is used to send a narrowcast message. For more information, see Sending messages to multiple users via attribute data or retargeting (narrowcast messages) in the Messaging API documentation.

# Limit on the number of concurrent operations

We'll set a limit of 10 concurrent endpoint operations per audience ID (audienceGroupId), for creating an audience for uploading user IDs and adding user IDs to an audience.

Item Before change After change
Number of concurrent operations No limit 10

There is no change on the rate limit of the target endpoints.

# Target endpoints

The number of concurrent operations is shared by all of the above endpoints, not per endpoint.

# Impact

Requests that exceed the limit on the number of concurrent operations will return an error with status code429 Too Many Requests.

If your implementation makes frequent requests to the target endpoint, such as creating an audience for every user ID, change your implementation so that it takes into account the limit on the number of concurrent operations.

If you've received an error, wait a while before making a request again.

You can check the number of requests being processed with the jobs property of the following endpoint response. If the status of a job (jobs[].jobStatus property) is waiting to run (QUEUED) or running (WORKING), it will be counted as the number of concurrent operations.

# Scheduled date of specification change

July 5, 2021

The content and date of the specification change is subject to change without notice.

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

Messaging API
Users can no longer add LIFF apps to Blockchain Service channels
2021/06/17

After July 20, 2021, users will no longer be able to add LIFF apps to Blockchain Service channels in the LINE Developers Console. LINE Login and LINE MINI App channels are not affected by this change.

This table shows the channel types to which LIFF apps can be added, before and after the change.

Item Before change After change
Channel type

# Scheduled date of change

July 20, 2021

# Impact

LIFF apps that have already been added to a Blockchain Service channel will continue to work after the specification change, but will be deprecated with these restrictions:

  • Unable to support LIFF functional enhancements.
  • There is a possibility that LIFF apps will not be available in the future.

In order to continue using all the features of LIFF without any restrictions, migrate your LIFF app from the Blockchain Service channel to a LINE Login channel by following the instructions in Migration to LINE Login channel.

# Migration to LINE Login channel

To continue using LIFF apps that have already been added to a Blockchain Service channel without any restrictions, add the LIFF app to a LINE Login channel.

If you add the LIFF app to another channel, the LIFF ID will be re-issued. These points must be noted:

  • If you are using LIFF v2, change the LIFF ID specified in liff.init().
  • The LIFF URL for launching LIFF (e.g. https://liff.line.me/1234567890-AbcdEfgh) will change.

For more information, see Adding a LIFF app to your channel in the LIFF documentation.

We appreciate your patience and apologize for any inconvenience this may cause.

LIFF LINE Developers Console LINE Blockchain Platform
Tutorial on how to create a sample bot for Messaging API using Node.js and Heroku is now available
2021/06/17

We have published a tutorial on how to create a Messaging API sample bot with Node.js and deploy it using Heroku.

This tutorial practically demonstrates how to set up an auto-response to a user's message with the Messaging API. When you reach the end of the tutorial, you will be able to deploy an auto-response bot like this one.

Conversation with a sample bot

Please take this opportunity to learn how to use the Messaging API and create your own bots.

Messaging API
The APIs for converting MIDs to user IDs will be discontinued at the end of June, 2021
2021/06/15
This announcement is for those who have been using LINE Login v1

This news is only for users of LINE Login v1, which was discontinued in 2018. Developers who are using the latest version, LINE Login v2.1, or LINE Login v2.0 are not affected.

The APIs for converting MIDs to user IDs will be discontinued at the end of June 2021.

The target APIs were temporarily provided to LINE Login v1 developers due to the need to convert MIDs to user IDs during the transition from LINE Login v1 to LINE Login v2.0. For more information, see the news on February 28, 2018, LINE Login v1 to be discontinued.

# Target APIs

  • Convert MIDs to user IDs
  • Convert multiple MIDs at once

The documentation for these APIs is no longer available.

# Scheduled date of discontinuation

June 30, 2021

The date is subject to change without notice.

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

LINE Login Messaging API LINE Platform End of life
LIFF v2.11.0 released
2021/06/14

We've released LIFF v2.11.0.

In LIFF v2.11.0, these security improvements have been made.

# Credential information is now excluded from the primary redirect URL after liff.init()

For security reasons, URL fragments that contain credential information such as access tokens are now excluded from primary redirect URLs when liff.init() is resolved. Therefore, the primary redirect URL that doesn't contain credential information is processed as the current URL in the then() method of the method chain.

# Redirect example

If the LIFF URL is https://liff.line.me/{liffId}/path and the endpoint URL is https://example.com, you'll be redirected as follows:

When confidential information is excluded

Number Item URL
(1) LIFF URL https://liff.line.me/{liffId}/path
(2) Primary redirect URL https://example.com/?liff.state=path
#access_token=xxx&context_token=xxx&
feature_token=xxx&id_token=xxx&client_id=xxx
(3) URL after liff.init() https://example.com/?liff.state=path
(4) Secondary redirect URL https://example.com/path

# liff.init() sample code

Credential information is excluded within the liff.init().then() method.

console.log(window.location.href);
// https://example.com/?liff.state=path#access_token=xxx&context_token=xxx&feature_token=xxx&id_token=xxx&client_id=xxx

liff.init({liffId: myLiffId}).then(() => {
  console.log(window.location.href);
  // https://example.com/?liff.state=path
});
About using external logging tools like Google Analytics

To use an external logging tool such as Google Analytics, we recommend updating to LIFF v2.11.0 to better secure the credential information of users who access the LIFF app. Make sure to send a URL that doesn't contain credential information to external logging tools after liff.init() is executed.

liff.init({liffId: myLiffId}).then(() => {
    ga('send', 'pageview');
})

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app.

LIFF LINE MINI App
Icons in the LIFF app header will be visually enhanced from LINE 11.10.0 or later
2021/06/14

The LIFF app header design will be visually enhanced from LINE 11.10.0 or later.

All icon designs used in the LIFF header section, including the "close" button, "share" button, and "back" button, will change as follows:

LINE 11.9.x or earlier LINE 11.10.0 or later
Old LIFF header icon New LIFF header icon

# Applicable environments

The new icon designs will be applied in these environments.

Item Environment
LINE version v11.10.0 or later
Browser LIFF browser (Doesn't apply for LINE's in-app browser or external browser)
Screen size All screen sizes (Compact,Tall,Full)

This update is a design change only and doesn't affect existing features.

LIFF LINE MINI App
[Resolved] Notice about service outage for the Messaging API
2021/06/09

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

June 9, 2021 around 16:05 - around 16:55 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending text messages that include LINE emojis (emojis property)

# Details

During the above time period, requests to send text messages containing LINE emojis (emojis property) couldn't be processed correctly, resulting in an error with status code 40x.

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

Outage Report Messaging API
Mark-as-Read API maintenance notice
2021/06/09

Maintenance will be performed on the Mark-as-Read API, which marks messages from users as "Read". We sincerely apologize for any inconvenience that this may cause and thank you for your understanding.

Using the Mark-as-Read API requires an application

Only corporate users who have submitted the required applications can use the Mark-as-Read API.

For more informations, see Overview in the Options for corporate customers documentation.

# Date and time of maintenance

June 24, 2021 0:00 - 7:00 (UTC+9)

Note that the end time of maintenance may change without notice.

# Impact

During the stated period, LINE Official Accounts using the Mark-as-Read API won't be able to mark messages from users as read.

Requests for the Mark-as-Read API will return an error with status code 503. Requests with errors will be marked as read by retrying after maintenance is complete.

Maintenance Options for corporate customers Messaging API
We made a temporary fix for a bug which prevented content from being displayed correctly when returning to the previous page after a transition between LIFF apps
2021/05/31

In LINE or Safari on iOS 14.5.x or Safari 14.x on macOS, when users click the back button or return to the previous page after a transition between LIFF apps, the URL returned to the LIFF URL before the transition, but the screen remained the same or was blank.

The screen becoming blank when returning to the LIFF app before the transition between LIFF apps

Diagram of a blank screen when returning to the LIFF app before the transition between LIFF apps.

# Environment where the problem occurred

  • LINE and Safari on iOS 14.5.x
  • Safari 14.x on macOS

# Cause of the problem

The cause of this problem is a bug in Apple WebKit (opens new window).

We have already reported the issue to WebKit Bugzilla (opens new window) and requested them to investigate it, but as a temporary measure, we have fixed the problem by changing the way the LIFF server handles additional information in LIFF URLs.

# Temporary support

In response to this, we have changed the way the LIFF server handles additional information about LIFF URLs to avoid the problem.

Previously, all additional information in LIFF URLs, such as the path (/path), query parameters (?key=value), and URL fragment (#URL-fragment), were concatenated with the endpoint URL and redirected to the secondary redirect URL. As a result of this temporary fix, URL fragments among additional information in LIFF URLs will be excluded during redirects, only when the LIFF app is running on iOS 14.5 and Safari 14.x.

For environments other than iOS 14.5 and Safari 14.x, there is no change from the previous method of handling additional information in LIFF URLs.

No action is required on the LIFF app side

The temporary support is completed only on the LIFF server side, so there is no need to upgrade the LIFF SDK or modify the code in your LIFF apps.

Comparison of processing methods for additional information:

Comparison LIFF URL Endpoint URL Secondary redirect URL
Before bug fix https://liff.line.me/{liffId}
/path?key=value#URL-fragment		 https://example.com https://example.com
/path?key=value#URL-fragment
After bug fix https://liff.line.me/{liffId}
/path?key=value#URL-fragment		 https://example.com https://example.com
/path?key=value
If you want to include a URL fragment

Due to this temporary support, URL fragments included in the additional information in LIFF URLs will be excluded during redirects. However, if you directly access the endpoint URL that contains a URL fragment, the URL fragment will still be loaded as before.

If you want to use URL fragments during transitions between LIFF apps, configure your app so that end users will access the endpoint URL (e.g. https://example.com#URL-fragment) instead of the LIFF URL (e.g. https://liff.line.me/{liffId}#URL-fragment).

URL fragments can't be specified in Endpoint URL of the LINE Developers Console as before.

For more information about transitions between LIFF apps, see Opening a LIFF app from another LIFF app in the LIFF documentation.

LIFF LINE MINI App
[Method for converting additional information in the LIFF URL] settings deleted from LIFF channel on LINE Developers Console
2021/05/31

As announced on March 01, 2021, Replace (Backward compatibility mode) in Method for converting additional information in the LIFF URL has been discontinued on the LINE Developers Console.

Currently, because all LIFF and LINE MINI App URLs are opened with Concatenate, we've deleted the Method for converting additional information in the LIFF URL setting on the LINE Developers Console.

This deletion doesn't affect the operation of LIFF apps or LINE MINI Apps.

For Concatenate specifications, see Create a secondary redirect URL in the LIFF documentation.

The Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification, which was provided as a temporary measure to handle the discontinuation of Replace (Backward compatibility mode), will be removed at the end of June 2021.

LIFF LINE MINI App LINE Developers Console
You can now create audiences with the same name in the Messaging API
2021/05/27

Until now, Messaging API had a restriction that prevented you from reusing an existing audience name. This restriction has been removed.

For example, even if an audience named "AudienceGroupName_01" already exists, the removal of this restriction now allows you to create another audience with the same name. Each audience created can be distinguished by the audience ID passed in the response.

# Impacted endpoints

For more information on audiences, see Using audiences in the Messaging API documentation.

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

Messaging API
You can now send test messages from Flex Message Simulator
2021/05/20

Messaging API has a feature called Flex Message that can be written in JSON format to customize the layout. To make it easier for developers to try out Flex Messages, we introduced a new feature to send test messages with Flex Message Simulator.

To send a test message, go to Flex Message Simulator. Log in to Flex Message Simulator with the same LINE account that you have logged in to the LINE Developers Console.

On the top right corner, click the Send... button.

Send button shown on the top right corner of Flex Message Simulator

You'll see a "Send Message" popup, listing the LINE account you've logged in with as a destination by default.

About the account to log in to Flex Message Simulator

If the account you're logged in to the LINE Developers Console is a business account and it's not linked to a LINE account, the account won't be shown as a destination.

You also need to be friends with the Flex Message Simulator Official Account (opens new window) before you can receive test messages.

Popup showing the destination and a send button

To send a test Flex Message to this account, select the account and click the Send button. You should receive a sample Flex Message and a message indicating that it's a sample message in your LINE Account.

Test Flex Message

You can also add alternative destinations by clicking Register destination in the popup.

Popup showing the register destination button

Scan the displayed QR code with the LINE app of an account you'd like to register as a destination. You'll receive a verification code on your LINE app.

Popup display QR code

Once you enter and confirm the verification code in the Flex Message Simulator, your alternative destination will be registered.

Number of alternative destinations you can register

You can only register 1 alternative destination at a time. If you have already registered an alternative destination and register another one, the previous destination will be unregistered.

There are no special applications that developers need to submit to use this feature.

Flex Message Simulator Messaging API
LIFF v2.10.0 released
2021/05/17

We've released LIFF v2.10.0.

In LIFF v2.10.0, these bugs have been fixed.

# We fixed the bug that caused old context tokens to be referenced when initializing the LIFF app in external browsers

When users log in to a LIFF app using LIFF v2.9.1 or earlier in an external browser, old context tokens stored in the localStorage when the LIFF app is initialized (when liff.init() method is executed) in previous sessions are referenced, causing unexpected behaviors, but we fixed this bug.

What is a context token?

A context token holds information about the environment in which the LIFF app is launched, such as screen size and user ID, which can be retrieved using the liff.getContext() method. When your LIFF app is initialized (the liff.init() method is executed), it is stored as a context key in the browser's localStorage.

# Updated the timing of checking access token expiration

When your LIFF app is initialized (when liff.init() is executed), the expiration of the access token generated in the previous session is checked, and if it has expired, the context token is discarded. However, in LIFF v2.9.1 or earlier, this expiration check takes place at the tail end of the LIFF app initialization, so old tokens that haven't been discarded are referenced when the initialization takes place, leading to unexpected behaviors.

In LIFF v2.10.0, the access token expiration check takes place at the beginning of the LIFF app initialization, ensuring that initialization takes place after the old context tokens have been discarded.

There is no guarantee that the information obtained through the liff.getContext() method is up-to-date

Context tokens are discarded when access tokens expire. Even in LIFF v2.10.0, as long as the access token hasn't expired, the context information you can obtain through the liff.getContext() method doesn't change. Therefore, there is no guarantee that the information obtained through the liff.getContext() method is always up-to-date.

# When to discard context tokens for each version

Below is a comparison between LIFF v2.9.1 or earlier and LIFF v2.10.0 of when access token expiration is checked and context tokens are discarded.

LIFF
version		 Flow of storing context tokens in the localStorage
v2.9.1 or earlier Previous timing of when context tokens were discarded
v2.10.0 Timing of when context tokens are discarded in v2.10.0 or later
In the case of LIFF browser and LINE's in-app browser

LIFF browser and LINE's in-app browser aren't affected by this version update.

For details on information stored by context tokens, see liff.getContext() in the LIFF API reference.

LIFF
[Resolved] Notice about LINE Developers Console notification center failure
2021/05/13

We'd like to inform you about a service failure regarding the LINE Developers Console. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of failure

Around April 16, 2021 - May 12, 2021 around 17:17 (UTC+9)

# Cause of the failure

Problems with batch execution

# Impact

LINE Developers Console notification center

# Details

During the stated date and time, users who had notification email settings enabled in the notification center of the LINE Developers Console didn't receive notification emails.

As a result of the recovery work, notification emails that were supposed to be sent during stated duration were sent all at once to users on May 12, 2021. Users who hadn't configured their settings to receive notification emails were not affected.

The issue is now resolved and notification emails are being sent normally.

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

LINE Developers Console Outage Report
TLS 1.0 and TLS 1.1 support for LINE API will be discontinued at the end of August 2021
2021/05/13

TLS 1.0 and TLS 1.1 support for LINE API will be discontinued at the end of August 2021.

# Domain names of the target LINE API

  • api.line.me
  • api-data.line.me

All APIs using the domain names above are targeted without exception.

# Supported SSL/TLS protocol versions

We no longer support TLS 1.0 and TLS 1.1.

Protocol version By the end of August 2021 After September 2021
TLS 1.3 ✅ ✅
TLS 1.2 ✅ ✅
TLS 1.1 ✅ ❌
TLS 1.0 ✅ ❌
SSL 3.0 ❌ ❌
SSL 2.0 ❌ ❌

# Estimated end-of-support date

August 31, 2021

The date and time are subject to change without notice.

# Impact

If the source of requests to the LINE API does not support TLS 1.2 or higher, you will no longer be able to use the LINE API. If your environment is TLS 1.1 or lower, please upgrade your OS, OpenSSL, etc. so that your app or server can continue to communicate using TLS 1.2 or higher.

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

LINE Platform SSL/TLS End of life
The procedure for issuing an assertion signing key has changed
2021/05/12

As announced on April 1, 2021, the procedure for creating an Assertion Signing Key has changed.

How it affects developers using Assertion Signing Keys

This change affects developers who issue and use Assertion Signing Keys on these channels. Review the details of the changes.

  • LINE Login
  • Messaging API
  • LINE MINI App
  • Blockchain Service

# Overview

These changes have been made to the issuing procedure for safer use of the Assertion Signing Key.

Before change After change (Current state)
Issuing procedure
  1. Developer clicks the Issue button in the LINE Developers Console.
  2. A key pair for the Assertion Signing Key is generated on LINE’s server side.
  3. Developer downloads and saves the private key.
    * We only display the private key once when issued. LINE only stores the public key. We don't store the private key.
  1. Developer generates an Assertion Signing Key pair in their environment (PC or server).
  2. Developer clicks the Assertion Signing Key's Register a public key button in the LINE Developers Console.
  3. Developer pastes public key into the form in the LINE Developers Console and clicks the Register button.
  4. Once developer succeeds in registering the public key, kid will be displayed in the LINE Developers Console.
Instructions for use Developer uses private key when issuing a Channel access token v2.1. No change

# Diagram for issuing a channel access token v2.1

This diagram shows these three steps:

Procedure for issuing channel access token

For more information on the procedure of creating an Assertion Signing Key after the change, see Create an Assertion Signing Key in the Messaging API documentation.

You can continue using Assertion Signing Keys previously issued in the LINE Developers Console even though the procedure has changed.

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

LINE Developers Console LINE Login Messaging API LINE MINI App LINE Blockchain Platform
[Resolved] Notice about service outage for the Messaging API
2021/04/27

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

April 27, 2021 around 16:56 - around 17:25 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

During the stated date and time, some requests may not have been processed properly, resulting in an error with status code 500.

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

Outage Report Messaging API
LIFF v2.9.1 released
2021/04/27

In LIFF v2.9.1, these bugs have been fixed, but there are no changes to the features.

# We fixed the bug that occurs when using the npm package of the LIFF SDK

When attempting to use the npm package of the LIFF SDK on TypeScript, an error had occured during compilation, but this bug has been fixed. In LIFF v2.9.1, there is no issue with compilation, even when using TypeScript.

This fix applies to both the npm version and the CDN version of the LIFF SDK.

For more information on the npm package of the LIFF SDK, see Use the npm package.

How to handle compilation errors

We recommend upgrading to LIFF v2.9.1 as a workaround for compilation errors when using TypeScript, but if you can't, use this method to resolve the compilation errors:

If you enable the skipLibCheck (opens new window) option using TypeScript setting files such as tsconfig.json, compilation errors won't occur.


If you're using the CDN edge path(https://static.line-scdn.net/liff/edge/2/sdk.js), your LIFF will be automatically upgraded to v2.9.1.

If you're using the npm package, your LIFF will be upgraded to v2.9.1 if you execute either npm install @line/liff@2.9.1 or yarn add @line/liff@2.9.1.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app.

LIFF
[Resolved] Notice about service outage for the Messaging API
2021/04/23

We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved.

We sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

April 22, 2021 around 17:01 - around 17:51 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

During the stated date and time, some requests may not have been processed properly, resulting in an error with status code 500.

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

Outage Report Messaging API
Provider and Messaging API channel creation flow updated
2021/04/23

We updated the process to create a provider and a Messaging API channel on the LINE Developers Console to improve the developer experience.

# What's changed?

We've made these changes:

# Added a guide text when creating a provider

To make it easy for developers to understand the definition of a provider, we've added a guide text explaining the definition of a provider to the pop-up displayed when creating a new provider.

Pop-up to create a new provider with the definition of a provider

For instructions on how to create a new provider, see Creating a provider in the LINE Developers Console documentation.

# Updated the Messaging API channel creation flow

Before the update, the relationship between a provider, the Messaging API channels belonging to the provider, and their LINE Official Accounts was unclear to some developers. This lead to some developers creating Messaging API channels under unintended providers. To resolve this issue, we've updated the process of creating a Messaging API channel.

When a developer creates a Messaging API channel, a pop-up appears, showing the names of the channel, LINE Official Account, the provider, and some precautions.

Pop-up showing names of the channel, Official Account, and the provider

Once the developer clicks OK, a secrecy of communication agreement is displayed.

For instructions on how to create a new Messaging API channel, see Creating a channel in the LINE Developers Console documentation.

Messaging API LINE Developers Console
[Resolved] Notice about service outage for Mark-as-Read API
2021/04/22
Updated on April 23, 2021

We've updated the Date and time of outage, Cause of the outage and Details.

We'd like to inform you about a service outage regarding the Mark-as-Read API which marks messages from users as "Read". The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

Use of the Mark-as-Read API requires an application

Only corporate users who have submitted the required applications can use the Mark-as-Read API.

For more information, see Overview in the Options for corporate customers documentation.

# Date and time of outage

April 22, 2021 around 17:01 - around 18:34 (UTC+9)

# Cause of the outage

Server failure

# Impact

The request process of Mark-as-Read API

# Details

During the stated date and time, the Mark-as-Read API might not be processed properly and cause errors with status code 400.

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

Outage Report Options for corporate customers
[Resolved/Updated] Notice about service outage for LINE Login and LIFF/LINE MINI App
2021/04/16
Updated on April 19, 2021

We've updated the Cause of the outage and Details.

We'd like to inform you about a service outage regarding LINE Login, LIFF, and LINE MINI App. The issue has now been resolved, but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

April 16, 2021 around 17:54 - around 18:35 (UTC+9)

# Cause of the outage

Server failure

# Impact

  • LINE Login
  • LIFF/LINE MINI App

# Details

Due to this outage, some features of LINE Login and LIFF/LINE MINI App may not have been available during the above period.

We have confirmed that the following events have occurred.

  • LINE Login didn't work per usual
  • LIFF/LINE MINI Apps were inaccessible
  • LIFF API didn't work per usual

LINE will continue to improve the quality of its services to prevent future outages.

Thank you for your understanding.

Outage Report LINE Login LIFF LINE MINI App
[Resolved] Notice about outage for sending service messages in LINE MINI Apps
2021/04/15

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

# Date and time of outage

  • April 15, 2021 around 12:04 (UTC+9)
  • April 15, 2021 around 15:22 - around 16:23 (UTC+9)

# Cause of the outage

Server failure

# Impact

LINE MINI App's Sending service messages endpoint

# Details

In some LINE MINI Apps, when sending a request to the endpoint, a response with a status code 5xx error was returned. This has now been fixed and service messages can be sent normally.

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

Outage Report LINE MINI App
[Resolved] Notice about service outage for sending webhook events
2021/04/15

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

April 15, 2021 around 12:05 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending webhook events

# Details

In some channels, webhook events may not have been sent properly to the bot server.

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

Outage Report Messaging API
LIFF v2.9.0 released
2021/04/13

We've released LIFF v2.9.0.

In this update, only the internal behavior of the SDK has been changed. There is no change in functionality.

If you're using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), it will automatically update to v2.9.0.

If you're using the npm package, you can upgrade to v2.9.0 by running npm install @line/liff@2.9.0 or yarn add @line/liff@2.9.0.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

LIFF
[Resolved/Updated] Notice about service outage for LINE Platform
2021/04/12
Updated on April 13, 2021

We've updated the main impacts per product under Details.

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

# Date and time of outage

April 12, 2021 around 15:10 - 16:01 (UTC+9)

# Cause of the outage

Facility failure

# Impact

  • Messaging API
  • LINE Login
  • LIFF
  • Other general functions provided by the LINE Platform

# Details

Due to a facility failure, all products provided by LINE Developers may not have been available during the above period.

These are the main impacts per product:

# Messaging API

  • API request succeeded (HTTP status code 200 returned), but messages sent via the Messaging API were significantly delayed or didn't send per usual.
  • Webhook event was significantly delayed or didn't send per usual.

Due to this outage, messages that weren't properly sent, even if the API request was successful, won't count towards the "number of sent messages" that can be confirmed in some way such as the Get number of sent push messages endpoint, nor will there be any LINE Official Account usage fees.

# LINE Login

  • There were instances where LINE Login didn't work per usual.

# LIFF/LINE MINI App

  • There were instances where LIFF/LINE MINI App couldn't be used per usual.
  • There were instances where liff.shareTargetPicker()couldn't be used per usual.
  • There were instances where service messages weren't sent per usual.

# LINE Developers Console

  • There were instances where Messaging API channels couldn't be created.

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

Outage Report LINE Platform
LINE Login now supports PKCE
2021/04/09

We now support PKCE for LINE Login, which will make the authorization flow of LINE Login v2.1 more secure.

# What is PKCE

PKCE (Proof Key for Code Exchange) is an OAuth2.0 extension specification defined in RFC7636 (opens new window), intended to combat authorization code interception attacks.

The OAuth2.0 authorization flow that doesn't use PKCE is vulnerable to user-specific access tokens being stolen if a malicious app somehow gets the custom URI containing the authorization code. By implementing the PKCE authorization flow into web apps that incorporate LINE Login, you can further improve the security of LINE Login v2.1 and prevent authorization code interception attacks.

# Benefits of implementing PKCE for LINE Login

The behavior against authorization code interception attacks differs depending on whether PKCE is implemented or not in the web app that uses LINE Login. We recommend implementing PKCE to make your web app more secure.

Without PKCE implemented With PKCE implemented
If a malicious app somehow gets a callback URL containing an authorization code, it can steal an access token.
Authorization code interception attack when PKCE isn't implemented		 Even if a malicious application steals the information passed during the redirection, it can be checked against a unique code_challenge to prevent access tokens from being stolen.
Authorization code interception attack when PKCE is implemented
Another benefit of implementing PKCE

If you access a web app that incorporates PKCE-implemented LINE Login from the Yahoo! JAPAN app (opens new window), the auto login function that lets you skip the login process using your email address and password will be enabled.

Auto login from the Yahoo! JAPAN app

For more information on how to implement PKCE, see Implement PKCE for LINE Login in the LINE Login documentation.

LINE Login
The LINE API Use Case site is now available in English
2021/04/08

The LINE API Use Case (opens new window) site, which introduces technical information about LINE APIs, use cases, client cases, demo apps, and more, is now available in English.

LINE offers a variety of APIs that let companies and external developers connect with our various services. Prior to using the LINE Developers site, which explains the API specifications and development methods for developers, you can refer to the LINE API Use Case site to discover what you can do with those APIs in the first place.

On the LINE API Use Case site, you will find use cases, client case studies, and demo apps that utilize LINE APIs in categories such as "reservations," "table orders," "membership cards," "information distribution for local governments," and "reservation phone calls." You can refer to actual use cases and experience the behavior of each API in an easy-to-understand manner.

These are the LINE APIs provided on the LINE API Use Case site:

  • Messaging API
  • LINE Login
  • LINE Front-end Framework (LIFF) / LINE MINI App
  • LINE Pay API
  • LINE Social Plugins
  • CLOVA Chatbot (Coming soon)
  • CLOVA OCR (Coming soon)

You can access the LINE API Use Case site by clicking Use Case in the More drop-down menu.

Use Case option in the More drop-down menu.

LINE will continue to strengthen its cooperation with external companies, partners, and developers in order to create a stronger relationship and shorten the distance between users and various information, services, and goods.

LINE Platform
[Resolved] Notice about service outage for LINE Login
2021/04/07

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

# Date and time of outage

April 3, 2021 around 10:00 - April 6, 2021 around 12:05 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

In some requests, an error with HTTP status code 400 occurred and the request was not processed properly, even though the request content was appropriate.

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

Outage Report LINE Login
More stickers are available with Messaging API
2021/04/07

We have greatly increased the number of stickers available with Messaging API, and the sticker list has been changed from a PDF file to a web page for easier viewing. For more information, see List of available stickers in the Messaging API documentation.

Specify the package ID and sticker ID in the sticker message object

You can send a sticker to a user by specifying the package ID and sticker ID of the sticker you want to use in the packageId and stickerId properties of the sticker message object. For details on how to send sticker messages, see Sending messages in the Messaging API documentation.

Messaging API
LIFF v1 is deprecated
2021/04/05

We announced on October 16, 2019 that LIFF v1 will be deprecated. As of April 1, 2021, LIFF v1 is deprecated.

What does "deprecated" mean?

"Deprecated" means that the feature or capability will be removed in a future MAJOR release. During the deprecation period, we don't provide bug fixes or security improvements to maintain the existing functionality that we provide during the maintenance window. For example, if there's a bug or security issue in LIFF v1, the SDK and API won't be updated. The deprecation period is intended to give developers time to plan and update the SDK before LIFF v1 reaches end-of-life. For more information about LIFF's MAJOR release schedule, see The LIFF MAJOR version status in the LIFF documentation.

# Impact

LIFF v1 features will continue to work until they are discontinued, but we recommend migrating to LIFF v2.

# Required action

# If you're currently using LIFF v1

You must migrate to LIFF v2 before LIFF v1 is deprecated. For more information on LIFF migration, see Migrate to LIFF v2.

# If you're not using LIFF v1

No action is required, but new use of LIFF v1 isn't recommended.

# Migrate to LIFF v2

The LIFF version is determined by the LIFF SDK version. If the existing LIFF app uses LIFF v1, you can move to LIFF v2 by changing the SDK loaded by the LIFF app and verifying that it works correctly.

# Difference between LIFF v1 and LIFF v2

LIFF v1 and LIFF v2 have different initialization methods and specs for LIFF apps.

# Minimum operating environment difference

The minimum operating environment for opening the LIFF app in the LIFF browser is different between LIFF v2 and LIFF v1. See this table for details:

LIFF SDK version Minimum operating environment Details
LIFF v1
  • iOS: iOS 8 or later
  • Android: 4.2 or later
  • LINE: v7.14 or later
 Operating environment in the LIFF API reference
LIFF v2
  • iOS: iOS 12.0 or later
  • Android: 5.0 or later
  • LINE: v9.14.0 or later
 Recommended operating environment in the LIFF documentation
Note

Even if you're using a version later than the minimum operating requirements, it may not work or the screen may not be displayed properly depending on the functions and settings.

# Installation method difference

LIFF v1 was installed by CDN, but LIFF v2 can be installed by npm or CDN. See this table for details:

LIFF SDK version LIFF SDK installation method Details
LIFF v1 Specify CDN path Integrating the LIFF SDK in the LIFF documentation
LIFF v2
  • Specify CDN path
  • Use the npm package
 Integrating the LIFF SDK with the LIFF app in the LIFF documentation
# Initialization method difference

LIFF v1 calls liff.init() without arguments, but LIFF v2 must pass the liffId property and the LIFF ID of the LIFF app as its value when calling liff.init().

How to initialize LIFF v1:

liff.init(
  data => {
    // Now you can call LIFF API
    const userId = data.context.userId;
  },
  err => {
    // LIFF initialization failed
  }
);

How to initialize LIFF v2:

// Using a Promise object
liff
  .init({
    liffId: "123456-abcedfg" // Use own liffId
  })
  .then(() => {
    // Start to use liff's api
  })
  .catch((err) => {
    // Error happens during initialization
    console.log(err.code, err.message);
  });

// Using a callback
liff.init({ liffId: "123456-abcedfg" }, successCallback, errorCallback);

See this table for different initialization methods and related documentation:

LIFF SDK version How to initialize the LIFF app Details and code examples
LIFF v1 Call liff.init() liff.init() in the LIFF API reference
LIFF v2 Pass the liffId property and the LIFF ID of the LIFF app as its value when calling liff.init() liff.init() in the LIFF v2 API reference
# Functionality difference

LIFF v2 has more features than LIFF v1.

  1. The LIFF app can run in an external browser

In LIFF v1, the LIFF app only worked in the LIFF browser. With LIFF v2, it also works with external browsers. Therefore, you can develop LIFF apps in the same development environment as general web apps.

  1. Available LIFF methods

LIFF v2 provides more LIFF methods than LIFF v1. This list shows the available LIFF v2 methods:

For code examples and details of each method, see LIFF v2 API reference.

# Resources to help with migration

The LIFF starter application (opens new window) is useful for checking the specs and development methods of LIFF v2. For more information, see Trying the LIFF starter app in the LIFF documentation.

LIFF Deprecated Life cycle
LINE API Status site for checking service availability opened
2021/04/05

We've opened the LINE API Status (opens new window) site for checking the service availability and outage status of LINE APIs.

# What is LINE API Status?

LINE API Status is a site through which you can check the service availability and outage status of APIs and services that LINE provides. Service availability and outage status information is provided in English.

You can get the ATOM or RSS feed by clicking SUBSCRIBE TO UPDATES on LINE API Status.

A subscribe to updates button that lets you subscribe to Atom Feed or RSS Feed

# Display when operation is stable

When there is no outage and operation is stable, All Systems Operational is displayed.

Display when operation is stable

# Display when outage occurs

When an outage occurs, the following is displayed regarding the service undergoing outage and the occurrence of outage:

Display when outage occurs

Outage status is also displayed through this pop-up on the LINE Developers site.

A pop-up message alerting the reader of an outage report in the Messaging API.

# Services covered by LINE API Status

LINE API Status covers these services:

  • Messaging API
    • API
    • Webhook
  • LINE Developers
    • LINE Developers site
    • LINE Developers Console

Currently, LINE API Status doesn't cover the LINE app and services other than the above (such as LINE MINI App, LIFF, and LINE Pay).

# Accessing LINE API Status

You can access LINE API Status by clicking LINE API Status (opens new window) on the More dropdown menu.

LINE API Status on the more dropdown menu

On the information on LINE API Status

LINE will provide information on outage status through LINE API Status, but this doesn't guarantee immediate, accurate, or comprehensive information. We will continue to inform you of the details of the outage, such as the cause and extent of influence, through News on the LINE Developers site.

LINE Platform
The procedure for creating an Assertion Signing Key will be changed
2021/04/01

The procedure for creating an Assertion Signing Key is scheduled to change in early May of 2021.

How it affects developers using Assertion Signing Keys

This change affects developers who issue and use Assertion Signing Keys on the following channels:

  • LINE Login
  • Messaging API
  • LINE MINI App
  • Blockchain Service

Review the details of the changes before making any changes.

# Overview

Currently, when you click the Issue button for the Assertion Signing Key in the LINE Developers Console, a key pair (private key/public key) of the Assertion Signing Key is generated on LINE’s server side, and developers can download the private key. To increase the security of the Assertion Signing Key, we’ll change the issuing procedure as follows:

Before change After change
Issuing procedure
  1. Developer clicks the Issue button in the LINE Developers Console
  2. A key pair for the Assertion Signing Key is generated on LINE’s server side
  3. Developer downloads and saves the private key
    * We only display the private key once when issued. LINE only stores the public key. We don't store the private key.
  1. Developer generates an Assertion Signing Key pair in their environment (PC or server)
  2. Developer clicks the Assertion Signing Key's Register a public key button in the LINE Developers Console
  3. Developer pastes public key into the form on the LINE Developers Console and clicks the Register button
  4. Once developer succeeds in registering the public key, kid will be displayed in the LINE Developers Console
Instructions for use Developer uses private key when issuing a Channel access token v2.1. No change

You can continue using Assertion Signing Keys previously issued in the LINE Developer Console, even after the procedure changes.

# Estimated date of specification change

Early May 2021

We’ll announce the exact date and time as soon as possible. The contents and date of this specification change are subject to change without notice.

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

LINE Developers Console LINE Login Messaging API LINE MINI App LINE Blockchain Platform
[Resolved/Updated] Notice about partial LIFF API outage
2021/03/23
Updated on March 26, 2021

Initially, the date and time of the outage was given as "March 22, 2021 around 13:55 - 16:30 (UTC+9)", but the problem continued to occur for some liff.getFriendship() operations even after the reported recovery time. The time of the outage in this news article has also been changed as a result of our investigation. Consequently, we have corrected the "Date and time of outage". We sincerely apologize for the inconvenience caused.

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

# Date and time of outage

March 22, 2021 around 10:15 - March 25, 2021 around 11:36 (UTC+9)

# Cause of the outage

Server failure

# Impact

Using the liff.getFriendship() LIFF method to get the friendship between a user and the LINE Official Account

# Details

During the stated date and time, when using liff.getFriendship(), an error occurred in the browser that opened the LIFF app due to a violation of the Cross-Origin Resource Sharing (CORS) (opens new window) policy. The problem has been fixed, and you can now use liff.getFriendship() normally.

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

Outage Report LIFF
[Resolved] Notice about service outage for Mark-as-Read API
2021/03/18

We'd like to inform you about a service outage regarding the Mark-as-Read API which marks messages from users as "Read". The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

Use of the Mark-as-Read API requires an application

Only corporate users who have submitted the required applications can use the Mark-as-Read API.

For more information, see Overview in the Options for corporate customers documentation.

# Date and time of outage

March 17, 2021 around 4:51 - around 7:35 (UTC+9)

# Cause of the outage

Server failure

# Impact

The request process of Mark-as-Read API

# Details

During the stated date and time, the Mark-as-Read API might not be processed properly and cause errors with status code 5xx.

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

Outage Report Options for corporate customers
LIFF v2.8.1 released
2021/03/16

We've released LIFF v2.8.1.

This update only includes refactoring of the SDK. There is no change in features.

If you're using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), it will automatically update to v2.8.1.

If you're using the npm package, you can upgrade to v2.8.1 by running npm install @line/liff@2.8.1 or yarn add @line/liff@2.8.1.

For more information on how to integrate the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

LIFF
The "Header background color" setting for the LINE MINI App will be temporarily disabled in the LINE Developers Console
2021/03/10

During the following time period, you won't be able to set or change the Header background color in LINE MINI App in the LINE Developers Console. Thank you for your understanding.

# Date and time

March 15, 2021 11:00 - 12:00 (UTC+9)

*The actual end time may be earlier.

# Details

When you try to set the Header background color in the LIFF tab of the LINE MINI App channel in the LINE Developers Console, the color selector won't be displayed and you won't be able to set the header background color.

Header background color setting

You can still set and change settings other than Header background color as usual.

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

LINE MINI App Maintenance LINE Developers Console
Messaging API update for March 2021
2021/03/10

We've added new features to the Messaging API. These are the features added in this update:

# URI action can be used with quick reply

URI action can be used with quick reply. When you send a message with a quick reply button configured from your LINE Official Account, the following is displayed at the bottom of the chat screen.

Example of URI action

When you configure URI action with quick reply, users can do the following when they tap the button:

  • Open a specified URL in LINE's in-app browser
  • Open a specified number on a call app
  • Share a LINE Official Account using the LINE URL scheme

For more information on quick reply, see Using quick reply. For more information on what you can do with each action, including URI action, see Action.

For more information on URI action, see URI Action under the Messaging API Reference.

# "Feature for getting statistics per aggregation unit" has been added to optional functions for corporate customers

"Feature for getting statistics per aggregation unit" has been added to optional functions for corporate customers. This feature enables you to aggregate statistics when sending push messages and multicast messages to multiple end users. You can view statistics on a per-unit basis, simply by specifying any unit name when sending the message.

Workflow for aggregating statistics per unit

User interaction statistics per request ID have been available for broadcast and narrowcast messages, but statistics hadn't been available for push messages or multicast messages. "Custom aggregation of statistics per unit" enables you aggregate and obtain statistics per unit on multiple push messages and multicast messages.

Before change After change
Up until now, you couldn't get statistics with push messages or multicast messages.
User interaction statistics		 By assigning a unit name when sending the message, you can get statistics on a per-unit basis.
Aggregating statistics per unit

For more information, see Get statistics per aggregation unit under "Options for corporate customers".

Messaging API
[Resolved] Notice about service outage for LINE Login
2021/03/10

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

# Date and time of outage

March 8, 2021 15:03 - 15:25 (UTC+9)

# Cause of the outage

Server failure

# Impact

LINE Login services that use auto login

# Details

During the stated date and time, LINE Login requests using the auto login feature could not be processed properly and LINE Login would fail in some cases.

Single Sign On (SSO) Login and Log in with email address or QR code were not affected.

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

Outage Report LINE Login
The UI of the LIFF app will change in LINE v11.3.0
2021/03/01

The UI of LIFF apps opened in LINE v11.3.0 will change.

# Toast displayed during LIFF-to-LIFF transition will change

In LINE v11.3.0, the toast displayed during "LIFF-to-LIFF transitions," where users can transition to another LIFF app without closing the LIFF app opened in the LIFF browser, will change. This change makes it easier for users to identify the destination LIFF app.

The design of the toast differs between Android and iOS. The figure below shows an example of a toast when using an iPhone.

In LINE v11.2.x and earlier, the toast message is displayed in the center of the screen. In LINE v11.3.0, the toast message is displayed at the bottom of the screen.

Changes Supported OS LINE v11.2.x and earlier LINE v11.3.0
Message*
  • iOS
  • Android
 Switched to another app. Switched to the {LIFF app name} app.**
Display location iOS only*** Center of screen Bottom of screen

* Toast messages are displayed in multiple languages according to LINE's language settings, but {LIFF app name} will be displayed in the language it was entered as.

** The {LIFF app name} section displays the app name specified in the LIFF app name section of the LIFF tab in the LINE Developers Console.

*** LINE v11.2.0 and earlier for Android will also display the toast at the bottom of the screen.

For more information about LIFF-to-LIFF transitions, see Opening a LIFF app from another LIFF app in the LIFF documentation.

# LIFF apps will be displayed in a modal window in LINE for iPadOS

In LINE v11.3.0, to improve the experience with LIFF apps designed for many portrait modes (portrait display), LIFF apps opened on the iPad will be displayed in a formSheet (opens new window) size (540W x 620H pt) modal window.

Regardless of the Size setting (Compact,Tall, or Full) specified in the LIFF tab of the LINE Developers Console, LIFF apps will always be displayed in a formSheet size modal window in LINE v11.3.0 on iPad.

Example of a LIFF app with the screen size set to Compact:

formSheet modal display on iPad

About the screen ratio in landscape mode (landscape view)

formSheet will be displayed in portrait mode screen ratio (540W x 620H pt) even in landscape mode (landscape display).

landscape mode

LIFF
[Updated] Replace (Backward compatibility mode) has been removed from the permanent link redirect settings of the LIFF app and LINE MINI App
2021/03/01

As announced on November 20, 2020, effective March 1, 2021, Replace (Backward compatibility mode) in Method for converting additional information in the LIFF URL on the LINE Developers console is no longer available.

After this change, all LIFF and LINE MINI App URLs will be opened with Concatenate.

How to process additional information in LIFF URLs

Cases in which Replace (Backward Compatibility Mode) works

After March 1, 2021, LIFF SDK v2.2.1 and earlier will continue to work in environments that don't support Replace (Backward compatibility mode), but the normal operation of the LIFF app and LINE MINI App isn't guaranteed. We recommend upgrading to LIFF SDK v2.3.0 or later.

# Transition from "Replace (Backward compatibility mode)" to "Concatenate"

If your existing LIFF and LINE MINI Apps are using Replace (Backward compatibility mode), do these two things to make them compatible with Concatenate.

# Upgrade your LIFF SDK version to v2.3.0 or later

Versions earlier than v2.3.0 don't support Concatenate, so upgrade to v2.3.0 or later.

If you're already using v2.3.0 or later, you don't need to upgrade.

# Make endpoint URL and LIFF URL correspond to "Concatenate"

When the setting is switched to Concatenate, the path and query parameters (/2020campaign/?key=value) specified in Endpoint URL of the LINE Developers Console will be included in the secondary redirect destination. As a result, the same endpoint URLs and LIFF URLs that were used to set Replace (Backwards compatibility mode) may result in unintended redirects to unintended URLs.

Make Endpoint URL and LIFF URL compatible with Concatenate.

To learn about the difference between Replace (Backward compatibility mode) and Concatenate, see Create a secondary redirect URL in the LIFF documentation.

Verify that the LIFF app and LINE MINI App open correctly after changing the settings

Once you have migrated your existing LIFF app and LINE MINI App settings to Concatenate, verify that the app opens correctly with the new settings. If they don't open correctly, correct the LIFF SDK version, Endpoint URL, and LIFF URL to be compatible with Concatenate.

# Convert URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" (Updated on July 1, 2021)

Updated on July 1, 2021

As announced on 31st May, 2021, Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification has been removed at the end of June 2021.

Even after migrating your LIFF App or LINE MINI App to Concatenate, if the Replace (Backward compatibility mode) specification still requires a transition to a secondary redirect URL, use the function that converts URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)".

Use only if you want to generate a secondary redirect URL using the Replace (Backward compatibility mode) method

The function that converts URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" is information for generating secondary redirect destination URLs in the same way as Replace (Backward compatibility mode). If your app already supports Concatenate, you don't need to use this function.

This function is provided as a temporary fix for the discontinuation of Replace (Backward Compatibility Mode) and isn't intended to be a recommendation to use the code. The best solution is making the LIFF app and LINE MINI App compatible with Concatenate.

We're providing this function for a limited time only

Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification in the LIFF documentation is intended to support the migration to Concatenate, due to the discontinuation of Replace (Backward compatibility mode). Some time after the discontinuation of Replace (Backward compatibility mode), we may delete the page. If you wish to check the conversion method even after the page is deleted, download the function that converts secondary redirect URL generated by "Concatenate", and refer to the code as necessary.

LIFF LINE MINI App End of life
[Resolved] Notice about service outage for processing rich menus
2021/02/26

We'd like to inform you about a service outage regarding some of the rich menu APIs provided by 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

  • February 22, 2021 16:00 - February 23, 2021 2:46 (UTC+9)
  • February 23, 2021 11:38 - 13:31 (UTC+9)
  • February 23, 2021 17:50 - 18:43 (UTC+9)
  • February 24, 2021 0:30 - 7:42 (UTC+9)
  • February 24, 2021 12:26 - 15:00 (UTC+9)

*Listed times are estimates

# Cause of the outage

Server failure

# Impact

Processing of these APIs for rich menus:

# Details

The processing of the listed APIs took a long time and, in some cases, the rich menu wasn't switched correctly. The process has now been resolved and the rich menus are being processed correctly.

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

Outage Report Messaging API
[Resolved] Notice about service outage for sending webhook events
2021/02/26

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

February 26, 2021 around 13:45 - 14:15 (UTC+9)

# Cause of the outage

Network failure

# Impact

Sending webhook events

# Details

During the stated date and time, webhook events may have been delayed or unable to be sent successfully.

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

Outage Report Messaging API
[Resolved] Notice about service outage for sending webhook events
2021/02/16

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

February 4, 2021 12:37 - February 16, 2021 17:59 (UTC+9)

# Cause of the outage

Due to the detection of unauthorized communications in our network, we've blocked some communications as a preventive measure.

# Details

During the date and time stated above, webhook events couldn't be sent to some bot servers (Webhook URLs) using ngrok.

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

Outage Report Messaging API
LIFF v2.8.0 released
2021/02/15

We've released LIFF v2.8.0.

These bugs have been fixed in LIFF v2.8.0.

There are no feature changes or additions.

# Fixed bug of liff.init() being resolved before being redirected to a secondary redirect URL

In versions earlier than LIFF v2.7.1, there was a bug of liff.init() being resolved before being redirected to the secondary redirect URL. Because of this bug, there would be duplicate processing of the then() method, once before and once after being redirected to the secondary redirect URL.

In the code example below, the alert liff.init() is resolved. is displayed twice, because liff.init() is resolved once each, before and after being redirected to the secondary redirect URL.

Code sample for displaying alerts when liff.init() is resolved:

liff.init(myLiffId).then(() => {
    // This process is executed after liff.init() is resolved.
    window.alert('liff.init() is resolved.');
});

Because in LIFF v2.8.0, liff.init() is resolved for the first time after being redirected to a secondary redirect URL, duplicate processing of the then() method has been fixed. In the code sample above, an alert is displayed only once.

LIFF Version Timing when liff.init() is resolved
v2.7.1 or earlier resolve-timing-v2-7-0
v2.8.0 resolve-timing-v2-8-0

# Fixed bug of unintentional decoding of URL encoded query parameters

In versions earlier than LIFF v2.7.1, if a developer gave the LIFF URL a URL encoded query parameter (e.g. ?t=http%3A%2F%2Fexample.com), the query parameter was decoded when being redirected (e.g. ?t=http://example.com). As a result, it would lead to a secondary redirect URL unintended by the developer.

In LIFF v2.8.0, query parameters aren't decoded but redirected remaining URL encoded.

Redirect flow when you open the LIFF URL https://liff.line.me/{liffId}?t=http%3A%2F%2Fexample.com:

LIFF Version Primary redirect URL Secondary redirect URL
v2.7.1 or earlier https://endpoint.example.jp/?liff.state=
?t=http%3A%2F%2Fexample.com		 https://endpoint.example.jp/
?t=http://example.com
v2.8.0 https://endpoint.example.jp/?liff.state=
%3Ft%3Dhttp%253A%252F%252Fexample.com		 https://endpoint.example.jp/
?t=http%3A%2F%2Fexample.com
LIFF URL that contains a query parameter

When using LIFF URLs with URL encoded query parameters, upgrade to v2.8.0 to avoid unintended redirections to URLs.

For more information on redirects on LIFF apps, see Behaviors from accessing the LIFF URL to opening the LIFF app in the LIFF documentation.

LIFF
TLS 1.0 and TLS 1.1 support by the webhook notification source discontinued
2021/02/08

As announced on October 6, 2020, January 18, 2021, and January 28, 2021, the following updates have been made to the LINE Platform, which is the source for webhook notifications for the Messaging API.

  • Supported SSL/TLS protocol versions
  • Supported HTTP versions
  • Request header field name
  • Supported root certification authorities
What if chatbot stops working?

If your chatbot suddenly stops working, it's possible that these updates caused communication failures from the LINE Platform to the webhook URL (the bot server which receives webhook notifications). Check the communication using the verification method described in Reminder: TLS 1.0 and TLS 1.1 support by the webhook notification source will be discontinued at the end of January 2021.

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

Messaging API SSL/TLS End of life
[Updated] An example code for converting URL generated by "Concatenate" to the "Replace (Backward compatibility mode)" specification has been published in LIFF
2021/02/02
Updated on July 1, 2021

As announced on 31st May, 2021, Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification has been removed at the end of June 2021.

As announced on November 20, 2020, on March 1, 2021, Replace (Backward compatibility mode) in Method for converting additional information in the LIFF URL on the LINE Developers Console will no longer be available. After this change, all LIFF and LINE MINI App URLs will be opened with Concatenate.

Accordingly, we published a document introducing how to address cases in which the Replace (Backward compatibility mode) specification still requires a transition to a secondary redirect URL, even after you migrate your LIFF app or LINE MINI App to Concatenate.

This document introduces the function and logic that redirects users to a URL based on the Replace (Backward compatibility mode) specification when they click on a secondary redirect URL generated by Concatenate.

When you use the conversion code

We will provide this document for a limited time only.

Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification in the LIFF documentation is intended to support the migration to Concatenate, due to the discontinuation of Replace (Backward compatibility mode). Some time after the discontinuation of Replace (Backward compatibility mode), we may delete the page. If you wish to check the conversion method even after the page is deleted, download the function that converts secondary redirect URL generated by "Concatenate", and refer to the code as necessary.

LIFF LINE MINI App
Reminder: TLS 1.0 and TLS 1.1 support by the webhook notification source will be discontinued at the end of January 2021
2021/01/28

As announced on October 6, 2020 and January 18, 2021, we're planning these updates to the LINE Platform, which is source for webhook notifications for the Messaging API. If you're using a webhook, 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 this table 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 this table for differences before and after the transition.

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

# Request header field name

After the transition, there may be changes to uppercase and lowercase letters in the field name of the Request header when sending a webhook from the LINE Platform. *1

Before transition After transition
Header field name example X-Line-Signature x-line-signature

In addition, uppercase and lowercase letters may change without notice in the future as the LINE server is updated. The bot server that receives the webhook should handle the header field name without case distinction. *2

*1 https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2 (opens new window)
*2 https://datatracker.ietf.org/doc/html/rfc7230#section-3.2 (opens new window)

# 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 this table 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

# Impact

If you're using Messaging API webhooks, we recommend that you use one of these 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

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 its customers. Thank you for your understanding.

Messaging API SSL/TLS
You can now use audiences created with LINE Ads and LINE Points Ads
2021/01/27

Audiences created and shared by LINE Ads (opens new window) and LINE Points Ads (opens new window) (Japanese only) can now be used through the Messaging API.

Audiences now available through the Messaging API How to create
Audience for uploading user IDs LINE Points Ads (opens new window) (Japanese only)
Web traffic audience LINE Ads (opens new window)
App event audience LINE Ads (opens new window)
Video view audience LINE Ads (opens new window)
How to share audiences created with LINE Ads

For more information on how to "share" audiences created in the LINE Ads management screen, see Delivering with Audiences (opens new window) (Japanese only) in LINE for Business.

To use audiences created by LINE Ads or LINE Points Ads from the Messaging API, you will need to activate them using the newly added "Activate audience" endpoint. For more information, see Activate audience in the Messaging API reference.

With this change, we added several properties in these Messaging API endpoints to check if an audience is activated or not, and the name of the ad account that created the audience group.

Messaging API
Some endpoints have stopped accepting requests with the old domain name
2021/01/21

As we have announced on November 8, 2019, March 19, 2020, August 12, 2020, and October 9, 2020, the domain name for some endpoints in the Messaging API changed from "api.line.me" to "api-data.line.me".

This announcement is to inform you that we're no longer accepting requests under the old domain name as of today because the migration deadline expired.

# Target endpoints

# Impact

If you access these endpoints under the old domain name, the status code 404 will be returned. If the above endpoints were used under an old domain name, change the domain name to api-data.line.me as soon as possible.

We apologize for any inconvenience and appreciate your understanding.

Messaging API
The handling of "Safe Areas" for LIFF apps and LINE MINI Apps will be stricter
2021/01/21

Starting with LINE v11.0.0 for iOS and iPadOS, the handling of the "Safe Area" will be stricter.

From now on, to display LIFF apps and LINE MINI Apps with the screen size set to Full in a layout that covers the entire display on devices with rounded corner displays such as iPhone X, specify viewport-fit=cover in the <meta> tag.

"viewport-fit=cover" specification example

<meta name="viewport" content="width=device-width,initial-scale=1.0,viewport-fit=cover">

However, due to a bug caused by the current version of iOS and iPadOS, the safe area won't be disabled in LINE v11.0.0 even if viewport-fit=cover is specified in the <meta> tag. We're planning to fix this issue in a future version of LINE.

How to disable the Safe Area in LINE v11.0.0

If you want to lay out the entire display in LINE v11.0.0, you can disable the Safe Area by specifying viewport-fit=cover and then specifying height: 100vh in the <html> tag in CSS.

 html { height: 100vh; }
What is a "Safe Area?"

"Safe Area" in iOS and iPadOS refers to an area that can be safely laid out on devices with rounded corner displays, leaving a margin in the header/footer area. You can usually disable the safe area and lay out the entire display by specifying viewport-fit=cover in the <meta> tag in the HTML.

safe area

For more information about safe areas, see Layout Guides and Safe Area (opens new window) on the Apple Developer site.

LIFF
Messaging API update for January 2021
2021/01/20

We added new properties to the Get narrowcast message status API endpoint and the Text message type of the Message webhook event object of the Messaging API.

# Get narrowcast message status properties

We've added these properties to the Get narrowcast message status API endpoint. With these new properties, you can now know when the narrowcast message request was accepted and when processing was completed.

  • acceptedTime: The accepted time (in milliseconds) of the narrowcast message request.
  • completedTime: The completed time (in milliseconds) of the processing of the narrowcast message request. Returned when the phase property is succeeded or failed.

For more information, see Get narrowcast message status in the Messaging API reference.

# Text message type properties

Before, when a user was mentioned in a group or room, it wasn't possible to capture any information about the mention. Now, with the new properties we've added to the Text message type of the Message webhook event object, you can.

These are the newly added properties.

  • mention: Object containing the contents of the mentioned user.
  • mention.mentionees[]: Mentioned user information.
  • mention.mentionees[].index: Index position of the user mention for a character in text, with the first character being at position 0.
  • mention.mentionees[].length: The length of the text of the mentioned user. For a mention (@example), 8 is the length.
  • mention.mentionees[].userId: User ID of the mentioned user.

For more information, see the Text message type in the Messaging API reference.

Messaging API
LIFF v2.7.1 released
2021/01/20

We've released LIFF v2.7.1.

This bug has been fixed in LIFF v2.7.1:

# Fixed a bug that might prevent LIFF apps using LIFF v2.7.0 from launching in external browsers

We’ve fixed a bug that might cause LIFF apps using LIFF v2.7.0 to fail to launch when opened in external browsers. In LIFF v2.7.1, the LIFF app can launch correctly in external browsers.

When already using LIFF v2.7.0

If you are already using LIFF v2.7.0, we recommend that you update your LIFF apps to LIFF v2.7.1.

When you are using the CDN edge path (https://static.line-scdn.net/liff/edge/2/sdk.js), it will be automatically updated to v2.7.1. When you are using the CDN fixed path or the npm package version of LIFF SDK, update it to LIFF v2.7.1 manually.

For more information about the different ways to embed the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

LIFF
[Updated] Reminder: On March 1, 2021, "Replace (Backward compatibility mode)" will be removed from the permanent link redirection settings for LIFF App and LINE MINI App
2021/01/18
Added on February 2, 2021

We have added a way to address cases in which the Replace (Backward compatibility mode) specification still requires a transition to a secondary redirect URL, even after migrating your LIFF App or LINE MINI App to Concatenate. For more information, see Convert URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification.

Changes from the news for November 20, 2020

In the November 20, 2020 news, the day when it will not be possible to return to Replace (Backward compatibility mode) once Method for converting additional information in the LIFF URL is set to Concatenate was announced as January 11, 2021. However, the schedule was changed to January 19, 2021. For more information about the updated schedule, see Discontinuation schedule.

As announced on November 20, 2020, on March 1, 2021, Replace (Backward compatibility mode) in Method for converting additional information in the LIFF URL on the LINE Developers Console will no longer be available. After this change, all LIFF and LINE MINI App URLs will be opened with Concatenate.

How to process additional information in the LIFF URL

Switch the setting to Concatenate for LIFF apps and LINE MINI Apps that are currently set to Replace (Backward compatibility mode) by the discontinuation date.

Continuation of "Replace (Backward compatibility mode)"

After March 1, 2021, environments that don't support Concatenate, such as LINE v10.10.0 or lower and LIFF SDK v2.2.1 or lower, can continue to use Replace (Backward compatibility mode), but the normal operation of the LIFF app and LINE MINI App isn't guaranteed. We recommend migrating to Concatenate.

# Discontinuation schedule

Date Description
January 11, 2021
January 19, 2021
  • Deprecation of Replace (Backward compatibility mode)
  • Replace (Backward compatibility mode) will no longer be available when creating new LIFF apps and LINE MINI Apps.
  • Once you change the setting to Concatenate, you can't revert to Replace (Backward compatibility mode).
March 1, 2021 Replace (Backward compatibility mode) will be removed, so the setting will be switched to Concatenate in all LIFF apps and LINE MINI Apps.

# Transition from "Replace (Backward compatibility mode)" to "Concatenate"

If your existing LIFF app or LINE MINI App uses Replace (Backward compatibility mode), do these three things to move to Concatenate by the discontinuation date (February 28, 2021).

# Upgrade your LIFF SDK version to v2.3.0 or later

Versions earlier than v2.3.0 don't support Concatenate, so upgrade to v2.3.0 or later.

If you're already using v2.3.0 or later, you don't need to upgrade.

# Make endpoint URL and LIFF URL correspond to "Concatenate"

When the setting is switched to Concatenate, the path and query parameters (/2020campaign/?key=value) specified in Endpoint URL of the LINE Developers Console will be included in the secondary redirect destination. As a result, the same endpoint URLs and LIFF URLs that were used to set Replace (Backwards compatibility mode) may result in unintended redirects to unintended URLs.

Make Endpoint URL and LIFF URL to be compatible with Concatenate if necessary.

To learn about the difference between Replace (Backward compatibility mode) and Concatenate, see Create a secondary redirect URL in the LIFF documentation.

Verify that the LIFF app and LINE MINI App open correctly after changing the settings

Once you have migrated your existing LIFF app and LINE MINI App settings to Concatenate, verify that the app opens correctly with the new settings. If they don't open correctly, correct the LIFF SDK version, Endpoint URL, and LIFF URL to be compatible with Concatenate.

# Convert URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" (Added on July 1, 2021)

Updated on July 1, 2021

As announced on 31st May, 2021, Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification has been removed at the end of June 2021.

Even after migrating your LIFF app or LINE MINI App to Concatenate, if the Replace (Backward compatibility mode) specification still requires transition to a secondary redirect URL, use the function that converts URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)".

We are providing this function for a limited time only.

Example code for converting URL generated by "Concatenate" to URL of "Replace (Backward compatibility mode)" specification in the LIFF documentation is intended to support the migration to Concatenate, due to the discontinuation of Replace (Backward compatibility mode). Some time after the discontinuation of Replace (Backward compatibility mode), we may delete this page. If you wish to check the conversion method even after the page is deleted, download the function that converts secondary redirect URL generated by "Concatenate", and refer to the code as necessary.

LIFF LINE MINI App End of life
Reminder: TLS 1.0 and TLS 1.1 support by the webhook notification source will be discontinued at the end of January 2021
2021/01/18

As announced on October 6, 2020, we're planning these updates to the LINE Platform, which is source for webhook notifications for the Messaging API. If you're using a webhook, 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 this table 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 this table for differences before and after the transition.

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

# Request header field name

After the transition, there may be changes to uppercase and lowercase letters in the field name of the Request header when sending a webhook from the LINE Platform. *1

Before transition After transition
Header field name example X-Line-Signature x-line-signature

In addition, uppercase and lowercase letters may change without notice in the future as the LINE server is updated. The bot server that receives the webhook should handle the header field name without case distinction. *2

*1 https://datatracker.ietf.org/doc/html/rfc7540#section-8.1.2 (opens new window)
*2 https://datatracker.ietf.org/doc/html/rfc7230#section-3.2 (opens new window)

# 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 this table 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

# Impact

If you're using Messaging API webhooks, we recommend that you use one of these 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

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 its customers. Thank you for your understanding.

Messaging API SSL/TLS End of life
LIFF v2.7.0 released
2021/01/14

We've released LIFF v2.7.0.

These are the changes in this update:

# The npm package version of LIFF SDK can now be referenced by RequireJS

The npm package version of LIFF SDK can now be referenced by RequireJS (opens new window).

For information on how to integrate the npm package version of the LIFF SDK, see Integrating the LIFF SDK with the LIFF app in the LIFF documentation.

# Fixed a bug in which the name property of the ID token retrieved by the liff.getDecodedIDToken() method became unreadable

In LIFF v2.6.0 or earlier, when a decoded ID token was retrieved using the liff.getDecodedIDToken() method, the value of the name property was unreadable if the username contained Unicode characters other than ASCII characters, such as Japanese.

In LIFF v2.7.0, the bug was fixed and usernames written in Unicode characters such as Japanese can now be retrieved correctly.

If you get an ID token with コニー as the user name

user profile of conny

LIFF v2.6.0 or earlier LIFF v2.7.0
 
{
"iss": "https://access.line.me",
"sub": "U272cada9c6f4c0c933b0713bc2f90f68",
"aud": "1234567890",
"exp": 1513142487,
"iat": 1513138887,
"name": "コニー", //Unreadable
"picture": "https://profile.line-scdn.net/..."
}
 
{
"iss": "https://access.line.me",
"sub": "U272cada9c6f4c0c933b0713bc2f90f68",
"aud": "1234567890",
"exp": 1513142487,
"iat": 1513138887,
"name": "コニー", //Correctly received
"picture": "https://profile.line-scdn.net/..."
}

For more information on liff.getDecodedIDToken(), see liff.getDecodedIDToken() in the LIFF API reference.

LIFF
[Resolved] Notice about service outage for sending webhook events
2021/01/14

We'd like to inform you about a service outage regarding LIFF. When a message was sent to a chat room using the liff.sendMessages() method of the LIFF SDK, the corresponding webhook event was not sent to the bot server. The issue has now been resolved but we sincerely apologize for the inconvenience caused to our customers.

The impact of this failure is limited to sending webhook events. Messages sent using the liff.sendMessages() method were displayed correctly in the chat room.

# Date and time of outage

January 13, 2021 around 15:30 - 22:19 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending webhook events when messages were sent with the liff.sendMessages() method.

# Details

During the stated date and time, webhook events were not sent correctly. The issue has now been resolved and the webhook events are sent correctly.

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

Outage Report LIFF Messaging API
[Resolved] Notice about service outage for sending webhook events
2021/01/13

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

January 13, 2021 around 10:52 - 10:58 (UTC+9)

# Cause of the outage

Server failure

# Impact

Sending webhook events

# Details

During the stated date and time, webhook events may have been delayed or unable to be sent successfully.

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

Outage Report Messaging API
Beacon Leave Event was deprecated at the end of 2020
2021/01/07

As announced on June 6, 2020 and November 25, 2020, the leave event of Beacon event was deprecated at the end of 2020.

Schedule Description
End of 2020 Leave event was deprecated.
January 6, 2021 Webhook transmission has ceased.
Tip

We will continue supporting other Beacon events (enterevent, bannerevent, or stayevent).

# Impact

Please adjust your service to use the stay event instead of the leave event for detecting when users exit the reception range of Beacon.

beacon.type Description
leave [Has been deprecated at the end of 2020] User left the reception range of Beacon.
stay User is currently within the reception range of Beacon.
This event is sent repeatedly at a minimum interval of 10 seconds.
We are no longer accepting new applications in Japan

As of January 2021, we are no longer accepting new applications for stay events.

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

Messaging API End of life

Filter by
news tag

Android Bot Designer Channel access token CLOVA CLOVA Extensions Kit Developers Community LINE Developers Console Deprecated Docs End of life Flex Message Flex Message Simulator Flutter Group Imagemap message iOS Life cycle LIFF LINE Ads LINE API Expert LINE Blockchain Platform LINE Developers site LINE Login LINE MINI App LINE Official Account LINE Platform LINE Login SDK LINE Things LINE TV Maintenance Messaging API Options for corporate customers Outage Report Rich menu Social API LINE Social Plugins SSL/TLS Template message Unity

LINE Developers Official Account

Subscribe for the latest information on the LINE Platform
LINE Developers QR Code