# Release notes

April 2, 2020

We've revised some of the design and text to make the consent screen of LINE Login easier to see and use.

# Changes

  • To make it easier for users to understand what to do on this screen, we've removed the screen title Grant permission? and changed the screen description statement to This service's provider is requesting the following permissions.
  • You can show or hide the description of each item by clicking on the Arrow icon icon in the Required permissions section.
  • We've enlarged the Allow button to improve visibility.

Improved LINE Login Consent Screen

The changed consent screen appears in the process of requesting the user to grant permissions to the app. For more information, see Authorization process.

October 25, 2019

# New ID token verification endpoint released

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 (opens new window) 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.

June 26, 2019

# New parameters and properties added

We've added new parameters and properties to LINE Login v2.1:

  • The parameter ui_locales lets you specify the display language and script for LINE Login.

  • The property amr specifies the authentication methods used in authentication. This corresponds to the OpenID Connect 1.0 amr Claim.

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


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.

February 5, 2019

# You can log in with a QR Code

Web apps that use LINE Login v2.1 can now let users log in by scanning a QR code on the login screen with the LINE app on their smartphones. As before, they can also log in with their email address and password.

We've applied this new feature to all channels with LINE Login v2.1 enabled. You don't need any further development.

November 22, 2018

The behavior of a consent screen displayed to users at login has been changed when you use LINE Login to request your users to grant your app permission to get their email address.

Previously, when a user attempted to log in, a consent screen was displayed at each login with or without the prompt parameter. Currently, a consent screen is not displayed for a certain period unless the user's email address changes.

For more information, see Authentication process.

February 28, 2018

# New permission to get users' email address released

Now you can request users who log in using LINE Login to grant your app the permission to get their email address. To do so, you first need to apply for the permission in the LINE Developers Console.

For more information, see the sections below in Integrating LINE Login with your web app.

November 21, 2017

We've added an option to display a prompt to let you display an option for users to add your bot as a friend when logging in to your app with the LINE Login. This is called the bot link feature. To do this, first, link a bot to your LINE Login account from the new "Bot linked to this channel" item in the LINE Developers Console, then include the bot_prompt query parameter in the authorization URL for LINE Login.

For more information on this feature, see Add a LINE Official Account as a friend when logged in (bot link).

In addition, we've released a new resource for the Social API which lets you get the friendship status between your bot and a user. Send a GET request to https://api.line.me/friendship/v1/status to see if the user has added your bot as a friend or not.

To learn more about this resource, see Get friendship status between the user and the LINE Official Account in the API reference.

September 28, 2017

# LINE Login v2.1 released

We've released LINE Login v2.1 which provides new features to make it easier for you to implement a login feature to your app. The new version adds support for the OpenID Connect 1.0 (opens new window) specification which is an identity layer on top of OAuth 2.0.

Here are some of the key changes.

# ID tokens

With LINE Login v2.1, you'll be able to get ID tokens which contain user profile information when you retrieve the access token. This means that you no longer need to send a separate request to retrieve a user's profile information.

For more information, see ID tokens.

# Login sessions

In version 2.1, when users are redirected to the authorization endpoint, we'll be able to check the login session to determine if the user is logged in to LINE or not. If users are logged in to LINE and their browsing session is valid, they will not be required to enter their email and passwords to log in.

For more information, see Authentication process.

# Updated endpoints

We've updated our authorization endpoints where you can use the new version 2.1 features. For more information, see:

Note: You'll still be able to use our LINE Login v2.0 endpoints.