# News: Articles for 2022

2022/12/06

Messaging API requests will return an error if the JSON object has duplicate properties

As announced on October 31, 2022, we've changed the specification of the Messaging API to return an error if the request body's JSON object contains duplicate properties.

# Date of change

December 6, 2022 JST (GMT+9)

# Changes

The HTTP status 400 and an error response will be returned if the JSON object contains duplicate properties.

The following are examples of error responses if you send a push message with duplicate properties.

// If you specify a duplicate 'to' property
{
  "message": "The request body could not be parsed as JSON (line: 3, column: 7)",
  "details": [
    {
      "message": "Duplicate field 'to'"
    }
  ]
}

// If you specify a duplicate 'type' property in messages[1]
{
  "message": "The property, 'messages[1]', in the request body is invalid (line: 11, column: 13)",
  "details": [
    {
      "message": "Duplicate field 'type'"
    }
  ]
}

# Important points about the specification change

From now on, even if you use the same request body of a request that was successful before the specification change, you'll receive an error response if the JSON object contains duplicate properties. Make sure that the request body doesn't contain any duplicate properties.

You can use the following endpoints to validate message objects and rich menu objects:

# Updating the LINE Messaging API SDK for Java

Some older versions of the LINE Messaging API SDK for Java (opens new window) send duplicate JSON object properties. This issue has been fixed in version 5.0.3 (opens new window).

If you're using the SDK for Java, please update to version 5.0.3 or later.

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

2022/12/01

You can now use both webhooks and chats together for your LINE Official Account

Previously, LINE Official Accounts required a setting called Response Mode to select either Bot mode for using webhooks or Chat mode for using chats. This specification has been changed so that webhooks and chats can be used together for LINE Official Accounts from November 30, 2022.

# Date of change

November 30, 2022 JST (GMT+9)

# Changes in existing LINE Official Accounts

The settings of existing LINE Official Accounts were automatically changed as follows. You can check and change the settings in the LINE Official Account Manager (opens new window).

Before change After change (current)
Response mode is set to Chat mode Chat is set to "On"
Response mode is set to Bot mode Chat is set to "Off"

For more information, see [Notice] Regarding change in "Response settings" (opens new window) in LINE Official Account Manager.

2022/11/29

[Resolved] Notice about service outages for the Home tab of the LINE app

We'd like to inform you about the following two service outages regarding the Home tab of the LINE app. These issues have now been resolved. We sincerely apologize for any inconvenience that this may have caused.

  1. An issue with some of the "Pinned services" being removed
  2. An issue with "Pinned services" being changed to default settings

Details of each outage are as follows.

# 1. An issue with some of the "Pinned services" being removed

# Period of the outage

May 21, 2020 - October 16, 2022 JST (GMT+9)

# Cause of the outage

An issue with LINE for iOS from 10.8.0 to 12.17.0.

# Impact

There was a problem with some users who met all of these conditions:

  • A user uses LINE for iOS.
  • A user uses LINE version from 10.8.0 to 12.17.0.
  • A user has added services to the "Pinned services" of the LINE Home tab.

# Details

In the Home tab of LINE for iOS version 10.8.0 or later, the "Pinned services" weren't updated correctly and the services were unpinned when it failed to retrieve the data from the service list. This issue has been resolved in LINE for iOS version 12.17.1 or later, which has been available since October 17, 2022.

# 2. An issue with "Pinned services" being changed to default settings

# Period of the outage

  • LINE for iOS: May 19, 2022 - November 1, 2022 JST (GMT+9)
  • LINE for Android: October 3, 2022 - October 24, 2022 JST (GMT+9)

# Cause of the outage

  • An issue with LINE for iOS from 12.7.0 to 12.17.1.
  • An issue with LINE for Android from 12.16.0 to 12.17.2.

# Impact

There was a problem with some users who met all of these conditions:

  • A user uses LINE for iOS or LINE for Android.
  • A user uses LINE for iOS version from 12.7.0 to 12.17.1 or LINE for Android version from 12.16.0 to 12.17.2.
  • A user has added services to the "Pinned services" of the LINE Home tab.

# Details

In the Home tab of LINE for iOS version 12.7.0 or later or LINE for Android version 12.16.0 or later, when logging in again to reinstall the LINE app or transfer the account, the pinned services were changed to the default settings. On LINE for iOS, this issue only occurred when there was an error in the process of retrieving the "Pinned services" settings when logging in.

This issue has been resolved in LINE for iOS version 12.18.0 or later, which has been available since November 2, 2022, for LINE for iOS and since October 25, 2022, for LINE for Android.

# Notes

Once the services have been unpinned or changed due to these outages, they won't be restored automatically. To re-add the services, the user must manually add the services to the "Pinned services". Users affected by these issues will be notified individually via service messages.

We'll continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

2022/11/25

LINE Developers Console maintenance notice

Maintenance is scheduled for LINE Developers Console. We sincerely apologize for any inconvenience that this may cause and thank you for your understanding.

# Date and time of maintenance

November 29, 2022 2:00 - 6:00 JST (GMT+9)

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

# Impact

During the maintenance, you won't be able to perform the following operations on the LINE Developers Console.

  • Creating Messaging API channels and Blockchain Service channels
  • Adding or deleting developers to/from the Messaging API channels and Blockchain Service channels
2022/11/10

LIFF v2.21.3 released

We've released LIFF v2.21.3.

In LIFF v2.21.3, we've fixed the following bug.

# We've fixed a bug where an error would occur when importing the npm package of the LIFF SDK as an ES module

There was a bug where an error Uncaught ReferenceError: require is not defined would occur when importing the npm package of the LIFF SDK as an ES module.

This bug was fixed in LIFF v2.21.3 so that even in the above case, an error wouldn't occurred.

# How to update to LIFF v2.21.3

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

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

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

2022/11/09

On LINE for iOS version 12.19.0 or later, we'll be making changes to the UI of the action button in the LIFF browser

On LINE for iOS version 12.19.0 or later, we'll be making changes to the UI of the action button in the LIFF browser.

# Target version

LINE for iOS version 12.19.0 or later

# Changes

The UI of the action button will be changed from an action sheet (opens new window) to a pull-down button (opens new window). Also, the icon for each option of the action button will be displayed.

LINE for iOS version earlier than 12.19.0 LINE for iOS version 12.19.0 or later
The action button on LINE for iOS version earlier than 12.19.0 The action button on LINE for iOS version 12.19.0 or later
The UI of the action button on iOS earlier than 14

On iOS earlier than 14, even if the user is using LINE for iOS version 12.19.0 or later, the UI of the action button will be an action sheet (opens new window).

2022/10/31

Revision of LINE Official Account subscription plans

We're planning to revise the subscription plans for LINE Official Account around June 2023. In this revision, the pricing for each plan will remain unchanged, but the number of messages that can be sent for free will be changed.

For more information about the revision of LINE Official Account subscription plans, see Important: LINE Official Account new plan structure and end of prorated billing (opens new window) (only available in Japanese) in LINE for Business.

2022/10/31

As of December 5, 2022, Messaging API requests will return an error if the JSON object has duplicate properties

As of December 5, 2022, in the Messaging API, we'll change the specification to return an error when there are duplicate properties of the JSON object specified in the request body.

# Scheduled date of change

2022/12/05 JST (GMT+9)

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

# Changes

Currently, your request can succeed without error even if the request contains duplicate properties of the JSON object specified in the request body in the Messaging API. After the specification change, you'll receive a 400 HTTP status and an error response when there are duplicate properties of the JSON object.

The following are examples of the error responses when sending a push message with duplicate properties.

// If you specify a duplicate 'to' property
{
  "message": "The request body could not be parsed as JSON (line: 3, column: 7)",
  "details": [
    {
      "message": "Duplicate field 'to'"
    }
  ]
}

// If you specify a duplicate 'type' property in messages[1]
{
  "message": "The property, 'messages[1]', in the request body is invalid (line: 11, column: 13)",
  "details": [
    {
      "message": "Duplicate field 'type'"
    }
  ]
}

# Notes on specification change

After the specification change, even if you use the same content as a previously successful request for the request body, you'll receive an error response when there are duplicate properties of the JSON object. Before the specification change, make sure that there are no duplicate properties in the request body of the endpoint you're using.

# Updating the LINE Messaging API SDK for Java

In the LINE Messaging API SDK for Java (opens new window), some versions send duplicate JSON object properties. This issue has been fixed on version 5.0.3 (opens new window).

If you're using the SDK for Java, please update to 5.0.3 or later before the specification change.

# Background

The purpose of this specification change is to prevent unintended behavior due to duplicate properties.

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

2022/10/26

CLOVA assistant service on CLOVA devices will be terminated on March 30, 2023

As of March 30, 2023, the CLOVA assistant service on CLOVA devices will be terminated.

The CLOVA Extensions Kit, which allow developers to create their own skills for CLOVA devices, will also be discontinued.

# Details

LINE has been providing the CLOVA assistant service for CLOVA devices such as AI speakers (CLOVA WAVE, CLOVA Friends, CLOVA Friends Mini, CLOVA Friends Dock, and CLOVA Desk), which enables various functions through voice control. However, the service will be terminated on March 30, 2023.

Along with the built-in skills for CLOVA devices, Custom Extensions developed with CLOVA Extensions Kit, will also be terminated on the same day.

In addition, the skill review for the public release of Custom Extensions will be stopped on February 28, 2023.

After March 31, 2023, you won't be able to launch skills when talking to CLOVA devices.

# Schedule

The schedule for the service termination is as follows:

Date Descriptions
October 31, 2022, JST (GMT+9) Sales of CLOVA devices will be discontinued
February 28, 2023, JST (GMT+9) Applications for the skill review will no longer be accepted
March 30, 2023, JST (GMT+9)

# Data handling after the service termination

The data registered on the CLOVA Developer Center (opens new window) will be deleted after April 2023.

The CLOVA skill channel and the provider registered on the LINE Developers Console must be deleted by the developer themselves. We apologize for the inconvenience and appreciate your cooperation.

2022/10/24

The endpoints for validating message objects have been added

We've added endpoints for validating message objects in the Messaging API. Added endpoints are as follows:

Previously, when checking that message objects were valid, you had to actually send a message, such as to yourself. This method, however, reduced the number of messages that could be sent.

By using the above endpoints, you can validate that message objects are valid without reducing the number of messages that can be sent.

2022/10/19

[Resolved/Updated] Notice about service outage for the LINE Platform

Updated on October 20, 2022

We've updated the details of Messaging API.

Updated on October 19, 2022 17:10

We've updated the Date and time of outage and Impact.

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 19, 2022 around 12:00 - around 16:18 JST (GMT+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:

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


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

2022/10/18

LIFF apps can't be added to Messaging API channels

LINE provides the Server API for the LINE Front-end Framework (LIFF) for developers. Using the Server API, you can perform operations such as adding LIFF apps to LINE Login channels via the API.

When using the Server API, there are cases where the channel access token for a Messaging API channel is specified. However, as announced on February 5, 2020, you can't add LIFF apps to Messaging API channels.

When adding LIFF apps to channels using the Server API, specify the channel access token for a LINE Login channel. For more information, see Preparing a channel access token in the Server API reference.

2022/10/18

The LINE Developers Official Account has been split into a Japanese and an English version

As of October 18, 2022, we're distributing the latest information on the LINE Developers site from two LINE Official Accounts, a Japanese account and an English account.

Previously, we've delivered messages in both Japanese and English from one account. However, from now on we'll be operating separate accounts for each language.

The content will remain the same in both languages.

Old name New name QR code
- LINE Developers (JA) QR code for JA
LINE Developers LINE Developers (EN) QR code for EN

# To subscribe to the Japanese version

We created a new Japanese-language account, LINE Developers (JA), to deliver messages in Japanese.

To subscribe to the Japanese version, add the new LINE Official Account as a friend.

# To subscribe to the English version

The existing LINE Official Account has changed its name to LINE Developers (EN), and will continue to deliver information in English only. If you've already added the LINE Developers account as a friend, you don't have to do anything.

To newly subscribe to the English version, add LINE Developers (EN) as a friend.

2022/10/17

[Resolved] Notice about service outage for LINE Platform

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 16, 2022 around 17:47 - around 18:07 JST (GMT+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:

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.

2022/10/12

LIFF v2.21.2 released

We've released LIFF v2.21.2.

In LIFF v2.21.2, we've refactored the LIFF SDK to improve the stability of the LIFF 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), you'll automatically update LIFF to v2.21.2.

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

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

2022/10/11

[Resolved] Notice about service outage for the LINE Platform

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 8, 2022 around 5:51 - 6:45 JST (GMT+9)

# Cause of the outage

Server failure

# Impact

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

# 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.
  • Rich menus may not have been actually linked or unlinked to users in some requests to the endpoints that succeeded and returned a status code 202 when making a request to the following endpoints.
  • 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.

# LINE Developers Console

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

When an outage occurs, we post a preliminary report on the LINE API Status. For more information, see the news from April 5, 2021, LINE API Status site for checking service availability opened.

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

2022/10/11

On LINE version 12.17.0 or later, we'll be making changes to some of LIFF browser's specifications

On LINE version 12.17.0 or later, we'll be making changes to some of LIFF browser's specifications.

# Target version

LINE version 12.17.0 or later

# Changes

# In a LIFF browser with the screen size set to "Full", the header will shrink when scrolling

Previously, there was a problem with the user accidentally tapping the close button in the header while browsing a LIFF browser, causing the LIFF browser to close unintentionally.

To improve this problem, in a LIFF browser with the screen size set to "Full", the header will shrink when scrolling. When the header shrinks, some components of the header, such as the action button or the URL, will be hidden.

Normal header Shrinking header
Normal header in the LIFF browser Shrinking header in the LIFF browser

# Changes to minimizing a LIFF browser

Previously, there were three ways to minimize a LIFF browser.

Of these, dragging a LIFF browser will be changed to swiping a LIFF browser. Swiping a LIFF browser down will minimize the LIFF browser.

LIFF browser minimization (swiping a LIFF browser)

The differences in behavior between the LIFF browser and LINE's in-app browser

The LIFF browser and LINE's in-app browser behave differently when swiped down. Swiping LINE's in-app browser down will close LINE's in-app browser.

For more information on LIFF browser minimization, see Minimizing LIFF browser in the LIFF documentation.

2022/10/04

[Resolved] Notice about service outage for the Home tab of LINE for iOS

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

# Period of the outage

May 21, 2020 - September 7, 2022 JST (GMT+9)

# Cause of the outage

An issue with LINE for iOS from 10.8.0 to 12.14.0.

# Impact

There was a problem with some users who met all of these conditions:

  • A user uses LINE for iOS.
  • A user uses LINE version from 10.8.0 to 12.14.0.
  • A user has added services to the "Pinned services" of the LINE Home tab.

# Details

In the LINE Home tab, there was an issue that caused services to be unpinned if the user had added the services to the "Pinned services". This issue has been resolved in LINE for iOS version 12.14.1 or later, which has been available since September 7, 2022.

Once the services have been unpinned due to this outage, they won't be re-pinned automatically. If the user wants to re-add the services, the user must manually add the service to the "Pinned services". Users affected by this issue will be notified individually via service messages.

We'll continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

2022/10/03

The scheduled effective date of the "Individual Terms and Conditions for Provision of Information to ZHD Group" will be postponed to March 8, 2023

We'll postpone the scheduled effective date of the "Individual Terms and Conditions for Provision of Information to ZHD Group" (opens new window) (only available in Japanese) (hereafter called individual terms and conditions), which was announced on July 5, 2022, to March 8, 2023.

Item Before change After change
Scheduled effective date October 5, 2022 JST (GMT+9) March 8, 2023 JST (GMT+9)

For more information about individual terms and conditions, see the news from July 5, 2022, [Updated] Establishment of "Individual Terms and Conditions for Provision of Information to ZHD Group".

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

2022/09/28

"Feature for getting statistics per aggregation unit" is now available in the Messaging API

"Feature for getting statistics per aggregation unit," which was previously an option for corporate customers, is now a feature of the Messaging API and can be used by anyone.

# Overview

This feature enables you to aggregate statistics per unit when sending push messages and multicast messages with the same content to multiple end users.

Previously, 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. From now on, by assigning a unit name to the customAggregationUnits property when sending the message with push messages or multicast messages, you can get statistics on a per-unit basis.

Aggregating statistics per unit

For more information, see Get statistics per aggregation unit in the Messaging API documentation.

# Available endpoints

The following endpoints are now available in the Messaging API:

2022/09/28

LINE Conversion API is now available

The LINE Conversion API (opens new window) is now available.

Using the LINE Conversion API, it's possible to send user information and event data directly from the advertiser's server to the LINE's server.

For more information about the LINE Conversion API, see LINE Conversion API (opens new window) (only available in Japanese) on LINE DATA SOLUTION and LINE Conversion API development guidelines (opens new window).

2022/09/22

[Resolved] Notice about service outage for the LINE MINI App in Taiwan

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

# Date and time of outage

September 15, 2022 around 12:05 - September 20, 2022 around 21:44 JST (GMT+9)

# Impact

Sending service messages

# Details

If you tried to send a service message using a "Traditional Chinese" service message template, the request wasn't processed properly, resulting in a Not allowed template error with status code 403.

We'll continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

2022/09/21

[Updated] Messaging API template messages are now available for the desktop version of LINE

Updated on September 29, 2022

Template messages are now available for the desktop version of LINE.

Updated on September 22, 2022

Due to a problem with supporting for the desktop version of LINE, we've reverted template messages to the state before the specification change. We'll make a new announcement when the support for the desktop version of LINE is completed.

Updated on September 21, 2022 21:00

Some template messages aren't displaying properly on the desktop version of LINE. We apologize for any inconvenience.

Messaging API template messages are now available for the desktop version of LINE (macOS and Windows).

Previously, template messages were only supported on LINE for iOS and LINE for Android, but now they are also supported on the desktop version of LINE. The changes and versions covered by this support are as follows:

These changes don't apply to template messages sent by liff.sendMessages() and liff.shareTargetPicker() in LIFF.

About Template Messages that have already been sent

Template messages that have already been sent aren't affected by the changes. Only template messages sent after the changes will be affected by the changes.

# Change of display

There are some minor partial changes in the display of template messages as a result of the support for the desktop version of LINE. The layout and the actions to be specified aren't affected by the changes.

# Sending GIF images

The imageUrl and thumbnailImageUrl properties of template messages don't support GIF format images. However, in the past, when a template message was sent with a GIF format image, the GIF animation would be played in some cases.

After the changes, GIF format images will no longer be displayed correctly even if GIF format images are specified in the template message.

Images in unsupported file formats may not display properly

The imageUrl and thumbnailImageUrl properties of template messages support JPEG or PNG format images.

# Target version

The target LINE versions for which changes has been made are as follows:

OS Target version
iOS All versions
Android All versions
macOS 7.8.1 or later
Windows 7.8.1 or later
2022/09/08

The documentation and development guidelines for LINE Ads API are now available

The documentation and development guidelines for LINE Ads API are now available.

For more information, see About LINE Ads API in the LINE Ads API documentation.

Use of the LINE Ads API requires an application

The LINE Ads API can only be used by corporate users who have submitted the required applications. To use it with your LINE Ads Account, apply for authorization in the LINE Ads Manager. For more information, see Using LINE Ads API (opens new window) (only available in Japanese) in LINE for Business.

2022/09/05

LIFF v2.21.1 released

We've released LIFF v2.21.1.

In LIFF v2.21.1, we've refactored the LIFF 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), you'll automatically update LIFF to v2.21.1.

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

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

2022/09/01

We've published "The differences between LIFF browser and external browser"

We've published "The differences between LIFF browser and external browser" in the LIFF documentation.

The LIFF browser doesn't support some of the web technologies supported by external browsers. In "The differences between LIFF browser and external browser", you can find the web technologies that aren't supported by the LIFF browser.

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.

2022/08/17

Users can now cancel sending messages in one-on-one chats with LINE Official Accounts

In one-on-one chats between users and LINE Official Accounts, users (excluding users in Thailand and Taiwan) can now cancel sending messages.

Accordingly, in the Messaging API webhooks, the object included in the source of unsend events (the source property) will change to include users, in addition to the existing group chats and multi-person chats.

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

Item Before change After change
Source of unsend event (the source property)

If you've displayed the message on your own management screen after a message event is received by the bot server, we recommend that you cancel displaying the message when the bot server receives the unsend event.

For more information, see Unsend event in the Messaging API reference.

2022/08/15

More properties are available in the LIFF server API

The following properties are now available in the LIFF server API:

  • features.qrCode
  • scope
  • botPrompt

Now you can set 2D code readers, scopes and bot link features via the LIFF server API, which previously could only be set via the LINE Developers Console.

In addition, the Get all LIFF apps endpoint response now includes these properties so that the configuration status of each LIFF app can be checked.

For more information, see Server API reference.

2022/08/08

In the LINE MINI App, we've changed our policy on user inducement to external services

In the LINE MINI App, we've changed our policy on user inducement to external services.

Previously, we prohibited in principle to direct users to external services in the LINE MINI App. This policy change allows users to be directed to external websites and native apps when certain conditions are met.

Even after changing the policy, the main features of the LINE MINI App to be published must be provided within the LINE MINI App.

# Directing to external websites

In the process of using the main features of the LINE MINI App, you can temporarily direct the user to external websites. For example, in the following cases:

  • Transaction and authentication

When using services or information that aren't the primary function of the LINE MINI App, you can direct the user to external websites. For example, in the following cases:

  • Present privacy policies and terms of use
  • Introduce the company's official website

# Directing to other native apps

As a general rule, directing users to other native apps is prohibited. However, only the following native apps are allowed:

  • Apps pre-installed on the device
  • PayPay (only for temporary inducements to use the payment function)
  • Instagram, Twitter, Facebook, TikTok, Google Maps

For more information about policy on user inducement to external services, see On User Inducement in the LINE MINI App Policy.

2022/08/04

LIFF v2.21.0 released

We've released LIFF v2.21.0.

In LIFF v2.21.0, we've added and improved the following features:

# The text displayed by the LIFF SDK now supports multiple languages

The text displayed by the LIFF SDK now supports multiple languages. This means that each text displayed by the LIFF SDK will be displayed in the user's language obtained from navigator.language (opens new window).

However, at this time, no translations have been applied, so all of the text will be displayed in English. Translation will be applied gradually.

# The language of the text displayed by the LIFF SDK can now be specified

We've added the liff.i18n.setLang() method, through which you can specify the language of the text displayed by the LIFF SDK. With the liff.i18n.setLang() method, the text of the LIFF SDK will be displayed in a specified language, regardless of the users's language.

liff.i18n.setLang("en");

Text with no translation isn't affected by this method.

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

# We've fixed a bug where the liff.init() method could succeed with an invalid LIFF ID

There was a bug where the liff.init() could succeed with an invalid LIFF ID. In LIFF v2.21.0, this bug was fixed so that the liff.init() method fails with an invalid LIFF ID.

# The Typescript type definition for profile information retrieved by the liff.getProfile() method is now available

In the npm package of the LIFF SDK, the Typescript type definition for profile information retrieved by the liff.getProfile() method is now available. You can import the Profile type from the @liff/get-profile package.

import { Profile } from "@liff/get-profile";
2022/08/04

In the LIFF browser on LINE version 12.13.0 or later, we'll change the specifications for transitions to the external site and the LIFF-to-LIFF transition

In the LIFF browser on LINE version 12.13.0 or later, we'll change the specifications as follows:

# Display a popup when moving to an external site

When opening an external site that isn't a non-LIFF app from a LIFF app opened in the LIFF browser, a popup will appear indicating that "This is an external page".

A popup when moving to an external site

The popup will only appear when opening the external site in the same window. If the external site is opened in a different window, the popup doesn't appear.

Displaying the popup will be applied gradually to users who are using LINE version 12.13.0 or later.

# Changes to the specifications for the LIFF-to-LIFF transition

The specification for LIFF-to-LIFF transitions in LIFF URL will be changed as follows. The same applies to LIFF URLs with additional path or query parameters.

For more information about LIFF URL, see Opening a LIFF app in the LIFF documentation. Note that the LIFF-to-LIFF transition using the endpoint URL isn't subject to this specification change.

# The screen transitions on the LIFF-to-LIFF transition become smoother

Login processing by liff.login(), which used to be executed automatically when transitioning between LIFF apps, is no longer performed. The screen transitions are smoother because redirects don't occur during the LIFF-to-LIFF transition.

# The "liff.sendMessages()" method can also be used in the transition destination LIFF app

On LINE versions earlier than 12.13.0, after transitioning from LIFF A to LIFF B, the chat_message.write scope will be disabled in LIFF B, and the channel consent screen won't be displayed either.

On LINE version 12.13.0 or later, the chat_message.write scope of LIFF B is enabled. The liff.sendMessages() method is also available in LIFF B.

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

2022/07/28

In the LINE Developers Console, we've reorganized the tabs of the LINE MINI App channel

In the LINE Developers Console, the tab name of the LINE MINI App channel has been changed, input fields have been moved and other changes have been made.

The LINE MINI App channel allows you to input and check information related to the LINE MINI App. In the past, the tab name in the LINE MINI App channel made it difficult to imagine the contents of the tab.

This change has made it easier to manage the LINE MINI App channel.

# Changes

The following three main changes were made:

  1. Changed the tab name
  2. Moved the Function category to the Basic settings tab
  3. Changed the input field of reference materials for review

# 1. Changed the tab name

In the LINE MINI App channel, the tab name has been changed as follows:

Language Before changes After changes
Japanese LINEミニアプリ 事業情報
English LINE MINI App Business information

LINE MINI App channel tab

# 2. Moved the Function category to the Basic settings tab

Along with the tab name change, the input field for the Function category has been moved from the previous LINE MINI App tab to the Basic settings tab.

# 3. Changed the input field of reference materials for review

The existing Additional files in the LINE MINI App tab and the Content to be referenced during the review in the Workflow tab have been merged into the Reference materials for the review in the Workflow tab.

In the Reference materials for the review, you can attach, for example, materials that give an overview of the project. However, don't attach any material that constitutes personal or confidential information to the Reference materials for review.

For more information about the LINE MINI App, see LINE MINI App documentation.

2022/07/28

[Resolved] Notice about service outage for the Messaging API

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

July 28, 2022 around 5:29 - around 5:49 JST (GMT+9)

# Cause of the outage

Server failure

# Impact

# Details

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

  • Some requests weren't processed properly, resulting in errors with status code 5xx.
  • Messages may not have been actually sent in some requests that succeeded and returned a status code 200 when making a request to the above 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 will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

2022/07/21

On LINE for iOS version 12.12.0 or later, we'll be making changes to some of LIFF browser's minimization specifications

We'll be making changes to some of LIFF browser's minimization specifications as announced in the news from June 2, 2022.

# Target version

LINE for iOS version 12.12.0 or later

# Changes

# Changes to closing a minimized LIFF browser

In addition to the current way of swiping a LIFF browser off the screen, you can also close a LIFF browser in the following way:

Closing a minimized LIFF browser

Dragging a minimized LIFF browser shows the close icon at the bottom of the screen. Drag the minimized LIFF browser to the close icon and release your finger.

# Changes to the Japanese notation of the action button's options

Changes to the Japanese notation of the action button's options are as follows:

LINE for iOS version earlier than 12.12.0 LINE for iOS version 12.12.0 or later
画面を小さく表示 閲覧中のページを最小化

For more information on LIFF browser minimization, see Minimizing LIFF browser in the LIFF documentation.

2022/07/06

LIFF v2.20.3 released

We've released LIFF v2.20.3.

In LIFF v2.20.3, we've fixed the following bug.

# An alert is now displayed after auto login as a temporary measure to solve a bug that auto login on external browsers on Android doesn't work properly

There were instances where auto login on external browsers on Android didn't work properly. As a temporary measure, the following alert is now displayed after auto login on external browsers on Android:

Login successfully!

We plan to improve the display of the alert in a future update of the LIFF SDK.

# How to update to LIFF v2.20.3

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

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

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

2022/07/05

[Updated] Establishment of "Individual Terms and Conditions for Provision of Information to ZHD Group"

Added on October 3, 2022
Added on September 8, 2022

The scheduled effective date was announced as October 3, 2022, but has been changed to October 5, 2022.

As of March 8, 2023, consent to the "Individual Terms and Conditions for Provision of Information to ZHD Group" (opens new window) (only available in Japanese) (hereafter called individual terms and conditions) will be required for certain channels. When creating a new channel or selecting an existing channel in the LINE Developers Console, a consent screen will appear. Confirm the content displayed and consent to the individual terms and conditions.

# Target channels

Consent is required for the following channels linked to the LINE Official Account in Japan:

  • Messaging API channel
  • Blockchain Service channel

# Notes for existing channels

For existing channels, regardless of the developer's channel roles, the individual terms and conditions consent screen will be displayed when a developer registered on the target channel selects the target channel in the LINE Developers Console.

Even if the developer doesn't consent to the individual terms and conditions, Messaging API functions such as sending messages and Webhooks are still available, but you can't proceed to the settings screens in the LINE Developers Console, such as Basic settings and Messaging API settings.

You only need to consent to the individual terms and conditions once per channel. If multiple developers are registered for a single channel, once one developer has consented, the consent screen won't be displayed thereafter. Also, if you've already consented to the individual terms and conditions by selecting the LINE Official Account linked to the target channel in the LINE Official Account Manager (opens new window) or the LINE Official Account Manager App, the consent screen won't be displayed in the LINE Developers Console.

# Scheduled effective date

March 8, 2023 JST (GMT+9)

The details and date are subject to change without notice.

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

2022/06/29

TLS 1.0 and TLS 1.1 support for LINE Developers site has been discontinued

As of June 29, 2022, TLS 1.0 and TLS 1.1 support for LINE Developers site has been discontinued.

# Target site

LINE Developers site (including LINE Developers Console and Flex Message Simulator)

# Supported SSL/TLS protocol versions

We no longer support TLS 1.0 and TLS 1.1. We will continue to support TLS 1.2 or higher.

# End-of-support date

June 29, 2022 JST (GMT+9)

# Impact

LINE Developers site will become sequentially unavailable with older browsers, computers, and smartphones. If your environment only supports TLS 1.1 or lower, upgrade your OS, browser, etc. so that you can continue to access using TLS 1.2 or higher.

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

2022/06/17

[Resolved] Notice about service outage for the LINE MINI App

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

# Period of outage

May 11, 2022 - May 18, 2022 JST (GMT+9)

# Impact

There was a problem with some users who met all of these conditions:

  • A user was using LINE for Android.
  • A user was using LINE version 12.7.0.
  • A user had added LINE MINI Apps to the "Pinned services" of the LINE Home tab.

# Details

In the LINE Home tab, there was an issue that caused LINE MINI Apps to be unpinned if the user had added the LINE MINI Apps to the "Pinned services". This issue has been resolved in the LINE for Android version 12.7.1 or later, which has been available since May 18, 2022.

In order to re-pin the LINE MINI Apps that have been unpinned, the user needs to re-add the LINE MINI Apps to the "Pinned services". Users affected by this issue will be notified individually via service messages.

We'll continue to improve the quality of its services to prevent future outages. Thank you for your understanding.

2022/06/08

LIFF v2.20.2 released

We've released LIFF v2.20.2.

In LIFF v2.20.2, we've made internal improvements.

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

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

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

2022/06/03

The endpoint for getting user information has been added to the LINE Login

We've added an endpoint for getting user information to the LINE Login.

LINE Login supports OpenID Connect Discovery 1.0 (opens new window) and information about the OpenID provider is available in the OpenID Provider Configuration Document (opens new window). With the addition of the endpoint, we've also updated this document, including the addition of userinfo_endpoint property.

# Added endpoint

For more information on LINE Login, see LINE Login overview.

2022/06/02

LIFF browser can now be minimized on LINE for iOS version 12.8.0 or later

A LIFF browser opened in a chat room can now be minimized on LINE for iOS version 12.8.0 or later.

LIFF browser minimization

Previously, when viewing a LIFF browser in a chat room, the user had to close the LIFF browser to perform another action, such as sending a message to the chat room. To return to the LIFF browser after performing the action, the user had to reopen the LIFF browser.

On LINE for iOS version 12.8.0 or later, the user no longer need to close a LIFF browser to perform another action. By minimizing the LIFF browser, the user can suspend viewing the LIFF browser and perform the action. After performing the action, the user can resume viewing the LIFF browser by maximizing the LIFF browser.

# Conditions of use for LIFF browser minimization

To minimize a LIFF browser, the following conditions must be met:

  • LINE for iOS version 12.8.0 or later
  • Full is specified as the screen size for your LIFF app
  • chat_message.write scope is off for your LIFF app
  • The LIFF browser isn't overlapping on another modal
The LIFF app after LIFF-to-LIFF transition must meet the conditions of use

To minimize the LIFF browser after LIFF-to-LIFF transition, the LIFF app after transition must meet the conditions of use.

For example, as described in Behavior based on screen size of the LIFF app in the LIFF documentation, the LIFF app after transition will be displayed in Full, regardless of the screen size specified. However, if Tall or Compact is specified as the screen size for the LIFF app after transition, the LIFF app after transition won't satisfy the conditions of use for LIFF browser minimization.

LIFF browser minimization will be available on LINE for iPadOS and Android, but the date is yet to be determined.

For more information on minimizing LIFF browser, see Minimizing LIFF browser in the LIFF documentation.

2022/06/01

The notation of "Region" of LINE Login channel and LINE MINI App channel has been changed on the LINE Developers Console

We've changed the notation of Region in the channel settings of LINE Login channel and LINE MINI App channel on the LINE Developers Console.

# Changes

The changes are as follows:

Channel Before changes After changes
LINE Login channel Region Region to provide the service
LINE MINI App channel Region Region to provide the service

You don't need to change the channel settings with these changes.

2022/06/01

In Japan, the pre-examination for LINE MINI Apps has been eliminated, making it easier to start development

We've made the following two changes to the process of releasing LINE MINI Apps in Japan:

  1. The pre-examination has been eliminated
  2. The submission of a PSD file of the icon is no longer required

By providing your service as a LINE MINI App, your users can use the service without downloading the service app. In addition, notifications of services offered on your LINE MINI App can be sent as Service Messages free of charge, which will improve the user experience.

Until now, there have been two processes involved in the release of LINE MINI Apps: a pre-examination prior to development (LINE MINI App Development Program) and a release review prior to the release of LINE MINI Apps. With this change, the pre-examination has been eliminated.

In addition, the submission of PSD file of the icon, which was previously required, is no longer necessary. These changes have made it easier to start developing LINE MINI Apps.

Creating LINE MINI App channel

If you are unable to create a LINE MINI App channel even though your service area is Japan, try the following:

For more information on the process of developing and publishing LINE MINI Apps, see Overall Process.

# Notes on LINE MINI App development

Note the following three points regarding changes to the process of publishing in the LINE MINI Apps:

  1. Include the correct service description in the channel description
  2. Check the LINE MINI App policy
  3. Create your icons according to the guidelines

# 1. Include the correct service description in the channel description

With the elimination of the pre-examination, it's no longer necessary to submit a proposal. For this reason, during the release review process, the Channel description on the Basic settings tab of the LINE Developers Console will be checked in order to understand the contents of the service. Make sure to enter the correct service description in the Channel description.

Channel description

For more information about channel description, see Channel description.

# 2. Check the LINE MINI App policy

With the elimination of the pre-examination, the only opportunity to confirm whether or not your application can be released as a LINE MINI App is the release review. Check the LINE MINI App policy when considering releasing your application as a LINE MINI App.

Also, for more information on the most frequently asked questions about the planning, examination and development of LINE MINI Apps, see LINE MINI Apps (opens new window) (only available in Japanese) in LINE for Business.

Contact for inquiries regarding the release of LINE MINI Apps

If, after checking the above, you're still unsure whether the service you are considering is suitable for release as a LINE MINI App, see How can I check whether my service project is eligible for release before developing a LINE MINI App (opens new window) (only available in Japanese).

Note that the above page is only for those who intend to release LINE MINI Apps in Japan. The above page can only be used to check if the contents of the LINE MINI Apps you are planning to release are releasable.

# 3. Create your icons according to the guidelines

In the LINE MINI App, it's no longer necessary to submit PSD files for icon, which was previously required.

Although the submission of PSD file is no longer required, continue to use the icon template and follow the guidelines to create icon that are easily recognizable by users.

For more information on icon template and guidelines, see Creating a LINE MINI App icon.

2022/05/26

With the enforcement of Thailand's Personal Data Protection Act, the specifications of some features have been changed in the Messaging API

Thailand's Personal Data Protection Act is scheduled to be enforced on June 1, 2022. Accordingly, as announced on May 17, 2022, we've changed the specifications of some features in the Messaging API. The specification changes only apply to Thai users and the Thai LINE Official Accounts.

# Changes

The changes are as follows:

API Changes
Send narrowcast message When you filter recipients by certain conditions, users under the age of 20 in Thailand will be excluded.
Get friend demographics When you retrieve the demographic information of a Thai LINE Official Account, the percentages with ages[].age values of from0to14 and from15to19 won't be included in the response. Users under the age of 20 will be counted as unknown.
When sending narrowcast messages, existing audiences are also subject to the specification changes

Even if you use an audience created before the specification change, users under the age of 20 in Thailand may be excluded.

LINE will continue to work on further improving our services to our customers. Thank you for your understanding and cooperation.

2022/05/24

[Updated] LIFF v2.20.1 released

Added on May 25, 2022

The problem that the npm package for LIFF v2.20.1 can't be installed due to a bug on the npm side has been resolved.

For more information, see the npm status page (opens new window).

We've released LIFF v2.20.1.

In LIFF v2.20.1, we've made the following improvement.

# An error is now returned when executing the liff.scanCodeV2() method in an external browser without login

To execute the liff.scanCodeV2() method, user login is required.

In LIFF v2.19.1 or earlier, when executing the liff.scanCodeV2() method in an external browser without login, a sub-window will open and show a blank page. Also, the Promise will remain pending.

In LIFF 2.20.1, the sub-window will no longer open in the above case. Also, the Promise will be rejected and LiffError will be passed.

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

LIFF v2.20.0 has been deprecated

LIFF v2.20.0 has been deprecated due to a bug where some users using an external browser on Android can't log in. If you are using LIFF v2.20.0, update to LIFF v2.20.1.

2022/05/20

LINE MINI Apps now appear in "Siri Suggestions"

LINE MINI Apps now appear in "Siri Suggestions" on iPhone.

What is "Siri Suggestions"

This feature suggests shortcuts or provides suggestions based on the user's routines and app usage by Siri. For more information, see Siri Suggestions on iPhone (opens new window) in Apple Support.

# Conditions for LINE MINI Apps to appear in "Siri Suggestions"

LINE MINI Apps appear in "Siri Suggestions" when all of the following conditions are met:

  • A user uses LINE for iOS.
  • A user have turned on "Siri Suggestions" in device settings
  • A user have turned on "Siri Shortcuts" in the LINE Settings
  • A User is using LINE MINI Apps.
  • LINE version is 12.7.0 or later.

If the conditions are met, the LINE MINI Apps will be displayed automatically, so there is no need for the service providers offering the LINE MINI Apps to take any action. Conversely, it is not possible for the service providers to disable the display of LINE MINI Apps in "Siri Suggestions".

2022/05/17

With the enforcement of Thailand’s Personal Data Protection Act, as of late May 2022, the specifications of some features will be changed in the Messaging API

Thailand’s Personal Data Protection Act is scheduled to be enforced on June 1, 2022. Accordingly, we plan to change the specifications in the Messaging API for sending messages using attribute information and retargeting, and for retrieving demographic information. These specification changes only apply to Thai users and the Thai LINE Official Accounts.

# Scheduled date of change

Late May 2022

The date and time are subject to change without notice.

# Changes

The changes are as follows:

API Changes
Send narrowcast message When you filter recipients by certain conditions, users under the age of 20 in Thailand will be excluded.
Get friend demographics When you retrieve the demographic information of a Thai LINE Official Account, the percentages with ages[].age values of from0to14 and from15to19 won't be included in the response. Users under the age of 20 will be counted as unknown.

LINE will continue to work on further improving our services to our customers. Thank you for your understanding and cooperation.

2022/05/13

[Updated] Added features such as automatic opening and closing of the rich menu when tapping a rich menu

Added on May 18, 2022

We've updated the Target version.

In postback action of the Messaging API, we've added features to open and close a rich menu and open keyboard and voice message input mode based on user action.

Previously, when a user tapped on a rich menu and messages were sent from the LINE Official Account, these messages would overlap the rich menu, making them difficult to read. With this new feature, the rich menu can now be automatically closed when the user taps on the rich menu.

# Added display methods

With this new addition, the following display methods can be specified depending on user action:

  • Close rich menu
  • Open rich menu
  • Open keyboard
  • Open voice message input mode

# Added properties

The following two properties have been added to the postback action of an action object in conjunction with these features addition.

Property name Type Summary
inputOption String

The display method of such as rich menu based on user action. Specify one of the following values:

  • closeRichMenu: Close rich menu
  • openRichMenu: Open rich menu
  • openKeyboard: Open keyboard
  • openVoice: Open voice message input mode
fillInText String String to be pre-filled in the input field when the keyboard is opened. Valid only when the inputOption property is set to openKeyboard. The string can be broken by a newline character (\n).
Max character limit: 300

# Example of postback action object

For example, suppose the user taps a control with a postback action object such as the following. At this time, the user's keyboard is automatically opened. In addition, the input field will be pre-filled with the string specified by fillInText.

{
  "type": "postback",
  "label": "Buy",
  "data": "action=buy&itemid=123",
  "displayText": "Buy",
  "inputOption": "openKeyboard",
  "fillInText": "---\nName: \nPhone: \nBirthday: \n---"
}

# Target version

These added features are available on LINE version 12.6.0 or later for iOS or Android.

2022/04/27

LINE Developers Thailand is now available

LINE Developers Thailand is now available. This site provides LINE API development methods and know-how for developers in Thailand.

If you'd like to learn about LINE API in Thai, try out LINE Developers Thailand.

2022/04/26

LINE Login v2.1 is recommended as we'll implement LINE's Two-factor Authentication Switch function

From the upcoming release of LINE for smartphones version 12.7.0, the Two-factor Authentication Switch function will be added to allow users to enable or disable two-factor authentication (2FA).

This allows users to choose whether to enable two-factor authentication when they log in to a service that uses LINE Login v2.1.

The Two-factor Authentication Switch function is not available for LINE Login v1.0 and LINE Login v2.0, so we recommend updating to LINE Login v2.1.

# Date of implementation of Two-factor Authentication Switch function

May 2022 (LINE for smartphones version 12.7.0 or later)

The date is subject to change without notice.

# What is two-factor authentication?

Two-factor authentication is a method to authenticate a user using two elements: knowledge known only to the user (such as a password), the user's property (such as an IC card or a smartphone), and biometric authentication. Two-factor authentication increases the possibility of preventing unauthorized logins even if a password is known to a third party.

LINE Login performs two-factor authentication by password authentication for the LINE account and entering the verification code displayed on the smartphone's LINE screen.

If the user logs in to the service for the first time, or if the device, browser, or IP address changes, the user is prompted to enter the verification code after entering the password.

The flow of two-factor authentication

# Requirements for using the Two-factor Authentication Switch function

The Two-factor Authentication Switch function allows users to choose whether to use two-factor authentication when logging in to services that use LINE Login.

However, the Two-factor Authentication Switch only applies to sites that don't have two-factor authentication applied on the server side. For sites that have already applied two-factor authentication, the user will always log in using two-factor authentication.

To use the Two-factor Authentication Switch function, the following requirements must be met:

Scope Requirement
Services that use LINE Login Use LINE Login v2.1
Users Use LINE for smartphones version 12.7.0 or later

This function is not available in LINE Login v1.0 (end-of-life) and LINE Login v2.0 (deprecated), so we recommend updating to LINE Login v2.1

For more information about the differences between the versions, see LINE Login versions in LINE Login documentation.

# Behavior when the Two-factor Authentication Switch function is enabled

The Two-factor Authentication Switch function can be activated by tapping Home > Settings > Accounts in LINE and turning the Two-factor authentication toggle switch to "ON" (right).

Two-factor authentication

The behavior when the user turns the switch on and off is as follows:

Websites that haven't applied 2FA Websites that have already applied 2FA
ON Enable two-factor authentication Always enable two-factor authentication
OFF Disable two-factor authentication Always enable two-factor authentication

The default setting after the implementation of the function is "OFF", and the users can use the service as before.

# Notes after implementation

The notes after enabling the Two-factor Authentication Switch function are as follows:

  • When you log in for the first time, you need a smartphone with LINE installed.
  • You won't need to enter the verification code for one year, since the trusted status will continue for one year.
  • If the service is used by a typical LINE user, the impact of the implementation of the Two-factor Authentication Switch function is expected to be small since the user has a smartphone. On the other hand, in cases where accounts are shared and managed for business purposes, etc., you need to be careful in advance because you need to operate the smartphone that uses the LINE account.
2022/04/25

Create LIFF App, a CLI tool for building a development environment for LIFF apps, released

We've released Create LIFF App, a CLI tool that allows developers to build a development environment for LIFF apps to help developers develop LIFF apps more smoothly.

# What is Create LIFF App

Create LIFF App is a CLI tool that allows you to build a development environment for LIFF apps with a single command, like Create React App (opens new window) by React or Create Next App (opens new window) by Next.js. Answering questions from Create LIFF App generates the environment, including the LIFF app template, so you can start development immediately.

The following languages and frameworks are currently available for Create LIFF App. For example, you can generate Next.js source code written in TypeScript.

# Languages that can be generated by the Create LIFF App

  • JavaScript
  • TypeScript

# Frameworks that can be generated with Create LIFF App

For more information about Create LIFF App, see Building a LIFF app development environment with Create LIFF App in the LIFF documentation.

For more information on the differences between the LIFF starter app and LIFF Playground and Create LIFF App, see Tools to support LIFF app development.

2022/04/25

LIFF Inspector and LIFF Mock released

As announced on April 18, 2022, we've released LIFF plugins: LIFF Inspector and LIFF Mock.

# LIFF Inspector

LIFF Inspector is a LIFF plugin to debug your LIFF app. Using LIFF Inspector, you can debug your LIFF app with Chrome DevTools (opens new window) on a different PC than the device on which you are running the LIFF app.

# LIFF Mock

LIFF Mock is a LIFF plugin to make testing your LIFF app easy. Using LIFF Mock, you can add the mock mode to the LIFF SDK. In the mock mode, your LIFF app is independent of the LIFF server and the LIFF API returns mock data. Therefore, you can perform unit testing or load testing more easily.

For more information on LIFF plugin, see LIFF plugin in the LIFF documentation.

2022/04/19

In the Messaging API, a feature to redeliver webhooks that fail to be received has been added

As announced on March 7, 2022, we've added the webhook redelivery feature to the Messaging API.

When a user sends a message to a LINE Official Account, the webhook is sent to the bot server according to the event. This webhook has only been sent once, but we've added a feature to redeliver it. In addition, common properties have been added to webhook event objects.

# Overview

We've added the following three main features.

  1. Add the webhook redelivery feature
  2. Add common properties to webhook event objects
  3. Publish error statistics aggregation

# 1. Add the webhook redelivery feature

If the bot server does not return a status code in the 2xx for a webhook sent from the LINE Platform, the webhook will redeliver from the LINE Platform after a period of time.

This feature is disabled by default and can be enabled from the LINE Developers Console. It is available for all Messaging API channels.

Note

Be sure to check Notes before enabling the webhook redelivery feature.

For more information about the webhook redelivery feature, see Redeliver a webhook that failed to be received in the Messaging API documentation.

# 2. Add common properties to webhook event objects

The following two properties were added as common properties of webhook event objects. These properties will be included in the webhook event objects regardless of whether the webhook redelivery feature is enabled or not.

# Added common properties
Property name Type Summary
webhookEventId String Webhook Event ID, an ID that uniquely identifies a webhook event
deliveryContext.isRedelivery Boolean Whether the webhook event is a redelivered one or not

# 3. Publish error statistics aggregation

A feature to check the statistics of errors in webhooks sent has been published in the LINE Developers Console.

In enabling the webhook redelivery feature, there may be a need to check the status of webhooks sent that were not received by the bot server. Error statistics aggregation was previously available only to corporate users, but with this release, they are now available for all Messaging API channels.

For more information about error statistics aggregation, see Check error statistics for sending webhooks in the Messaging API documentation.

# Notes

Before enabling the webhook redelivery feature, check the following notes:

  • Due to network routing problems and other factors, duplicate webhook events may be sent. If this is an issue, use webhookEventId in the webhook event objects to detect duplicates.
  • If webhook events are redelivered, the order in which webhook events occur and the order in which they reach the bot server can be different significantly. If this is an issue, check the context by looking at the timestamp of webhook event objects.
  • The webhook redelivery feature does not guarantee reliable redelivery of webhooks. In addition, if the number of webhook redeliveries increases significantly in a short period of time and it is determined that it will affect the operation of the LINE Platform, the webhook redelivery setting may be forcibly disabled.
  • The number and interval of the webhook redelivery are not disclosed. In addition, the number of times and intervals are subject to change without notice.
  • Webhook sending may be suspended for bot servers that have been failing to receive webhooks for a long period of time.
2022/04/19

Basic authentication is now available for LINE MINI App

Basic authentication is now available for LINE MINI Apps with the status "Developing" or "Reviewing". You can restrict access to pre-publishing LINE MINI Apps by using basic authentication.

# How to use basic authentication

In the LIFF tab on the LINE Developers Console, specify the URL with basic authentication in the Endpoint URL for Developing or Review. Then open the LINE MINI App in the LIFF browser and a dialog box will appear prompting you to enter your username and password.

Basic authentication screen

# Conditions for basic authentication

Basic authentication is available when all of the following conditions are met:

  • The status of your LINE MINI App is "Developing" or "Reviewing".
  • LINE version is 12.2.0 or later.
  • LINE MINI App is open in LIFF Browser.

Basic authentication isn't available for LIFF Apps and LINE MINI Apps whose status is "Published". Also, you can't use digest authentication.

When basic authentication isn't available even though the conditions are met

Basic authentication isn't available in a LINE MINI App after a LIFF-to-LIFF transition. For more information, see Opening a LIFF app from another LIFF app (LIFF-to-LIFF transition) in the LIFF documentation.

For more information about basic authentication specifications on LIFF browser, see LIFF browser specifications in the LIFF documentation.

# Notes on using basic authentication

Basic authentication is an authentication method used for simple access restrictions, and developers of LINE MINI Apps should evaluate and judge for themselves whether basic authentication meets their security requirements before using it.

The addition of this functionality doesn't recommend the use of basic authentication, nor does it guarantee the security of access restrictions based on basic authentication.

For more information, see Use basic authentication to restrict access to your LINE MINI App before it is released in the LINE MINI App documentation.

2022/04/18

[Updated] LIFF v2.19.1 released

Added on April 25, 2022

As previously announced, we've released LIFF Inspector and LIFF Mock today. For more information, see the news from April 25, 2022, LIFF Inspector and LIFF Mock released.

We've released LIFF v2.19.1.

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

# We've added the LIFF plugin feature that can extend the LIFF SDK

We've added the LIFF plugin feature introduced in the session entitled "For Improvement of Developer Experience of All LIFF App Developers (opens new window)" at LINE DEVELOPER DAY 2021, held last November.

LIFF plugin is a feature to extend the LIFF SDK. Using a LIFF plugin, you can add your own APIs to the LIFF SDK or change the behavior of LIFF APIs.

Also, as previously announced, the following LIFF plugins are now available:

# LIFF Inspector

LIFF Inspector is a LIFF plugin to debug your LIFF app. Using LIFF Inspector, you can debug your LIFF app with Chrome DevTools (opens new window) on a different PC than the device on which you are running the LIFF app.

# LIFF Mock

LIFF Mock is a LIFF plugin to make testing your LIFF app easy. Using LIFF Mock, you can add the mock mode to the LIFF SDK. In the mock mode, your LIFF app is independent of the LIFF server and the LIFF API returns mock data. Therefore, you can perform unit testing or load testing more easily.

For more information on LIFF plugin, see LIFF plugin in the LIFF documentation.

2022/04/11

LINE Login security checklist released

We've released LINE Login security checklist.

When developing an application using LINE Login, you must prepare for potential attacks by third parties and implement the login function without any security flaws.

The security checklist contains information that should be kept in mind when using LINE Login. You can check for any security flaws in your application by utilizing the security checklist.

Be sure to build a safe system with an understanding of the purpose of the checklist

The security checklist contains excerpts of points that require special attention when using LINE Login. Conforming to the contents of the checklist does not guarantee security. Be sure to build a safe system with a full understanding of the dangers.

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.

2022/04/05

The endpoint for validating rich menu object has been added

We've added an endpoint for validating a rich menu object to the Messaging API.

Previously, when checking that a rich menu object is valid, you must execute create rich menu endpoint. However, this method creates a rich menu if a rich menu object is valid.

By using the newly added endpoint, you can validate that a rich menu object is valid without creating a rich menu.

# Added endpoint

For more information about creating rich menu, see Creating rich menus with the Messaging API in the Messaging API documentation.

2022/04/01

[Resolved] Notice about service outage for the Messaging API

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

March 30, 2022 around 14:47 - around 20:51 JST (GMT+9)

# Cause of the outage

Server failure

# Impact

Get bot info

# Details

If developers hasn't set a profile image for the bot, the profile image URL (pictureUrl) is not included in the response when you're using the target endpoint.

However, during the stated date and time, when you get a bot's basic information at the target endpoint, even if developers haven't set a profile image for the bot, the response was returning https://profile.line-scdn.net as the value of the profile image URL (pictureUrl).

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

2022/04/01

"LINE original unicode emojis" of the Messaging API has been discontinued as of March 31, 2022

As announced on November 30, 2021 and February 28, 2022, "LINE original unicode emojis" has been end-of-life as of March 31, 2022.

# Date of discontinuation

2022/3/31 JST (GMT+9)

# Impact

"LINE original unicode emojis" will no longer be displayed sequentially. This change will take place without notice after March 31, 2022, but the date is yet to be determined. This change will also apply 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

The appearance after discontinuation may change without notice.

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

2022/03/31

Messaging API maintenance notice

Maintenance is scheduled for the Messaging API. We sincerely apologize for any inconvenience that this may cause and thank you for your understanding.

# Date and time of maintenance

April 7, 2022 21:00 - 24:00 JST (GMT+9)

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

# Impact

During the maintenance, updating of user interaction statistics will be delayed. Therefore, the following APIs may return statistics that don't reflect the most recent user interaction. To get the updated statistics, make another request after the maintenance is completed.

2022/03/24

The design of the channel consent screen has been changed

As announced on March 9, 2022, we've changed the design of the channel consent screen.

This design change includes the change to display the Company or owner's country or region for a channel on the channel consent screen.

With the design change of the channel consent screen, configure the company or owner's country or region as soon as possible

If the Company or owner's country or region is not set after March 24, 2022, "Unspecified" will be displayed on the channel consent screen. This content will be displayed when the user is asked to confirm whether or not they agree to the authorization. Therefore, configure the Company or owner's country or region as soon as possible.

Unidentified display image

For more information about the target channels and how to configure them, see the news from February 10, 2022.

# Changes

The main changes to the channel consent screen are as follows. The changes differ for each version of LINE Login.

Changes LINE Login v2.1 LINE Login v2.0
Added Country or region
Other design changes

The changes to the channel consent screen for LINE Login v2.1 are as follows:

Before changes After changes Main changes
Channel consent screen before changes Channel consent screen after changes
  • Added Country or region
  • Removed LINE logo from screen title
  • Changed size and shape of channel icon
  • Deleted text This service's provider is requesting the following permissions.
  • Moved Add friend button of LINE Official Account to the top (which is displayed by the bot link feature)
  • Changed permission switches to toggle buttons
2022/03/24

LINE Developers Agreement updated

We've updated LINE Developers Agreement (opens new window). In this update we've added 5.7.

Developers should also check the news on March 9, 2022, [Recommended] With the design change of the channel consent screen, configure the company or owner's country or region as soon as possible.

# Update date

March 24, 2022 JST (GMT+9)

# What is LINE Developers Agreement?

LINE Developers Agreement (opens new window) is an agreement regarding the terms of use for SDKs or APIs provided by LINE. Developers must agree to this agreement before using the SDKs or APIs.

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

2022/03/24

[Resolved] Notice of failure in some of the insight's APIs

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

March 23, 2022 around 3:17 - around 18:31 JST (GMT+9)

# Cause of the outage

Server failure

# Impact

# Details

The number of messages sent on March 22, 2022, retrieved by the APIs, was incorrect.

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

2022/03/22

LIFF v2.19.0 released

We've released LIFF v2.19.0.

In LIFF v2.19.0, we've made internal improvements.

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

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

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

2022/03/17

[Maintenance completed] Emergency maintenance notice of LINE notification messages

Added on March 18, 2022

We've completed the emergency maintenance of LINE notification messages. Therefore, we've updated the title and the Date and time of maintenance of this article.

We've been performing emergency maintenance on LINE notification messages of options for corporate customers, and the maintenance has been completed.

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 information, see Overview in the Options for corporate customers documentation.

# Date and time of maintenance

March 17, 2022 18:23 - March 18, 2022 17:47 JST (GMT+9)

# Impact

LINE notification messages

# Impact of maintenance

During the maintenance period, LINE notification messages weren't available.

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

2022/03/15

[Updated] As of March 29, 2022, only users who have agreed to the privacy policy (revised March 2022) will be added to an audience for uploading user IDs

Added on March 24, 2022

The scheduled date of change was announced as March 24, 2022, but has been changed to March 29, 2022.

As announced on "Revisions to the LINE Corporation Privacy Policy (opens new window)," we've made changes to the LINE Privacy Policy.

With the changes to the LINE Privacy Policy, we plan to change specifications to add only users who have agreed to the revised privacy policy when you add the user IDs to an audience for uploading user IDs.

# Scheduled date of change

March 29, 2022 JST (GMT+9)

# Impact

As of March 29, 2022, when adding user IDs to an audience, if the user IDs include those of users who haven't agreed to the privacy policy, users who haven't agreed will be ignored and only users who have agreed will be added.

Therefore, the number of valid recipients of the audience may be less than that of user IDs specified.

The affected APIs by this specification changes are as follows:

Users who haven't agreed to the privacy policy at the time of audience creation won't be automatically added to the audience even if they agree to the privacy policy afterwards

To add users who agree to the privacy policy after creating an audience, use the API again.

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

2022/03/11

[Updated] Flex Message Update 3 released

Added on March 15, 2022

Flex Message Simulator now supports Flex Message Update 3.

We've released Flex Message Update 3.

In Flex Message Update 3, the following features have been added:

# A video can now be displayed in the hero block

Video component is now available in Flex Message. Using the video component, you can display a video in the hero block.

Video component example

For more information, see Creating a Flex Message including a video in the Messaging API documentation.

# The max width and height of a box component can now be specified

The maxWidth property and the maxHeight property have been added to the box component. Using these properties, you can specify the max width and height of a box component.

For more information, see Max width of a box and Max height of a box in the Messaging API documentation.

# The line spacing in a text component can now be increased

The lineSpacing property has been added to the text component. Using the lineSpacing property, you can increase the line spacing in a text component.

lineSpacing not specified lineSpacing 20px
Example of not specifying the lineSpacing property Example of specifying 20px as the value of the lineSpacing property

For more information, see Increase the line spacing in a text in the Messaging API documentation.

# Flex Message Simulator now supports Update 3

Flex Message Simulator now supports Flex Message Update 3.

Using Flex Message Simulator, you can easily generate JSON data for flex messages and check the layouts. You can also send a test message and check the actual appearance on your LINE app.

Restrictions

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

2022/03/09

Use the correct endpoint when making requests to LIFF's server API

LINE provides a server API of the LINE Front-end Framework (LIFF) for developers. Using the server API, management such as adding LIFF apps to a channel can be done via the API.

In using this server API, we've seen cases where the string v1 in the endpoint is replaced with another string to make the request. Use the correct endpoint when making requests to the server API.

Item Endpoint(s)
Example of the correct endpoint https://api.line.me/liff/v1/apps
Examples of wrong endpoints
  • https://api.line.me/liff/v2/apps
  • https://api.line.me/liff/example/apps
Version number differs from LIFF SDK

The version number of the server API is different from that of LIFF SDK. The currently released version of LIFF SDK is v2, but the version of the server API is v1.

For more information on the server API, see server API reference.

2022/03/09

[Recommended] With the design change of the channel consent screen, configure the company or owner's country or region as soon as possible

We plan to change the design of the channel consent screen on March 24, 2022.

This design change includes the change to display the Company or owner's country or region for a channel on the channel consent screen, as announced in the news from February 10, 2022.

# Scheduled date of change

March 24, 2022 JST (GMT+9)

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

# Changes

The main changes to the channel consent screen are as follows. The changes differ for each version of LINE Login.

Changes LINE Login v2.1 LINE Login v2.0
Added Country or region
Other design changes

The changes to the channel consent screen for LINE Login v2.1 are as follows:

Before changes After changes Main changes
Channel consent screen before changes Channel consent screen after changes
  • Added Country or region
  • Removed LINE logo from screen title
  • Changed size and shape of channel icon
  • Deleted text This service's provider is requesting the following permissions.
  • Moved Add friend button of LINE Official Account to the top (which is displayed by the bot link feature)
  • Changed permission switches to toggle buttons

# With the design change of the channel consent screen, configure the company or owner's country or region as soon as possible

If the Company or owner's country or region is not set after March 24, 2022, "Unspecified" will be displayed on the channel consent screen. This content will be displayed when the user is asked to confirm whether or not they agree to the authorization. Therefore, configure the Company or owner's country or region as soon as possible.

Unidentified display image

If the terms of use are changed in the future, the setting of Company or owner's country or region may become mandatory. Channel administrators, regardless of whether they are corporations or individuals, are requested to take immediate action.

For more information about the target channels and how to configure them, see the news from February 10, 2022.

2022/03/07

Comprehensive learning platform "LINE Campus" is now available

"LINE Campus (opens new window)", a comprehensive learning platform that enables users to acquire the knowledge and skills of LINE Official Accounts and LINE Ads online, is now available. LINE Campus is currently only available in Japanese.

LINE Campus offers study courses and certification courses, all of which are free of charge. From beginners to experienced users, you can choose from a total of 27 courses and over 90 lessons, subdivided according to your skill level and objectives.

If you're a developer who would like to use the Messaging API but don't know what LINE Official Account is in the first place, or if you'd like to learn the basics of LINE Ads before using the LINE Ads API, try out LINE Campus.

2022/03/07

Webhook redelivery feature will be added to Messaging API in early April 2022

When a user sends a message to the LINE Official Account, a webhook is sent to the bot server according to the event. This webhook is only sent once, but we are planning to add a feature to redeliver it.

The webhook event objects will be changed accordingly, so please be informed in advance.

# Expected date of feature addition

Early April 2022

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

# Overview

This release adds the following two main features. The detailed specifications of each feature will be announced at the time of release.

  1. Add Webhook redelivery feature
  2. Add common properties to Webhook event objects

# 1. Add Webhook redelivery feature

If the bot server does not return a status code in the 2xx for a webhook sent from the LINE Platform, the webhook will be redeliver from the LINE Platform after a period of time.

This feature is disabled by default and can be enabled from the LINE Developers Console. It is available for all Messaging API channels.

# 2. Add common properties to webhook event objects

The following two properties will be added as common properties of the webhook event objects. These properties will be included in the webhook event objects regardless of whether the webhook redelivery feature is enabled or not.

If you are using SDK, need to wait for SDK update

In order to use the common properties added in this release, support on Messaging API SDKs is needed. If you are using the SDK to operate the Messaging API, you will not be able to use these properties until the SDK is supported.

# Common properties to be added

The property names are tentative and may change when the feature is added.

Property name Type Summary
webhookId String An identifier to uniquely define a webhook
deliveryContext Object An object containing information about webhook delivery
deliveryContext.isRedelivery Boolean Whether the webhook event is a redelivered one or not

# Background

The main purpose of this release is to make it possible to receive webhooks again even if there is a temporary problem with the bot server.

When a bot server returns an error in response to a webhook due to temporary over-access or other reasons, there has been no way to reacquire the failed webhook until now. With the addition of this new feature, even if a problem occurs with the bot server, you will be able to receive the redelivered webhook after the bot server is recovered.

Since webhooks that were not processed correctly will not be lost, users will be able to use the Messaging API with more confidence.

# Others

In conjunction with this release, we may stop sending webhooks to bot servers that have been failing to receive webhooks for a long time.

LINE will continue to work on further improving our services to our customers. Thank you for your understanding and cooperation.

2022/03/01

[Resolved] Notice about service outage for the Messaging API

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

February 28, 2022 around 14:24 - around 14:27 JST (GMT+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.

In addition, due to this outage, the number of deliverable messages in February was temporarily consumed more. As a result, the following API requests would fail when the maximum number of deliverable messages was reached:

There will be no impact on usage fees due to this outage.

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

2022/02/28

Reminder: "LINE original unicode emojis" of the Messaging API will be discontinued on March 31, 2022

As announced on November 30, 2021, "LINE original unicode emojis" will be end-of-life on March 31, 2022.

# Scheduled date of discontinuation

2022/3/31 JST (GMT+9)

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

2022/02/24

Users can no longer set "Other" as the Company or owner's country or region for the channel

As announced in the news on February 10, 2022, regarding the Company or owner's country or region, "Other" has been removed from the selectable items. The changes and impact are as follows.

# Changes and impact

We've removed "Other" from the list of Company or owner's country or region for the following channel types. Also, if you've already selected "Other," the selected value has been invalidated and changed to not set.

If your country or region isn't on the list of Company or owner's country or region, let us know the details via our inquiry form (opens new window).

We strongly recommend configuring Company or owner's country or region

These settings are related to the laws that will be enforced in Japan. Therefore, we strongly recommend that you configure these settings if you are providing the LINE Official Account or authorized apps. In addition, Company or owner's country or region is an optional field in an existing channel, but there may be mandatory after April 1, 2022.

# Specification change date

February 24, 2022 JST (GMT+9)

# Background of the specification change

The specification change was made in order to better manage the registration status of the country or region which customers configured for the channel. We sincerely apologize for any inconvenience this may cause to customers who have already selected "Other".

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

2022/02/16

Source code for LIFF Playground, a web application for trying LIFF features, is now available

LINE provides a web application (LIFF app) for developers called LIFF Playground (opens new window). LIFF Playground allows you to try out basic LIFF features on the web. The source code for LIFF Playground (opens new window) is now available on GitHub.

With the publication of the source code, developers will be able to set their LIFF ID and run their own LIFF Playground. For example, each client API such as liff.login() or liff.getProfile() can be run on the web based on the developer's LIFF ID.

LIFF Playground

For more information on how to get started with the LIFF Playground, see the README in the GitHub repository (opens new window).

Differences from the LIFF starter app

LINE has been publishing the LIFF starter app source code (opens new window) on GitHub for some time now. The LIFF starter app is a template with the minimum features required for LIFF app development.

For more information about the LIFF starter app, see Trying the LIFF starter app in the LIFF documentation.

2022/02/14

LIFF v2.18.2 released

We've released LIFF v2.18.2.

In LIFF v2.18.2, the following improvements have been made:

# An alert to encourage users to update LINE will be displayed on LINE for iOS or iPadOS version 12.0.0

As announced on January 14, 2022, there was a bug where the liff.sendMessages() didn't work properly and returned an error with status code 403 under certain conditions. Updating the user's LINE version to 12.0.1 or later will resolve the bug.

In order to encourage users to update to the fixed version of LINE, an alert will be displayed if an error with status code 403 occurs when executing the liff.sendMessages() method on LINE for iOS or iPadOS version 12.0.0.

The alerts that will be displayed is as follows:

LINEアプリをLINE 12.0.1以降にアップデートしてください。Please update your LINE app to LINE 12.0.1 or later.

# We've fixed a bug where scanning a 2D code encoded in UTF-8 with the liff.scanCodeV2() method would cause character corruption

We've fixed a bug where scanning a 2D code encoded in UTF-8 with the liff.scanCodeV2() method would cause character corruption.

This bug fix is automatically applied to all LIFF apps, so there is no need to update the LIFF SDK or modify the code in your LIFF apps.

We've fixed a bug where passing a URL containing a percent-encoded (opens new window) path to the liff.permanentLink.createUrlBy() method would return an incorrect permanent link or cause an error with status code 500.

This bug fix is automatically applied to all LIFF apps, so there is no need to update the LIFF SDK or modify the code in your LIFF apps.

# How to update to LIFF v2.18.2

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

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

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

2022/02/10

[Updated] With the enforcement of the Amended Act on the Protection of Personal Information, companies or owners that manage the LINE Official Account or the authorized apps should configure the country or region in which they are located

Added on February 17, 2022

Configuration function to set the country or region for existing channels is now available to the following channel types:

In addition, we've added the following information of the country or region settings for the LINE MINI App:

Japanese "Amended Act on the Protection of Personal Information (opens new window)" will be enforced on April 1, 2022. Accordingly, the country or region the of company or owner that manage the LINE Official Account or the authorized apps are located is required to be published to end users within LINE app.

Therefore, the LINE Developers Console has added a Company or owner's country or region field to the following channel types. Channel administrators, regardless of whether they are corporations or individuals, can configure the Company or owner's country or region for the corresponding channel.

Channel type Configuring for new channels Configuring for existing channels
LINE Login Configure in the screen to create a channel. Configure in the Basic settings tab.
Messaging API Configure in the screen to create a channel.
The same settings will be applied to the LINE Official Account corresponding to the Messaging API channel. (*)
Configure only for Messaging API channels on which LIFF apps were added before February 5, 2020 in the Basic Settings tab.
Blockchain Service (opens new window) Configure in the screen to create a channel. Configure in the Basic settings tab.
LINE MINI App LINE will configure the country or region based on the information that registered for enrollment in the LINE MINI App development program. Configure in the Basic settings tab.

* The Company or owner's country or region settings configured when creating a Messaging API channel can't be checked or changed from the LINE Developers Console.

# Display to end users of the country or region

The country or region of the company or owner that manages the channel will be displayed to end users in late March 2022. The screens where the country or region will be displayed are as follows:

  • The permission consent screen of the channel
  • The profile screen of the LINE Official Account

If country or region is not set, the message such as "Unknown" or "Unconfirmed" will be displayed.

# How to configure the country or region for LINE Login, Messaging API, and Blockchain Service

Set the appropriate country/region from the list of Company or owner's country or region. When setting the country or region, select the location where the company/individual providing the LINE Official Account or the authorized app is located.

We strongly recommend configuring Company or owner's country or region

These settings are related to the laws that will be enforced in Japan. Therefore, we strongly recommend that you configure these settings if you are providing the LINE Official Account or authorized apps. In addition, Company or owner's country or region is an optional field in an existing channel, but there may be mandatory after April 1, 2022.

# If the country or region to be selected does not exist in the list

If your country or region isn't on the list of Company or owner's country or region, let us know the details via our inquiry form (opens new window) by entering the following:

Item Description
Select your Country Select the major country or region that provide the LINE Official Account or the authorized apps.
Reply Email We'll send our response to this email address.
Please check your email settings beforehand and make sure you can receive messages from do_not_reply@linecorp.com.
Phone Number Enter the phone number registered with your LINE account or any phone number.
Your Registered Email Enter the email address registered with your LINE account or any email address.
1)What is the name of the app? Enter the exact name of your channel. If you have not yet created a channel, there is no need to enter.
2)What is the Channel ID? Enter the exact Channel ID of your channel. If you have not yet created a channel, there is no need to enter.
3)What is your login email address? Enter the email address of your developer account. If you are unsure, log in to the LINE Developers Console, click Accounts in the top-right corner of the screen, and enter the email address displayed.
4)When did the issue occur? Please give the date and time. There is no need to enter.
5)What are the details of the issue? Enter the following details:
  • That there were no items to select from the list of Company or owner's country or region.
  • The country/region where you want to set.

For items not listed in the table above, submit the form with the default values.

# How to configure the country or region for LINE MINI App

# Configuring for new LINE MINI App channels

The same value as Region set at the time of review request will be reflected. At the time of review request, you must agree to the following checkbox:

I represent and warrant that the region to provide the LINE MINI App and service company's country or region are the same.

# Configuring for existing LINE MINI App channels

You can configure the Company or owner's country or region to your existing LINE MINI App channels in the Basic settings tab. The value that can be configured is either the same value as Region or "Other".

The period during which the Company or owner's country or region can be set for the existing LINE MINI App channels

After March 9, 2022, you won't be able to edit the Company or owner's country or region.

Set the Company or owner's country or region for the existing LINE MINI App channels by March 8, 2022.

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

2022/02/09

Some of the channel status notations have been changed

We've changed some notations of the channel status that can be viewed when logging in to the LINE Developers Console. These changes only applied to the status notations in Japanese. There are no changes to the English notation or the functionality of the statuses.

# Channel status notations

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

Channel Before change (English/Japanese) After change (English/Japanese)
LINE Login channel Developing/非公開 Developing/開発中
Blockchain Service channel Developing/非公開 Developing/開発中
LINE MINI App channel Developing/開発中 no change

For more information about developing status, see Channel roles in the LINE Developers Console documentation.

2022/02/04

[Resolved] Notice about service outage for the Messaging API

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

February 3, 2022 around 9:24 - around 13:30 JST (GMT+9)

# Cause of the outage

Server failure

# Impact

# Details

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

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

2022/02/02

Rich Menu Playground is now available

Rich Menu Playground is now available. Rich Menu Playground is a LINE Official Account where you can try out rich menu features. It is only available in Japanese.

You can try out various rich menu features, such as letting the user select a date and time using the datetime picker action, or switching between multiple rich menus using rich menu aliases.

Rich Menu Playground main screen

For more information, see Try out rich menus on Rich Menu Playground in the Messaging API documentation.

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.

2022/01/27

LINE Ads Reporting API documentation site is now available

The LINE Ads API documentation (opens new window) is now available, showing you how to use the LINE Ads Reporting API.

All the contents of LINE Ads Reporting API published on the LINE Developers site have been transferred. From now on you can find the LINE Ads Reporting API reference on the LINE Ads API documentation website.

Use of LINE Ads Reporting API requires an application

The LINE Ads Reporting API can only be used by corporate users who have submitted the required applications. To use it with your LINE Ads Account, submit your application via LINE Ads Reporting API application form (opens new window)(Japanese).

2022/01/25

Some reserved words will no longer be allowed in LIFF app name as of January 25, 2022

We'd like to inform you that as of January 25, 2022, some reserved words will no longer be allowed in LIFF app name.

LINE Platform provides features to create and update LIFF apps on the LINE Developers Console and the LIFF server API. When creating or updating a LIFF app, there have been no restrictions on the LIFF app name. From now on, it will no longer be allowed to set "LINE" or similar strings, or inappropriate strings as the LIFF app name.

For more information about creating and updating LIFF app, see Adding the LIFF app to your channel.

# Date of change

January 25, 2022 JST (GMT+9)

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

2022/01/18

Development of the LINE Bot Designer has been terminated

We have terminated the development of the LINE Bot Designer, which has been used for creating LINE Bot prototypes. As a result, new features added to the Messaging API in the future won't be available on the LINE Bot Designer.

Creating a Flex Message prototype

We recommend using the Flex Message Simulator to create a Flex Message prototype. The Flex Message Simulator will support new features added to the Flex Message in the future.

Although the LINE Bot Designer is likely to be deprecated in the future, you can still download it from Download the LINE Bot Designer.

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

2022/01/14

[Resolved] Notice about service outage for the LIFF/LINE MINI App

Updated on January 17, 2022

We've updated the Date and time of outage and Impact.

We'd like to inform you about a service outage regarding the LIFF/LINE MINI App. We've released the fix version of LINE.

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

# Date and time of outage

January 12, 2022 - January 16, 2022 JST (GMT+9)

# Cause of the outage

Issue with LINE version 12.0.0 for iOS and iPadOS.

# Details

These issue were observed when opening the LIFF app or LINE MINI App under certain conditions:

  • liff.sendMessages() didn't work properly and returned an error message user doesn't grant required permissions yet with status code 403.
  • When executing liff.getContext(), none was returned as the type of the return value, regardless of the screen type on which the LIFF app launched.

# Impact

If all of these conditions are met, there was a problem with liff.sendMessages() and liff.getContext().

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

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