We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.
Date: December 19, 2019 Time: 19:10 - 19:32 (UTC+9)
Issue with our servers.
LINE Login and LIFF operations were unstable and did not work properly.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We've added the mode property to all Messaging API webhook events.
The mode property is necessary for the channel multiplexing feature (under development). Now, all existing webhook events contain "mode": "active".
The mode property's value can change to standby if the channel administrator starts using channel multiplexing. The value of mode never automatically changes to standby.
Learn more about the mode property by reading about the Common properties of webhook events in the Messaging API reference.
As announced on September 13, 2019, we've removed all content related to LINE SDK v4.x from this site. We've also redirected any paths still pointing to the removed content to these pages:
There was an issue with the Statistics tab for Messaging API channels on the LINE Developers Console. Due to an inconsistency in how the system handled timezones, the tab appeared to show different data for certain days than the TSV file that you can generate by clicking Download as TSV.
This problem only affected users outside the JST timezone, and only affected the presentation of the data. No data was deleted or damaged. you'll be able to retrieve and display all data as normal.
Issue inception: November 26, 2019
Issue solved: December 18, 2019
The issue has now been resolved, so you may retrieve and display all data as normal. We apologize for any inconvenience this may have caused.
When a user logs in to a site that uses LINE Login v2.1, the content of the notification from the Official LINE account will be different.
Before, the notification differed depending on the login method that was used. Starting December 9th, 2019, the notification content will be consistent regardless of how the user logs in.
| dummy | dummy |
|---|---|
| Successful login | We've detected a login to X on Y (Z). IP address: {ip_address} Location: {Location} If this wasn't you, you can log out here: {device_link} We also recommend changing your password via the following link: {help_link} |
| Failed login | We've detected an unsuccessful login attempt to X on Y (Z). IP address: {ip_address} Location: {Location} If this wasn't you, you can check which devices are logged into your account here: {device_link} We also recommend changing your password via the following link: {help_link} |
Note that (Z) represents a URL and may sometimes be omitted.
For all LINE users that log in to a site using LINE Login v2.1.
In the Messaging API beacon event, a stay event has been added to indicate that the user is staying in the covered area of the beacon.
If you wish to use the stay event, please contact us at LINE for Business.
As of January 2021, we are no longer accepting new applications for stay events.
We added a new stickerResourceType property to the webhook event that notifies you when a sticker message is sent.
Use this property to see what type of sticker was sent (still image, animated sticker, sticker with sound, etc.).
Learn more from the Sticker section of the Messaging API reference.
LINE TV is a video streaming service available in Thailand. Today, we released the English version of the LINE TV documentation. We are currently not planning to translate it to other languages.
While LINE TV is only available in Thailand, you can call the APIs from anywhere in the world.
Due to a technical issue, we've temporarily suspended the following LIFF functions. We'll let you know as soon as this situation changes.
liff.scanCode()liff.bluetooth.*| Environment | Version |
|---|---|
| LINE for iOS | On version 9.19.0 and later, the functions listed above are temporarily unavailable. |
| LINE for Android | Not affected for now, but more news will follow soon. |
We apologize for the inconvenience and are working hard to solve the problem.
As previously announced, today we released a new version of the LINE Developers Console.
This version of the LINE Developers Console fixes several reported problems and adds various improvements to create a smoother, more reliable experience. Here are some highlights of the new release:
Each channel's first tab is now called Basic settings and contains the essentials. The second tab is named after the channel type (LINE Login, Messaging API, or CLOVA skill), and contains settings relevant to that type.
Use the search field at the top of the provider list to filter by name and easily find the provider you're looking for.
In the previous version you had to manage Admin, Member, and Tester users on two different pages. Now, you can find and add users of any type on the Roles tab.
We hope the new LINE Developers Console makes it easier for you to create and manage channels. We'll continue working to improve your experience with future releases.
We will perform maintenance on the LINE Developers Console at the below time. We apologize for any inconvenience this may cause.
November 26, 2019 12:00 - 13:00 (UTC+9)
The LINE Developers site will be unavailable during the maintenance period.
This maintenance will not affect LINE Platform products such as LINE Login and the Messaging API.
This maintenance brings a new design to the LINE Developers Console. With the updated design, you will be able to use LINE Platform products more comfortably and efficiently.
The main changes are as follows.
We also plan to improve usability by changing certain specifications.
LINE will continue to improve the quality of its services.
LIFF v2 is scheduled to be updated with LINE Login as the core channel. Additionally, an upcoming change will prevent users from adding LIFF apps to Messaging API channels entirely. We strongly recommend users to add LIFF apps to the LINE Login channel.
Early February 2020
| Channel type | Impact |
|---|---|
| LINE Login channel | Not affected. |
| Messaging API channel | After the specification change, LIFF apps cannot be added to the Messaging API channel. LIFF apps added to Messaging API channels at the time of specification change are still usable. |
At this time, users can add LIFF apps to the Messaging API channel. However, we strongly advise against it due to the following restrictions:
LIFF apps added to the LINE Login channel have no restrictions and can use all LIFF v2 functions.
To continue using the LIFF app added to the Messaging API channel, re-add the LIFF app to the LINE Login channel. Once re-added, LINE Developers Console will issue a new LIFF app ID. As a result, please take note of the following:
liff.init().To avoid confusion, delete the LIFF app added to the Messaging API channel after adding to the LINE Login channel.
The domain name of certain Messaging API endpoints has been changed from api.line.me to api-data.line.me. There is no maintenance associated with this.
If you are using the above endpoints, please change your domain during the transition period. We apologize for any inconvenience this may case. Thank you for your understanding.
Once the transition period ends, accessing an endpoint of the old domain will return a 404 status code.
Today - April 30, 2020
Previously, the following Messaging API endpoint didn't allow LINE Official Accounts created in Thailand (TH) to get user activity statistics. Today, we've made it available.
This endpoint returns the same data as on the Insight tab in the LINE Official Account manager.
When your back-end server receives an ID token originating from LINE Login v2.1 or the LINE SDK, you should verify that the ID token is authentic.
Previously, you had to use a JWT library or write your own decoding and verification code.
After this release, you merely have to send an HTTP request to the verification endpoint to determine if an ID token is authentic.
For instructions on verifying ID tokens, read Transfer ID token to back-end server.
LINE Front-end Framework (LIFF) v2 is a platform for web apps provided by LINE.
LIFF v1 will be deprecated.
With LIFF v1, LIFF apps ran only in a LIFF browser. With LIFF v2, LIFF apps can also run in external browsers. This means you can develop LIFF apps using the same development environment as general web applications.
Because compatibility with LINE Login v2.1 has improved, you can retrieve a user's ID and email address from the LINE Platform. Your LIFF app can use this data to provide features related to user information and sending emails.
Furthermore, you can use LINE Login (web login flow) even when your LIFF app is running in an external browser. This means you can use the same information even when the LIFF app is running in an external browser.
You can start LINE's QR code reader and get the strings read by the user.
You can get the following details about the environment in which your LIFF app is running:
For more information, see LINE Front-end Framework.
We added a new Messaging API endpoint that returns information about how users interact with broadcast messages sent from your LINE Official Account.
This endpoint returns the same data as on the Insight tab in the LINE Official Account manager.
We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.
Date: October 4, 2019
Time:
9:00 - 9:02 (UTC+9)
10:04 (UTC+9)
11:00 - 11:08 (UTC+9)
12:02 - 12:08 (UTC+9)
Issue with our servers.
All Messaging API endpoints (https://api.line.me/v2/bot/*).
The API returned status code 500 for some requests.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
From now on, LINE Developers News will offer selected articles in Chinese (in addition to English and Japanese), making it easier for Chinese-speaking developers to stay up-to-date on LINE development.
To change your language setting to Chinese, scroll to the bottom of the page and select "繁體中文" (Traditional Chinese) from the language menu in the page footer:
We're performing system maintenance at the below time. We apologize for any inconvenience.
September 26, 2019 16:20 - 16:50 (UTC+9)
The maintenance will only last a few seconds and will take place somewhere in this time window.
Messaging API, LINE Login, and LIFF operations may result in errors. Specifically, the following events can occur:
We've added a Try button to these sections of the Messaging API reference documentation:
Clicking Try reveals a form that enables you to test the API call right then and there. You'll need to enter some required information, such as your channel access token (found in the LINE Developers Console). Depending on the call, there are also other fields to fill in.
For now, this feature is only enabled for a small number of operations. We plan to increase the number in future releases to cover more Messaging API functionality.
December 12th, 2019 marks the end-of-life date for LINE SDK v4.0 for Android and LINE SDK v4.1 for iOS (from hereon collectively called LINE SDK v4.x). On that date, we'll remove from this site the following things:
To ensure a consistent, secure, up-to-date experience for LINE users, our partners' apps and services should use the latest version of our technology. We already marked LINE SDK v4.x as deprecated some time ago, but continued to offer documentation and download links as a courtesy to partners who couldn't upgrade on short notice. Now we're taking the next logical step: declaring LINE SDK v4.x end-of-life and removing all references from our site.
What you need to do to upgrade depends on what version you're currently using.
| From | To | Notes |
|---|---|---|
| LINE SDK v4.x for iOS Objective-C | LINE SDK v5.2 for iOS Swift | The old and new versions use different programming languages, which makes migrating a big task. We hope the migration instructions in Upgrading the SDK will make it easier. |
| LINE SDK v4.x for Android | LINE SDK v5.1 for Android | There are minor differences between the old and new version, particularly with relation to how login works. The page Integrating LINE Login with your Android app explains how to integrate the latest version. |
| LINE SDK v3.x for iOS Objective-C | LINE SDK v5.2 for iOS Swift | There are major differences between the old and new version, meaning you'll have to redo your integration from scratch. See Integrating LINE Login with your iOS app for instructions. |
| LINE SDK v3.x for Android | LINE SDK v5.1 for Android | There are major differences between the old and new version, meaning you'll have to redo your integration from scratch. See Integrating LINE Login with your Android app for instructions. |
We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.
Date: September 11, 2019 Time: 17:00 - 18:30 (UTC+9)
Date: September 12, 2019 Time: 13:00 - 13:30 (UTC+9)
Server outage due to heavy load.
All Messaging API endpoints (https://api.line.me/v2/bot/*).
The API returned status code 500 for some requests. Also, the "Send reply message" endpoint (https://api.line.me/v2/bot/message/reply) returned error codes in the 400 range, even for correct requests.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Date: September 11th, 2019 Time: 13:46 - 15:58 (UTC+9)
Issue with our servers.
During the specified time, the Statistics tab for Messaging API channels in the LINE Developers Console was not working as intended.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We released Flex Message Simulator Update 1 (β). This version contains sample Flex Messages with more sophisticated layouts based on the new features of Flex Message Update 1.
We can't guarantee that the appearance of a Flex Message in Flex Message Simulator Update 1 (β) exactly matches the rendering on a target device. A single Flex Message may be rendered differently from device to device. Factors that affect rendering include OS, LINE version, screen resolution, language setting, and fonts.
We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Date: August 28, 2019 Time: 18:15 - 18:40 (UTC+9)
Issue with our servers.
During the date and time stated above, some users could not access the LINE Developers site and the LINE Developers Console.
We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.
We've added new Flex Message properties. As a result, you can use the rich expressive power of HTML and CSS in Flex Messages. For details, see Sending Flex Messages.
We discovered and fixed a bug in the LINE Developers Console that allowed Member users to obtain a channel secret. We sincerely apologize for any inconvenience caused.
On July 24, 2019, we emailed this information to all administrators of channels with Member users.
Issue inception: September 21, 2017
Issue solved: July 17, 2019
There was a bug that allowed Member users to obtain the channel secret, which should have appeared only to Admin users.
The Channel settings tab did not display the channel secret when a Member user viewed the page. However, the API that the LINE Developers Console called in the background did return the channel secret. Therefore, a malicious Member user could have obtained and abused the channel secret.
The channel secret is a secret key provided by LINE to call our APIs and validate identities. It should be kept secret from unauthorized parties.
Originally, Member users can only view basic information and statistics for a channel. They don't have access to the channel secret.
If you're concerned that unauthorized Member users have obtained your channel secret, you should issue a new one. Doing so will invalidate the previous channel secret.
After you issue a new channel secret, you'll have to update it in the app which uses the channel secret. Carefully consider the impact of issuing a new channel secret on your app.
You can issue a new channel secret on the Channel settings tab in the LINE Developers Console.
LINE will not forcibly reissue new channel secrets. The Admin user for each channel should decide whether it's necessary to reissue a new channel secret.
This bug was reported through the LINE Security Bug Bounty Program.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We want to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience this may have caused.
Date: July 18, 2019 Time: 9:38–10:40 (UTC+9)
Issue with our servers.
LINE Login returned http error codes with the pattern 5xx (500, 501, etc.) for some requests. As a result, LINE Login was unavailable in the following applications:
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We're happy to announce that we've added 3 new Messaging API endpoints that enable you to get detailed information about the friends of your LINE Official Account:
The data returned by these endpoints is the same data displayed on the Insight tab in the LINE Official Account Manager.
We've released a new LINE SDK for Flutter. This SDK is a Flutter plugin that lets you access the functions of LINE SDK for iOS and LINE SDK for Android in your Flutter app with Dart. For details, see these pages:
The LINE SDK for Flutter documentation is only available in English, for now.
We've added new parameters and properties to LINE Login v2.1:
ui_locales lets you specify the display language and script for LINE Login.amr specifies the authentication methods used in authentication. This corresponds to the OpenID Connect 1.0 amr Claim.amr property is automatically added to all LINE login v2.1 enabled channels, so no additional development work is required.See also Integrating LINE login with your web app. If you haven't integrated LINE Login yet, we hope you'll consider doing so now.
New or changed LINE Login functions may cause changes in the structure of the payload JSON object. These changes may include added properties, variations in property order, and added/removed white space and line breaks. Make sure your implementation can handle both current and future payload data objects.
Any functionality we offer may be changed without notice. However, we'll try notify you in advance if we believe that the change will significantly affect developers.
We encountered problems during the planned migration of accounts from the deprecated Developer Trial plan to the new free plan, which started on June 11, 2019. The problems have now been resolved. We sincerely apologize for the inconvenience this caused.
From: June 11, 2019 Until: June 18, 2019 14:33 (UTC+9)
In Japan and Thailand, accounts that were migrated from the old Developer Trial plan to the new free plan incorrectly retained their old limit on number of friends (50).
When a user tried to befriend an account that had reached the limit of 50 friends, this error was displayed:
Sorry, the account you are trying to add cannot accept any more friends.
We have now removed the limit on the number of friends.
LINE will continue improve the quality of its services to prevent future outages. Thank you for your understanding.
We'd like to inform you about a service outage regarding LINE Login. The issue has now been resolved. We apologize for any inconvenience that this may have caused.
Date: June 17, 2019 Time: 11:41 - 13:01 (UTC+9)
Issue with our servers.
LINE Login returned error code "400 Bad Request" when some users attempted to log in.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved. We apologize for any inconvenience that this may have caused.
Date: June 14, 2019 Time: 10:35 - 12:19 (UTC+9)
Issue with our servers.
All Messaging API endpoints (https://api.line.me/v2/bot/*).
The API returned status code 500 for some requests.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved. We apologize for any inconvenience that this may have caused.
Date: June 5, 2019 Time: 14:41 - 15:05 (UTC+9)
(Most errors were solved by 14:55.)
Issue with our servers.
All Messaging API endpoints (https://api.line.me/v2/bot/*) and webhook.
The API returned status code 403 or 500 error for some requests. Also, webhook events were not successfully sent.
We will continue to improve the quality of our services. Thank you for your understanding.
We added the "automatic communication" feature to the LINE Things Developers Trial. Learn more from these pages:
These pages will be translated into English soon.
We have improved the consent screen bundled with the LINE Front-end Framework (LIFF). The improvement is automatically applied to all LIFF apps. There's no need for additional development work.
As before this update, the user can choose to not allow the LIFF app to send messages to chats. But if they do so, unlike before, the consent screen will reappear the next time the user launches the LIFF app.
With the consolidation of LINE@ account plans into LINE official plans, we changed the functionality of the LINE Developers Console and the Messaging API as follows:
When you create a Messaging API channel in the LINE Developers Console, a LINE Official Account is created instead of a LINE@ account.
For more information, see Migration of LINE@ accounts. Existing LINE@ accounts will be migrated to LINE Official Accounts sequentially.
Now you can set your own privacy policy and terms of use for your app in your LINE Login and Messaging API channels.
In the future, we will add links to your privacy policy and terms of use for your app in the user consent screen of LINE Login or your LINE Official Account.
Bots associated with new or migrated LINE Official Accounts can use the following features regardless of applied plans:
Bots associated with LINE@ accounts cannot use these features depending on applied plans.
For more information, see the Messaging API reference.
We will consolidate the LINE@ account plans into the new LINE Official Account plans.
From April 18, 2019, when you create a Messaging API channel in the LINE Developers Console, a LINE Official Account will be created instead of a LINE@ account.
After mid-June, 2019, we will migrate the existing LINE@ accounts under the Developer Trial plan to LINE Official Accounts. The free plan will be applied to the migrated LINE Official Accounts.
Learn more from Migration of LINE Developer Trial plan on the LINE Engineering Blog.
We'd like to inform you about a service outage regarding the LINE Developers site. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Date: April 4, 2019 Time: 14:00 - 15:00 (UTC+9)
Issue with our servers.
During the date and time stated above, users could not access the LINE Developers site and the LINE Developers Console.
We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.
We added endpoints for the following rich menu operations:
For more information on how to use the rich menu features, see the following pages.
We released the LINE SDK 5.1.0 for iOS Swift. Get the SDK from our GitHub repository.
Changes:
Encodable protocol for easier serialization.We won't stop looking for ways to make your coding life easier. Expect more improvements in future versions!
We will perform maintenance for LINE Login and the Social API. We apologize for any inconvenience caused by this.
March 05, 2019 05:30 - 06:30 (UTC+9)
API operations using the access token for LINE Login v2.0 and the Social API v2.0 can be interrupted for 30 seconds to 1 minute.
This maintenance will not affect API operations using the access token for LINE Login v2.1 and the Social API v2.1.
We'd like to inform you about a service outage regarding LINE Login and the Social API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Date: February 26, 2019
Time: 6:46 - 7:16 (UTC+9)
Issue with our servers.
HTTP status code 500 was sometimes returned when requests were sent to the LINE Login and Social APIs.
We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.
In order to improve the quality of our documentation and products, we added the feedback form again at the right bottom of our documentation pages.
If you would like to report any bugs in our documentation or would like to leave any suggestions, scroll down the page and complete the form.
We greatly appreciate your feedback and we are committed to improving your experience using our developer products.
We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Issue with our servers.
HTTP status code 500 was sometimes returned when the following API endpoints were accessed:
We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.
We released the LINE SDK 1.0.0 for Unity.
The LINE SDK for Unity is a wrapper for our existing LINE SDKs for iOS and Android. This means you can now use the functionality offered by those SDKs in your Unity games.
Read our guide to learn more. In addition to the guide, we'll soon release a full reference for the methods available in the SDK.
We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Issue with our servers.
The Messaging API experienced errors with error code 403 or 500 during the outage.
We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.
We moved information related to the number of your bot's friends from the LINE Developers Console to the LINE Official Account Manager. We removed this information from the "Number of friends" tab on the "Statistics" tab of the Messaging API channels.
To view the number of your bot's friends, click the Account Manager Official Site button in the "Number of friends" tab. LINE Official Account Manager or LINE@ Manager will open according to your account plan.
To use the LINE Official Account Manager, you need separate access permission. If you cannot access these tools, please contact the tool administrators of your organization.
We will remove the "Number of friends" tab from the LINE Developers Console on March 26, 2019.
On February 27, 2019, we will perform maintenance for the LINE Developers site. We apologize for any inconvenience caused by this.
February 27, 2019 12:00 - 13:00 (UTC+9)
The LINE Developers site will be unavailable during maintenance.
This maintenance will not affect LINE Platform products such as LINE Login and the Messaging API.
We will archive the LINE Platform feedback repository on GitHub on February 15, 2019.
Please send your questions about the LINE Platform to the Q&A page of the LINE developers community site. Like many technical forums, you can post and answer questions freely, and leverage the development know-how accumulated within the developer community for the LINE Platform.
We added the liff.getAccessToken() method to the LIFF SDK.
Use the access token to interact with the Social API to access user profile data on the LINE Platform.
For more information, see Getting the user's access token.
Web apps that use LINE Login v2.1 now allow users to log in by scanning a QR code on the login screen. They can scan the QR code with LINE on their smartphones. As before, they can also log in with their email address and password.
We have applied this new feature to all channels with LINE Login v2.1 enabled. You don't need any further development.
Don't let your users miss out on this great UX feature — implement LINE Login today!
QR Code is a registered trademark of DENSO WAVE INCORPORATED in Japan and in other countries.
We'd like to inform you about a service outage regarding the Messaging API. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.
Issue with our servers.
The Messaging API experienced errors with status code 5xx for approximately one minute around 17:00 on January 12, 2019. Also, webhook events were not successfully sent until 18:30 on the same day.
We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.
