News

  • 2020/01/21

    LIFF v1 Server API end-of-life on March 31, 2020

    March 31, 2020 marks the end-of-life date for LINE Front-end Framework (LIFF) v1 Server API. On that date, these features will be removed:

    note Use the latest version of LIFF

    As announced on October 16, 2019, LIFF v1 will be discontinued.

    Use LIFF v2

    All discontinued Server API functions can be used in LINE Developers Console. For more information on how to add a LIFF app to a channel, read this:

    You can use other features with the same process.

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

  • 2020/01/15

    New Messaging API endpoint for sending narrowcast messages

    An endpoint for sending narrowcast messages has been added to the Messaging API.

    This endpoint lets you send push messages to multiple users at any time.

    You can specify the recipient using certain attributes (gender, age, OS type, region etc) and retargeting (audience).

    For more information, see Send messages to multiple users using attribute information and retargeting.

    Documentation available in Japanese only. English coming soon.

  • 2020/01/14

    Update your code that uses the suspended LIFF SDK API

    As announced on November 29, 2019, these APIs on LINE v9.19.0 and later for iOS were temporarily suspended due to technical issues.

    • liff.scanCode()
    • liff.bluetooth.*

    Starting today, for end users using the LIFF app on LINE v9.19.0 and later for iOS, each API works as follows.

    API Function
    liff.scanCode() API is undefined
    liff.bluetooth.* If the Bluetooth plug-in fails to initialize when calling liff.initPlugins(['bluetooth']), a FORBIDDEN error is returned.

    If you use liff.scanCode(), we recommend that you also consider the above case and verify that the function exists.

    Before modification:

    liff.scanCode().then(result => {
      // result = { value: '' }
    });
    

    Modified:

    if (liff.scanCode) {
        liff.scanCode().then(result => {
          // result = { value: '' }
        });
    }
    

    For more information, see LIFF v2 API reference.

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

  • 2020/01/08

    [Updated] Make sure the provider name is correct

    note Added on January 9, 2020

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

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

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

    Profile

    *The provider name is displayed in the red frame

  • 2019/12/20

    Notice about service outage for LINE Login (resolved)

    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 and time of outage

    Date: 2019/12/19 Time: 19:10-19:32 JST(GMT+9)

    Cause

    Issue with our servers.

    Details

    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.

  • 2019/12/17

    mode property added to Messaging API webhook events

    We've added the mode property to all Messaging API webhook events.

    The mode property is necessary for the channel multiplexing feature (under development). Now, all existing webhook events contain "mode": "active".

    The mode property's value can change to standby if the channel administrator starts using channel multiplexing. The value of mode never automatically changes to standby.

    Learn more about the mode property by reading about the Common properties of webhook events in the Messaging API reference.

  • 2019/12/12

    LINE SDK v4.x content removed

    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:

  • 2019/12/11

    Problem with channel statistics in console (resolved)

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

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

    Issue time

    Issue inception: November 26, 2019

    Issue solved: December 18, 2019

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

  • 2019/12/06

    A stay event was added to beacon event

    In the Messaging API beacon event, a stay event has been added to indicate that the user is staying in the covered area of the beacon.

    If you wish to use the stay event, please contact us at LINE for Business.

  • 2019/12/06

    New LINE Login notification message

    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.

    LINE Login notification message

    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.

    Target users

    For all LINE users that log in to a site using LINE Login v2.1.