You can now create coupons using the Messaging API and send them as messages
2025/08/06

You can now create coupons using the Messaging API and send them to users as messages from your LINE Official Account.

# Added Features

For more information, see Create coupons and send them to users in the Messaging API documentation.

# LINE Messaging API SDK Updates

For more information about the update status of each SDK release in line with the addition of these new features, see the LINE Messaging API SDK release notes.

Messaging API LINE Official Account
On LINE version 15.12.0 or later, users can use multiple LIFF apps at the same time and easily switch between them
2025/08/04

On LINE version 15.12.0 or later, we've made changes to the UI and specifications of the action button in the LIFF browser.

After the specification change, tapping the action button displays the multi-tab view. The multi-tab view displays options for the LIFF app currently in use and recently used services.

LINE version earlier than 15.12.0 LINE version 15.12.0 or later

Users can resume LIFF apps that they left off from the "recently used services" section in the multi-tab view. This allows users to use multiple LIFF apps at the same time and easily switch or move between different LIFF apps.

For more information, see Specifications of recently used services.

# Target version

LINE version 15.12.0 or later

# Specifications of recently used services

The recently used services section includes LIFF apps opened by the user, displayed in order of most recent use, up to a maximum of 50 items. The user can use the usage history to reopen the LIFF apps.

When the LIFF app is opened again from the usage history, the LIFF app is resumed or reloaded. The specifications for resuming and reloading are as follows:

Behavior when reopened Conditions Specifications
LIFF apps will resume

LIFF apps that meet both of the following conditions:

  • LIFF apps used within the last 12 hours
  • LIFF apps included in the 10 most recent usage items
 The LIFF app will resume from the screen where the user left off. The access token, browsing history, and screen scroll position will be retained.
LIFF apps will reload If the conditions for resuming are not met The LIFF app will be initialized at the URL where the user left off. The access token, browsing history, and screen scroll position will be discarded.

For more information, see Recently used services in the LIFF documentation.

# Behavior when closing the LIFF app

On LINE version 15.12.0 or later, the behavior when a LIFF app opened in the LIFF browser is closed by the user or via the liff.closeWindow() method has changed.

If the user closes a LIFF app that meets the conditions for appearing in recently used services, the LIFF app will appear in the "recently used services" section and the user can resume it.

If the user closes a LIFF app that doesn't meet the conditions for appearing in recently used services, the LIFF app will close and exit at the same time.

For more information, see Behavior when closing the LIFF app in the LIFF documentation.

LIFF LINE MINI App
As of the end of November 2025, the feature to check the number of sent messages in the Statistics tab of the LINE Developers Console will be discontinued
2025/07/31

As of the end of November 2025, the feature to check the number of sent messages in the Statistics tab of the Messaging API channel in the LINE Developers Console will be discontinued.

The number of sent messages can still be retrieved via the Get number of message deliveries endpoint in the Messaging API. Additionally, this information is available in the Insight tab of the LINE Official Account Manager (opens new window).

# Scheduled date of change

End of November 2025

The content and date of this specification change are subject to change.

# Details

The following statistics will be deleted from the Statistics tab in the Messaging API channel of the LINE Developers Console:

  • Messages sent
  • Phone number Push
  • Identifier For Advertisers (IFA)
  • Phone

To check the Messages sent or the Phone number Push, use the Get number of message deliveries endpoint in the Messaging API or the LINE Official Account Manager (opens new window) from now on.

Identifier For Advertisers (IFA) and Phone have already been discontinued.

Even if the above statistics are deleted, Errors in the Statistics tab will continue to be available. For more information about errors, see Check webhook error causes and statistics in the Messaging API documentation.

LINE Developers Console End of life Messaging API Options for corporate customers
LIFF v2.27.1 released
2025/07/24

We've released LIFF v2.27.1.

In LIFF v2.27.1, we've made changes to the internal behavior of the LIFF SDK. There is no change in features.

# How to update to LIFF v2.27.1

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

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

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

LIFF LINE MINI App
LINE MINI Apps can now display Yahoo! JAPAN Ads
2025/07/15

You can now display Yahoo! JAPAN Ads (opens new window) (only available in Japanese) in LINE MINI Apps. By displaying ads in LINE MINI Apps, you can monetize your LINE MINI Apps.

For ads that can be placed, we've designated Yahoo! JAPAN Ads as the ad network, which only displays ads that have been reviewed by LY Corporation to ensure that users can use the LINE MINI App safely, and we've enabled the display of those ads.

To place ads in LINE MINI Apps, you must apply to the Yahoo! JAPAN Ads Network Partner (opens new window) (only available in Japanese) and pass the Yahoo! JAPAN Ads site review. Ads can be placed in both verified and unverified MINI Apps, but the service must be provided in Japan.

For more information, see Place ads in LINE MINI Apps in the LINE MINI App documentation.

We plan to revise the LINE MINI App Policy (opens new window) at a later date in conjunction with this update. Once revised, we'll announce the changes on the LINE Developers site news.

LINE MINI App
In LINE MINI App channels, you no longer need to enter Apple Developer Program information
2025/07/09

As of July 9, 2025, it will no longer be necessary to enter Apple Developer Program information in LINE MINI App channels on the LINE Developers Console.

Previously, there was a section for Apple Developer Program information in the Business information tab of the LINE MINI App channel. Entering this information was required when applying for verification to make an unverified MINI App a verified MINI App.

With this change, entering this information is no longer required. As a result, joining the Apple Developer Program is also no longer necessary. The data entered in the Apple Developer Program information section will be deleted after October 2025.

For more information about the settings for LINE MIMI App channels, see LINE Developers Console Guide for LINE MINI App in the LINE MINI App documentation.

LINE Developers Console LINE MINI App
[Updated] Maintenance notice for the LINE Developers Console
2025/07/09
Added on July 10, 2025

The start date and time for Date and time of maintenance have been changed from July 14, 2025 around 15:00 to July 15, 2025 around 0:00.

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

# Date and time of maintenance

July 15, 2025 around 0:00 - around 0:30 (UTC+9)

Note that the date and time of maintenance are subject to change without notice.

# Impact

During the maintenance period, the following operations won't be available for the LINE Developers Console. Operations other than those listed below can be operated even during maintenance.

Also, the Errors in the Statistics tab of the Messaging API channel can be displayed even during maintenance, but the information won't be updated. Information on failures to receive webhook events during maintenance can be confirmed after the maintenance ends.

LINE Developers Console LIFF LINE Login LINE MINI App LINE Platform Maintenance Messaging API Options for corporate customers
[Resolved] Notice about service outage for the Messaging API
2025/06/26

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

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

# Date and time of outage

June 25, 2025 around 17:05 - around 17:44 (UTC+9)

# Cause of the outage

Server failure

# Impact

# Details

During the stated date and time, some requests weren't processed properly, resulting in errors with status code 5xx.

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

Outage Report Messaging API Options for corporate customers
[Resolved] Notice about service outage for the LINE Platform
2025/06/26

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

June 24, 2025 around 16:21 - around 16:24 (UTC+9)

# Cause of the outage

Network failure

# Impact

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

# Details

These are the main impacts per product:

# Messaging API

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

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

# LINE Login

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

# LIFF/LINE MINI App

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

# LINE Developers Console

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


When an outage occurs, we post a preliminary report on the LINE API Status. For more information, see Check the availability of the LINE Platform (LINE API Status) in the LINE Platform basics.

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

Outage Report LINE Platform LINE Login LIFF LINE MINI App Messaging API LINE Developers Console
LIFF v2.27.0 released
2025/06/25

We've released LIFF v2.27.0.

In LIFF v2.27.0, we've added the following feature.

# You can now get a list of scopes for which the user has agreed to grant permission

We've added the liff.permission.getGrantedAll() method to the LIFF SDK. Using the liff.permission.getGrantedAll() method allows you to get all scopes for which the user has agreed to grant permission.

liff.permission.getGrantedAll().then((scopes) => {
  // ["profile", "chat_message.write", "openid", "email"]
  console.log(scopes);
});

The scopes that you can get with this method are as follows:

Difference between liff.getContext() and liff.permission.getGrantedAll()

The liff.getContext() method gets a list of scopes for the LIFF app (*).

On the other hand, the liff.permission.getGrantedAll() method gets a list of scopes for which the user has agreed to grant permission among the scopes for the LIFF app.

* The scopes specified in the "Scope" section under the LIFF tab in a LINE Login channel

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

# How to update to LIFF v2.27.0

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

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

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

LIFF LINE MINI App
Connecting with Business Manager is now required when creating a new LINE Official Account
2025/06/25

As of June 25, 2025, connecting with Business Manager (opens new window) (only available in Japanese) is required when creating a new LINE Official Account as part of platform infrastructure integration. This requirement only applies to LINE Official Accounts in Japan.

Existing LINE Official Accounts aren't currently affected by this change. However, by March 2026, all LINE Official Accounts in Japan will be required to connect with Business Manager. Details will be announced as they are finalized.

For more information, see the PDF document titled Mandatory Connection Between LINE Official Accounts and Business Manager (opens new window) (only available in Japanese).

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

LINE Official Account Messaging API LINE Developers Console
[Resolved] Notice of email transmission outage on the LINE Developers Console
2025/06/19

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

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

# Date and time of failure

June 18, 2025 around 18:23 - around 18:33 (UTC+9)

# Cause of the failure

Server failure

# Impact

Various emails failed to be sent on the LINE Developers Console

# Details

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

Emails that weren't sent properly due to this outage won't be resent, even after the outage has been resolved. We kindly ask that you re-grant provider and channel access yourself. Additionally, you can check the review status of your LINE MINI App and the error information included in error notification emails on the LINE Developers Console.


When an outage occurs, we post a preliminary report on the LINE API Status. For more information, see Check the availability of the LINE Platform (LINE API Status) in the LINE Platform basics.

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

LINE Developers Console LINE MINI App Options for corporate customers Outage Report
The LIFF CLI v0.4 now officially supports ngrok
2025/06/11

In the LIFF CLI v0.4, we've officially supported ngrok (opens new window) as a method for exposing your local development server.

Until now, the LIFF CLI has only supported ngrok v1, but ngrok v1 has already reached the end of its development and maintenance cycle. With this update, we've officially added support for the latest version of ngrok, enabling stable use of ngrok.

This eliminates the need to install ngrok v1 (opens new window) and node-pty (opens new window), which were previously required when using ngrok v1. The LIFF CLI v0.4.0 has an issue where the serve command couldn't be executed properly, so please use the LIFF CLI v0.4.1 or later, which has fixed this issue.

# Usage

The serve command in the LIFF CLI starts a proxy server targeting the local development server. Specifying ngrok as the --proxy-type option of the serve command uses ngrok as the proxy. When using ngrok, set the authtoken of ngrok as the environment variable NGROK_AUTHTOKEN.

$ NGROK_AUTHTOKEN={Authentication token} liff-cli serve \
   --liff-id 1234567890-AbcdEfgh \
   --url http://localhost:3000/ \
   --proxy-type ngrok

Successfully updated endpoint url for LIFF ID: 1234567890-AbcdEfgh.

→  LIFF URL:     https://liff.line.me/1234567890-AbcdEfgh
→  Proxy server: https://1234abcd.ngrok.example.com/

After starting the proxy server, you can access the local development server from an external location by accessing the LIFF URL. Executing the serve command will change the LIFF app's endpoint URL, so don't execute it on a published LIFF app.

For more information about the LIFF CLI serve command, see Launch a local development server with HTTPS in the LIFF documentation.

LIFF LINE MINI App
We've added documentation for webhook signature verification to the Messaging API
2025/06/10

We've added Verify webhook signature to the Messaging API documentation. This document explains how the bot server should verify the signature when receiving a webhook.

We've also updated the Messaging API development guidelines by adding verification of webhook signature when receiving webhooks to the list of recommendations.

# Document Background

When a user adds a LINE Official Account as a friend or sends it a message, the LINE Platform sends a webhook to the bot server specified in the Webhook URL in the LINE Developers Console.

When the bot server receives a webhook, it is recommended that the bot server verify the signature included in the request header before processing the webhook event objects. This verification step is important to confirm that the webhook came from the LINE Platform and wasn’t tampered with during transmission.

The newly added documentation covers Preparations required for signature verification, How signature verification works, and Signature verification procedure.

Also, Common signature verification failures and their solutions explains how to troubleshoot cases in which signature verification fails even though the webhook was sent from the LINE Platform.

We’ll continue improving the LINE Developers site and its documentation to help developers build services using the Messaging API more smoothly.

Docs Messaging API
When identifying LIFF SDK errors, refer to both the error code and the error message
2025/05/30

LIFF SDK errors are returned in LiffError objects. You can identify errors by referencing the values of each property of the LiffError object. We've seen implementations that identify errors based only on an exact match of the error message (the value of the message property in the LiffError object).

Since the error messages are subject to change without notice, identifying LIFF SDK errors based on an exact match of the error message may cause your LIFF app to malfunction. To ensure that your LIFF app continues to work properly even when error messages change, identify LIFF SDK errors by referring to both the error code (the value of the code property in the LiffError object) and the error message (the value of the message property in the LiffError object).

We plan to make improvements so that errors can be uniquely identified by error codes.

LIFF LINE MINI App
LIFF v2.26.1 released
2025/05/26

We've released LIFF v2.26.1.

In LIFF v2.26.1, we've fixed the following bugs.

# We've fixed a bug where accessing a LIFF URL caused the LIFF app to navigate to an unintended secondary redirect URL

In a LIFF app, when accessing the LIFF URL, the LIFF app first navigates to the primary redirect URL and then to the secondary redirect URL. There was a bug in the conditions that append a slash (/) to the end of the path of the secondary redirect URL, which caused the LIFF app to navigate to an unintended secondary redirect URL.

# Conditions that append a slash (/) to the end of the path of the secondary redirect URL

In LIFF v2.26.0 or earlier, a slash (/) is appended to the end of the path of the secondary redirect URL if any of the following conditions are met:

  • The endpoint URL ends with a slash (/)
  • liff.state ends with a slash (/)

For example, if the LIFF app's endpoint URL is https://example.com/?key=value/ and the LIFF URL being accessed is https://liff.line.me/1234567890-AbcdEfgh/foo/bar, the correct secondary redirect URL is https://example.com/foo/bar?key=value/.

However, since the condition "the endpoint URL ends with a slash (/)" is met in this situation, the LIFF app actually navigates to https://example.com/foo/bar/?key=value/ which has a slash (/) added to the end of the path.

Correct secondary redirect URL Actual secondary redirect URL
https://example.com/foo/bar?key=value/ https://example.com/foo/bar/?key=value/

In LIFF v2.26.1, we've applied a fix so that a slash (/) is appended to the end of the secondary redirect URL if any of the following conditions are met. As a result, LIFF apps now navigate to the correct secondary redirect URL.

  • The endpoint URL's path ends with a slash (/)
  • liff.state's path ends with a slash (/)

For more information about the behavior when accessing a LIFF URL, see Behaviors from accessing the LIFF URL to opening the LIFF app in the LIFF documentation.

# We've fixed a bug where the liff.init() method replaced POST requests with GET requests in the browser's session history when excluding credential information

In LIFF apps, when the liff.init() method is resolved, credential information such as access tokens is excluded from URLs. At this time, there was a bug in some environments where POST requests were replaced with GET requests in the browser's session history.

In LIFF v2.26.1, we've fixed the bug so that the correct history is retained.

# Example of a POST request in the browser's session history being replaced by a GET request

For example, suppose you interact with a LIFF app in the following order:

  1. Open a LIFF app
  2. Navigate to /path1 with a POST request
  3. Navigate to /path2 with a GET request
  4. Click the browser's back button

In this situation, the LIFF app is expected to navigate to /path1 with a POST request, but in some environments, the LIFF app navigates to /path1 with a GET request.

# How to update to LIFF v2.26.1

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

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

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

LIFF LINE MINI App
Documentation correction announcement regarding webhooks when sending messages using liff.sendMessages()
2025/05/07

There was an error in Receive messages (webhook) of the Messaging API documentation regarding the behavior of webhooks when messages are sent using liff.sendMessages(). We've already corrected the mistake and apologize for any inconvenience caused by this error.

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

Item Incorrect Correct
Webhook behavior when a template message or a Flex Message is sent by the user using liff.sendMessages() Webhook is sent Webhook is not sent

When a template message or a Flex Message is sent from the user using liff.sendMessages(), the webhook is not sent from the LINE Platform. For all other message types, the webhook is sent.

For more information, see Webhooks when sending a message using liff.sendMessages() in the Messaging API documentation.

Messaging API LIFF LINE MINI App Template message Flex Message
Due to the LINE Pay service termination in Japan, we've discontinued providing LINE Pay documentation and references
2025/04/30

As of April 30, 2025, the LINE Pay service in Japan has been terminated. As a result, we've discontinued providing the following documentation and references on the LINE Developers site:

  • LINE Pay Online documentation
  • LINE Pay Online API reference
  • LINE Pay Offline documentation
  • LINE Pay Offline API reference

For more information about the LINE Pay service termination in Japan, see Notice of the LINE Pay service termination (opens new window) (only available in Japanese).

The LINE Pay services in Taiwan and Thailand will continue to be available. When developing services using LINE Pay in these regions, see the documentation and references on the LINE Pay Developers (opens new window).

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

Docs End of life Life cycle
As of April 23, 2025, in the Messaging API, the rate limit for the "Send multicast message" endpoint changed
2025/04/23

As announced on March 31, 2025, we've changed the rate limit for the Send multicast message endpoint as of April 23, 2025.

The rate limits before and after the change are as follows:

Endpoint Before After (current)
Send multicast message 2,000 requests per second 200 requests per second

There are no changes to the rate limits for endpoints other than those listed above.

# Date of specification change

April 23, 2025

If you're sending to a single user, we recommend using push messages

The "Send multicast message" endpoint is an API that allows you to efficiently send the same message to multiple users. You can also send a message to a single user using the multicast message, but if you're sending it to a single user, we recommend using the push message.

Push messages are suitable for sending messages with low latency, and can still be used at 2,000 requests per second.

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

Messaging API
LIFF v2.26.0 released
2025/04/22

We've released LIFF v2.26.0.

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

# We've fixed a bug where an incorrect error message was returned when a certain method is executed in an external browser while not logged in

There was a bug where an incorrect error message was returned when the following methods are executed in an external browser while the user isn't logged in.

In LIFF v2.26.0, we've fixed the bug so that the correct error message is returned.

Error message before the fix Error message after the fix
LiffId is not found. Need access_token for api call, Please login first

# How to update to LIFF v2.26.0

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

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

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

LIFF LINE MINI App
The MCP server for the Messaging API, "LINE Bot MCP Server" has been published on GitHub
2025/04/14

The LINE Bot MCP Server (opens new window), which is the MCP server for the Messaging API, has been published on GitHub. By using the LINE Bot MCP Server from AI agents such as Claude (opens new window), you can send messages to users from LINE Official Accounts in a dialogue format, and you can also use the information of users who have added LINE Official Accounts as friends.

For more information on how to use the LINE Bot MCP Server, see the README (opens new window) in the GitHub repository.

The LINE Bot MCP Server is currently being published on a trial basis and doesn't fully support the Messaging API features. We plan to add support for unsupported features in due course.

Messaging API
In October 2025, all LINE MINI App users will be able to use the service in a web browser
2025/04/02

In the LINE MINI App, non-LINE users outside of Japan, Thailand and Taiwan can currently use the service in a web browser. We'd like to inform you that we're planning to change the specification of LINE MINI Apps so that all users can use the service with a web browser in October 2025.

# Scheduled date of change

October 2025

The content and date of this specification change are subject to change.

# Changes

The screen that users see when they open the LINE MINI App from their smartphone's web browser will change. The changes are as follows. The changes apply to all LINE MINI Apps, regardless of whether they are verified or not.

  1. Display the LINE MINI App icon and logo at the top of the page
  2. Display a link [Open in web browser] at the bottom of the page to go to the endpoint URL (*)
Before change (current) After change

The images shown here are samples. Therefore, they are subject to change.

Note that there will be no change to behavior when opening the LINE MINI App on a computer.

* The endpoint URL can be set in the Web app settings tab on the LINE Developers Console.

# Important points about specification changes

With this change, users will be able to use the LINE MINI App service via a web browser.

Before the specification change in October 2025, make sure that users can use your service without any problems when opening the endpoint URL in a web browser. We'll announce the date of the specification change when it's determined.

For more information on opening the LINE MINI App in a web browser, see Open a LINE MINI App in an external browser in the LINE MINI App documentation.

# Discontinued features

The redirect non-LINE users to a web browser feature will be discontinued.

After the specification change, users will be able to use the LINE MINI App service via a web browser regardless of whether they are using LINE or not. Therefore, the redirect non-LINE users to a web browser feature, which is a similar feature, will be discontinued on the same day as the specification change.

# Background

LINE MINI Apps provide functionality as web applications that run on the LINE app's LIFF browser. For this reason, there are some LINE MINI Apps that aren't designed to be used with a web browser such as Safari or Chrome.

On the other hand, the LINE MINI App Policy (opens new window) states that "The URL set in the endpoint URL of the LINE MINI App must be accessible from web browsers such as Safari and Chrome".

In order to comply with this web browser usage policy, we've decided to change the specifications of the LINE MINI App so that it can also be used with web browsers.

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

LINE MINI App
LINE Notify service has been terminated as of March 31, 2025
2025/04/01

As announced on October 7, 2024, LINE Notify (opens new window) service has been terminated as of March 31, 2025.

# Date of service termination

March 31, 2025

# Impact

After April 1, 2025, all LINE Notify features, including the following, will no longer be available:

  • All APIs of LINE Notify
    • notify-bot.line.me/*
    • notify-api.line.me/*
  • LINE Notify's My page
    • Add a service
    • Check connected services
    • Generate access tokens

In addition, The LINE Official Account "LINE Notify" (@linenotify) and the following web pages will be deleted after May 12, 2025:

# Alternative method

Please consider using the Messaging API as an alternative method of notifying users from your LINE Official Account. You can send a certain number of messages each month for free. For more information, see Messaging API pricing in the Messaging API documentation.

For more information about features available with the Messaging API, see the Messaging API documentation.

# Contact

Please contact us via the inquiry form (opens new window).

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

End of life
As of April 23, 2025, in the Messaging API, the rate limit for the "Send multicast message" endpoint will change
2025/03/31

In the Messaging API, rate limits are set for each endpoint. We'd like to inform you that we plan to change the rate limit for the Send multicast message endpoint as of April 23, 2025.

The rate limits before and after the change are as follows:

Endpoint Before (current) After
Send multicast message 2,000 requests per second 200 requests per second

There are no changes to the rate limits for endpoints other than those listed above.

# Scheduled date of specification change

April 23, 2025

The content and date of this specification change are subject to change.

If you're sending to a single user, we recommend using push messages

The "Send multicast message" endpoint is an API that allows you to efficiently send the same message to multiple users. You can also send a message to a single user using the multicast message, but if you're sending it to a single user, we recommend using the push message.

Push messages are suitable for sending messages with low latency, and can still be used at 2,000 requests per second.

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

Messaging API
[Updated] We've ended the provision of the feature to change the authority level of the audience
2025/03/26
Added on April 16, 2025

We've added the Activate audience endpoint to the list of endpoints that have been discontinued.

As announced on February 6, 2025, the features to set and check the public/private setting of audiences created with the Messaging API has been discontinued as of March 26, 2025.

# Endpoints that have been discontinued

The following endpoints have been discontinued:

  • Change the authority level of the audience
  • Get the authority level of the audience
  • Activate audience

# Details

In order to use audiences created with the Messaging API in the LINE Official Account Manager (opens new window), it was previously necessary to set the audience's authority level to PUBLIC using the "Change the authority level of the audience" endpoint in the Messaging API.

As of March 26, 2025, this conventional feature for setting the audience authority level to public or private has been discontinued.

The audiences in the Messaging API and the LINE Official Account Manager continue to be mutually usable. In addition, all existing audiences that were set to private (PRIVATE) and couldn't be used with the LINE Official Account Manager are now available.

Tool that creates
audience		 Tool that uses
audience		 Authority level of
audience		 Before
discontinuation		 After
discontinuation (current)
Messaging API LINE Official Account Manager Private ❌ ✅
Messaging API LINE Official Account Manager Public ✅ ✅
LINE Official Account Manager Messaging API Private ❌ ✅
LINE Official Account Manager Messaging API Public ✅ ✅

✅: "Tool that uses audience" can use the audience.
❌: "Tool that uses audience" can't use the audience.

For more information about how to use audiences created with the Messaging API in other tools, see Share audiences in the Messaging API documentation.

Messaging API End of life Life cycle
LIFF CLI v0.3.0 released
2025/03/19

We've released LIFF CLI v0.3.0.

In LIFF CLI v0.3.0, we've added the following features:

# You can now create a LIFF app template

We've added the scaffold command to the LIFF CLI. The scaffold command allows you to create a LIFF app template using Create LIFF App. Passing the project name of the LIFF app to the scaffold command will execute Create LIFF App using that project name.

$ liff-cli scaffold my-app --liff-id 1234567890-AbcdEfgh

For more information, see Create a LIFF app template in the LIFF documentation.

# You can now create a LIFF app development environment

We've added the init command to the LIFF CLI. The init command allows you to create a LIFF app development environment. The init command performs the following three processes in order:

  1. Add a channel
  2. Create a LIFF app
  3. Create a LIFF app template
$ liff-cli init \
   --channel-id 1234567890 \
   --name "Brown Coffee" \
   --view-type full \
   --endpoint-url https://example.com

For example, the command above adds the channel with a channel ID of "1234567890". Next, the command creates a LIFF app with a LIFF app name of "Brown Coffee", an endpoint URL of "https://example.com", and a view size of "Full" for the channel. Finally, create a template with the LIFF ID of the created LIFF app set.

For more information, see Create a LIFF app development environment in the LIFF documentation.

# You can now expose your local development server

This feature is experimental

This feature is experimental. There is a possibility that changes will be made in the future that aren't backward compatible.

We've added the --proxy-type option to the serve command. You can use ngrok v1 (opens new window) instead of a local proxy server by specifying ngrok-v1 for the --proxy-type option. This allows you to expose your local development server.

Don't execute the serve command for a published LIFF app

The serve command rewrites the endpoint URL of the LIFF app with the URL of the local proxy server, so users can't access the LIFF app. Therefore, don't execute the serve command for a published LIFF app.

$ liff-cli serve \
  --liff-id 1234567890-AbcdEfgh \
  --url http://127.0.0.1:3000/ \
  --proxy-type ngrok-v1

ngrok-v1 is experimental feature.
Successfully updated endpoint url for LIFF ID: 1234567890-AbcdEfgh.

→  LIFF URL:     https://liff.line.me/1234567890-AbcdEfgh
→  Proxy server: https://1234abcd.ngrok.example.com/

To use this feature, you need to install ngrok v1 (opens new window) and node-pty (opens new window).

For more information, see Expose your local development server in the LIFF documentation.

LIFF
[Resolved] Notice about service outage for the LINE Platform
2025/03/03

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

February 28, 2025 around 18:20 - around 19:24 (UTC+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

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

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.
  • Some requests weren't processed properly, resulting in errors with status code 5xx.

# LIFF/LINE MINI App

  • There were instances where LIFF/LINE MINI App couldn't be used per usual.
  • Some requests weren't processed properly, resulting in errors with status code 5xx.

# 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 Check the availability of the LINE Platform (LINE API Status) in the LINE Platform basics.

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

Outage Report LINE Platform LINE Login LIFF LINE MINI App Messaging API LINE Developers Console
In the Messaging API, we've started to provide an endpoint and a webhook event related to membership
2025/02/13

We've started to provide an endpoint for obtaining the user IDs of users who have joined the membership of your LINE Official Account, as well as a webhook event that is sent when a user joins, renews, or leaves the membership.

For example, you can use these features to send push messages to users who have joined your membership, or to offer perks when a user renews the membership. For more information, see the sections of the Messaging API reference below:

# LINE Messaging API SDK Updates

For more information about the update status of each SDK release in line with the addition of these new features, see the LINE Messaging API SDK release notes.

Messaging API LINE Official Account
In the Messaging API, you can now use the shared audience in Business Manager to send messages
2025/02/12

In the Messaging API, you can now specify the shared audience in Business Manager as the recipient for narrowcast messages.

Accordingly, we've added the following endpoints:

Previously, shared audiences in Business Manager weren't available in the Messaging API. You can now use these endpoints to integrate between Business Manager and the Messaging API.

About Business Manager

Business Manager allows you to share specific audiences across multiple services. By sharing audiences in Business Manager, you can better communicate with your end users.

For more information, see Business Manager (opens new window) (only available in Japanese) in LINE DATA SOLUTION.

# LINE Messaging API SDK Updates

For more information about the update status of each SDK release related to the above, see the LINE Messaging API SDK release notes.

Messaging API
When you create a new LIFF app, we recommend that you create it as a LINE MINI App
2025/02/12

In the future, the LINE Front-end Framework (LIFF) and the LINE MINI App will be integrated into a single brand. As a result of this integration, LIFF will be integrated into the LINE MINI App. After the integration, as the LINE MINI App, we'll implement the features that can be realized in LIFF apps and add new features. For this reason, we recommend that you create a new LIFF app as a LINE MINI App.

# Scheduled date of brand integration

The date of the brand integration has not yet been determined. We will announce it as soon as it is determined.

# Impact on existing LIFF apps

You can continue to use your existing LIFF apps and your LIFF apps that are created in the future after the brand integration.

# Means of migration from existing LIFF apps to LINE MINI Apps

In late 2025, we'll provide a means of migration from LIFF apps on a LINE Login channel to LINE MINI Apps.

Creation of LINE MINI App channels
  • If your service area is Japan, anyone who is a permitted customer in the LINE MINI App Policy (opens new window) can create a LINE MINI App channel.
  • If your service area is Taiwan, you can only create a LINE MINI App channel if you are approved by our local subsidiary. For more information, see LINE MINI App official site for Taiwan users (opens new window).
  • If your service area is Thailand, you can only create a LINE MINI App channel if you are approved by our local subsidiary. The contact details for receiving approval are currently being prepared.

If the above doesn't apply to you, please continue to use LIFF apps. In the future, you will be able to create LINE MINI App channels without the approval of our local subsidiary, even if your service area is Taiwan or Thailand.

LIFF LINE MINI App
As of March 26, 2025, we will no longer provide the feature to change the authority level of the audience
2025/02/06

As of March 26, 2025, the feature to set and check the public/private setting of audiences created with the Messaging API will be discontinued.

Even after the discontinuation of the public/private setting of audiences, audiences created with the Messaging API and the LINE Official Account Manager will continue to be mutually usable.

# Endpoints to be discontinued

The following endpoints will no longer be provided:

If you send a request to these endpoints after they are discontinued, an HTTP status code 404 Not Found will be returned.

# Details

In order to use audiences created with the Messaging API in the LINE Official Account Manager, it was previously necessary to set the audience's authority level to PUBLIC using the Change the authority level of the audience endpoint in the Messaging API.

As of March 26, 2025, this conventional feature for setting the audience authority level to public or private will be discontinued.

Even after the feature to set the authority level of an audience to public or private is discontinued, the audiences in the Messaging API and the LINE Official Account Manager will continue to be mutually usable. In addition, all existing audiences that couldn't be used with the LINE Official Account Manager because they were set to private (PRIVATE) will be available from March 26, 2025.

Create Use Authority level Before discontinuation (current) After discontinuation
Messaging API LINE Official Account Manager Private ❌ ✅
Messaging API LINE Official Account Manager Public ✅ ✅
LINE Official Account Manager Messaging API Private ❌ ✅
LINE Official Account Manager Messaging API Public ✅ ✅

You can use the audience created by the Messaging API with the tools other than LINE Official Account Manager, such as LINE Ads Manager (opens new window), by using the audience sharing function in Business Manager (opens new window).

In addition, you can share audiences between Messaging API channels under the same provider by using the audience sharing function in the Business Manager. However, only verified accounts and premium accounts can set audience sharing in Business Manager.

For more information, see Notice regarding the discontinuation of the cross targeting feature (audience disclosure and LINE Tag sharing feature) (opens new window) (only available in Japanese) in LINE for Business.

# Schedule

The schedule for the end of feature provision is as follows:

Date Content
February 12, 2025 Start providing an endpoint for retrieving a list of audiences shared in Business Manager via the Messaging API
March 26, 2025 End of provision of conventional feature to set and check the public/private setting of audiences

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

Messaging API End of life Life cycle
LINE MINI App Playground released
2025/02/03

We've released a demo app, LINE MINI App Playground (opens new window), which allows developers to easily try out the features of the LINE MINI App.

By opening the LINE MINI App Playground on a smartphone with the LINE app installed, you can actually try out some of the features of the LINE MINI App. For example, you can try out features that are only available to verified MINI Apps, such as adding a shortcut to your LINE MINI App to the home screen of a device or skipping the channel consent process.

For more information, see LINE MINI App Playground (opens new window).

LIFF LINE MINI App
On February 3, 2025, LINE Developers Agreement will be revised
2025/01/17

We'd like to inform you that the LINE Developers Agreement (opens new window) will be revised on February 3, 2025. This revision is an addition regarding the use of module channels, and won't affect those who don't use module channels.

# Scheduled date of revision

February 3, 2025

The content and date of this revision are subject to change.

# Changes of revision

Article 15 "Special Provisions for the Use of Module Channels" will be added to the LINE Developers Agreement. The content of each agreement before and after this revision is as follows:

Before the revision (current) After the revision
LINE Developers Agreement (opens new window) LINE Developers Agreement (opens new window)

# Background of revision

For the reorganization of our services within LY Corporation Group and the restructuring of our terms and conditions accordingly, we've decided to revise the content that was separately agreed to by users of the module channel in order to add it to the LINE Developers Agreement.

We'll continue to work to further improve its service to our customers. Thank you for your understanding.

LINE Platform LINE Developers Console
LIFF browser can now be minimized on LINE for Android version 15.0.0 or later
2025/01/15

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

LIFF browser minimization is a feature that allows you to suspend viewing a LIFF browser to perform another action. Until now, this feature was only supported by LINE for iOS and not by LINE for Android. With LINE version 15.0.0 or later, it's now possible to minimize a LIFF browser on LINE for Android.

# Conditions of use for LIFF browser minimization

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

  • LINE for iOS version 12.18.0 or later or LINE for Android version 15.0.0 or later
  • Settings > Apps > LINE > Display over other apps is on for the user's device (only required in LINE for Android)
  • 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

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

LIFF LINE MINI App
Some LINE Login screens now support dark mode
2025/01/06

Dark mode is now supported for some of the screens displayed when users authenticate and authorize during LINE Login.

We will continue to add and improve features in LINE Login. For more information, see roadmap.

LINE Login LIFF LINE MINI App

Filter by
news tag

Android Bot Designer Channel access token CLOVA CLOVA Extensions Kit Developers Community LINE Developers Console Deprecated Docs End of life Flex Message Flex Message Simulator Flutter Group Imagemap message iOS Life cycle LIFF LINE Ads LINE API Expert LINE Blockchain Platform LINE Developers site LINE Login LINE MINI App LINE Official Account LINE Platform LINE Login SDK LINE Things LINE TV Maintenance Messaging API Options for corporate customers Outage Report Rich menu Social API LINE Social Plugins SSL/TLS Template message Unity

LINE Developers Official Account

Subscribe for the latest information on the LINE Platform
LINE Developers QR Code