# News

LINE's APIs will support HTTP/2

LINE's APIs will support HTTP/2.

# Domain names subject to the update

  • api.line.me
  • api-data.line.me
  • access.line.me

# Supported HTTP versions

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

HTTP version Before update After update
HTTP/2
HTTP/1.1
HTTP/1.0

# Scheduled date of change

August 4, 2020 12:00 ~ 16:00 JST (GMT+9)

# Impact

If you are using any of the above APIs, please confirm that your app can communicate using the updated supported HTTP versions.

Due to this update, when using the above APIs from clients that support HTTP/2 or TLS 1.3, the handshake overhead is reduced and the connection efficiency is improved.

To use the latest protocols such as HTTP/2 and TLS 1.3, we recommend upgrading your development environment such as JDK and other development languages and LINE SDK to the latest versions.

# Other changes

For access the APIs from outside Japan, these 2 changes are made in addition to the above.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Service message template tab of the LINE MINI App channel updated

The [Service message template] tab of the LINE MINI App channel has been updated.

You can select a template and add it to your LINE MINI App channel while viewing the preview of the service message.

Service message template

You can also enter a JSON object to see the preview or send a test message.

Send Test Message

For more information, see Sending service messages.

Get all valid channel access tokens v2.1 endpoint and content removed

As announced on July 01, 2020, the Get all valid channel access tokens v2.1 API endpoint for Messaging API has been removed. We've also removed all content related to this endpoint from this site.

When Issuing the channel access token v2.1, a unique key ID (key_id) paired with the channel access token is also returned. You can use the newly added Get all valid channel access token key IDs v2.1 endpoint to get an array of key IDs paired with the currently valid channel access tokens. You can verify the validity of channel access tokens by comparing the returned key IDs with pairs of channel access tokens and their IDs stored in a database.

Learn more about Issue channel access token v2.1 in the Messaging API documentation.

Notice of failure of some analytics APIs (Partially resolved)

These problems occurred in the Messaging API, but it has been partially resolved. We apologize for any inconvenience caused to our customers.

# Date and time of outage

Issue 1: July 21, 2020 around 7:00 - 17:00 (GMT+9)

Issue 2: July 16, 2020 onwards (GMT+9)

# Situation

# (Resolved) Issue 1

When premium and verified account users called the Get number of followers API endpoint, the endpoint returned an incorrect number of followers for July 21, 2020.

This issue is now resolved and you can get the correct number for July 21, 2020.

# (Limitation) Issue 2

Some LINE Official Accounts (less than 0.5%) that used the Get number of followers API endpoint from July 16, 2020 to July 20, 2020 may have gotten incorrect numbers returned for followers, targetedReaches, and blocks.

The affected LINE Official Accounts may have had these issues:

  • If you added friends during this period, they aren't added to the total amount of friends.

  • The number of followers during this period is returned with less than the actual value.

For issue 2, the correct value can't be restored.

Note

Neither issue has any effect on the total message delivery count.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LINE API's SSL root certificate authority has been changed

Added July 30, 2020

For access to the APIs from outside of Japan, the root certification authority will be changed after August 4, 2020. For more information, see the news on July 30, 2020, LINE's APIs will support HTTP/2.

We've changed the SSL certificate used in LINE's API servers. As a result, we've changed the root certificate authority from DigiCert to GlobalSign.

# Domain names subject to this change

  • api.line.me
  • api-data.line.me
  • access.line.me

# Date and time of change

  • For access from Japan: July 10, 2020 17:17 ~ 17:54 JST (GMT+9)
  • For access from outside Japan: August 4, 2020 12:00 ~ 16:00 JST (GMT+9)

# Impact

Due to this update, if an SSL communication problem occurs on the client side using the LINE API, it is possible that the corresponding root certificate (GlobalSign Root R3) does not exist.

If you observe this problem, please update the root certificate to the latest version on the client side using the API.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LIFF v2.3.1 released

We've now released LIFF v2.3.1. The changes in LIFF v2.3.1 are as follows:

There are no feature updates in this release.

# Problems with the LIFF SDK npm package documentation were fixed

We fixed an issue with the npm official site documentation for the LIFF SDK npm package that was experimentally released.

# Installation and usage instructions of the LIFF SDK npm package were moved

We moved the installation and usage instructions of the LIFF SDK npm package from the npm official website to the LINE Developers site. For more information, see Use the npm package.

New feature has been added to the LIFF header

As announced on July 6, 2020, a new feature has been added to the LIFF header.

LIFF header design to be improved

# The LIFF app icon is no longer displayed

The icon in the upper left corner of the LIFF app is no longer displayed.

# The share button has been added

LIFF apps with the size of the LIFF app view set to Full include a share button in the header. When a user taps the share button, the following options appear:

Item Description
Share Shares the URL of the current page via a LINE message.
Refresh Reloads the current page.

Enable Module mode of the LIFF app in the LINE Developers console to hide the share button. For more information, see Adding a LIFF app to your channel.

Operating environment

The share button will be available on LINE versions 10.12.0 or later for iOS and Android.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for sending webhook events (resolved)

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.

# Date and time of outage

June 29, 2020 13:20 JST (GMT+9) - July 14, 2020 17:42 JST (GMT+9)

# Cause of the outage

Due to the detection of unauthorized communications in our network, we've blocked some communications as a preventive measure.

# Details

During the date and time stated above, webhook events couldn't be sent to some bot servers (Webhook URLs) using ngrok.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Front-end Framework. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time

Date: July 13, 2020
Time: 11:44–17:26 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

During the date and time stated above, there was an issue with our server that caused an error message to display when creating a new LIFF app. Although an error message was displayed, new LIFF apps were being created. We have already completed the recovery process.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Improved Messaging API reference and side menu

The LINE Developers site's Messaging API reference page, due to the large amount of endpoints, was long and difficult to navigate.

We received feedback about the navigation pain points developers faced while navigating the Messaging API reference page. In response, we've made these improvements to provide a better user experience.

# You only see the categories you select

All endpoints are divided into categories such as Webhooks and OAuth.

You can see the overview for each category and select Show to display the category's endpoints.

Messaging API Webhooks overview

# Side menu shows current page location

When you scroll through the page, the highlighted location on the side menu automatically reflects your current location in green.

For example, when you scroll through the page and see the "response" section under the "Webhooks" category, "response" under "Webhooks" is also highlighted in the side menu.

Webhook location on page is reflected in side menu

If you're lost on the page, you can now refer to the side menu to find your location.

Developers who use the browser's in-page search should use the built-in search function to find the endpoint. You can search endpoints by title search or full-text search.

Search for an endpoint

# Tell us your thoughts about the LINE Developers site

If you use the new Messaging API Reference and notice issues or find it difficult to use, select "Was this page helpful?" in the bottom right corner and let us know.

Feedback form title

Thanks to everyone for their valuable feedback. We read each message we receive.

We will continue to improve the quality of the services we provide to our developers. Thank you for your understanding.

New feature will be added to the LIFF header

We plan to make changes to the LIFF header specifications after mid-July 2020.

LIFF header design to be improved

# The LIFF app icon will no longer be displayed

The icon in the upper left corner of the LIFF app will no longer be displayed.

# The share button will be added

LIFF apps with the size of the LIFF app view set to Full will include a share button in the header. When a user taps the share button, the following options will appear:

Items Description
Share Shares the URL of the current page via a LINE message.
Refresh Reloads the current page.

You can hide the share button by changing the settings of the LIFF app in the LINE Developers console. This option will be added in the future.

Operating environment

The share button will be available on LINE versions 10.12.0 or later for iOS and Android.

# Scheduled date of specification change

The specification change is scheduled to take place in mid-July 2020 or later.

The content and date of the specification change is subject to change without notice. We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LINE MINI App docs and entry point of contact opened

LINE MINI App opened its documents and entry point of contact.

# What is LINE MINI App?

LINE MINI App is a web application that runs on LINE.

With LINE MINI App, users can use various services without having to install separate apps.

LINE MINI App provides even more features than the existing LINE Front-end Framework (LIFF) App, including the ability to send a message called a "service message" to a special talk room.

Service Message

For details, see Discover LINE MINI App.

# How to develop LINE MINI App

In order to develop a LINE MINI App and provide it to your users, you must create a LINE MINI App Channel in the LINE Developers console.

Currently, only developers of services that have applied to Enroll in the LINE MINI App Development Program and have passed the pre-examination are allowed to create a LINE MINI App Channel.

Please take this opportunity to Enroll in the LINE MINI App Development Program.

# LINE MINI App Development Documents

Please see the below information necessary for LINE MINI App development.

Get all valid channel access tokens 2.1 is deprecated

As announced on June 22, 2020, the Get all valid channel access tokens v2.1 API endpoint is now deprecated and will be permanently removed on July 29, 2020.

If you're using this endpoint, change your bot to use the newly added Get all valid channel access token key IDs v2.1 endpoint by the specified EOL date.

Learn more about Issue channel access token v2.1 in the Messaging API documentation.

LIFF SDK released as an npm package

Until now, to include the LIFF SDK in a LIFF app, it was necessary to Specify the CDN path.

Today, we released the LIFF SDK npm package on a trial basis. Now you can use npm and Yarn to install the LIFF SDK.

For more information on the LIFF SDK npm package, see https://www.npmjs.com/package/@line/liff.

The available LIFF SDK versions as an npm package is v2.3.0 or later. The features of future LIFF SDK versions will be announced in Release Notes in the LIFF Documentation.

npm package trial

The npm package is available on a trial basis. It may be changed or deleted in the future without notice.

LINE's APIs now support TLS 1.3

Added July 30, 2020

For access to the APIs from outside Japan, TLS 1.3 will be available after August 4, 2020. For more information, see the news on July 30, 2020, LINE's APIs will support HTTP/2.

LINE's APIs now support TLS 1.3.

# Domain names subject to the update

  • api.line.me
  • api-data.line.me
  • access.line.me

# SSL/TLS supported protocol versions

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

Protocol version Before update After update
TLS 1.3
TLS 1.2
TLS 1.1
TLS 1.0
SSL 3.0
SSL 2.0

# Impact

If you are using any of the above APIs, please confirm that your app can communicate using the updated supported protocol versions.

# Transition period

  • For access from Japan: TLS 1.3 is available after July 1, 2020.
  • For access from outside Japan: TLS 1.3 is available after August 4, 2020.

Support for TLS 1.0 and TLS 1.1 will be discontinued in the future. The discontinuation schedule is undecided. We will make an announcement as soon as it is decided.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Beacon Leave Event to be deprecated at the end of 2020

July 8, 2020

We clarified the contact information. We apologize for any inconvenience this may have caused you.

As announced previously, the leave event of Beacon Event, will be deprecated. Please refer to the following schedule:

Schedule Description
End of 2020 Leave event will be deprecated.
Early January of 2021 Webhook transmission will cease
Tip

We will continue supporting other Beacon events (enterevent, bannerevent, or stayevent).

# Impact

Please adjust your service to use the stay event instead of the leave event for detecting when users exit the reception range of Beacon.

beacon.type Description
leave [To be deprecated at the end of 2020] User left the reception range of Beacon.
stay User is currently within the reception range of Beacon.
This event is sent repeatedly at a minimum interval of 10 seconds.

If you wish you use the stay event, contact your sales representative or contact our Sales partners.

We apologize for any inconvenience the deprecation of the leave event may have caused. LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.

LIFF v2.3.0 released

We've now released LIFF v2.3.0. The changes in LIFF v2.3.0 are as follows:

# You can now use paths and query parameters in the LIFF endpoint URL

As announced before, you can now use paths (/path) and query parameters (?key=value) added to the LIFF endpoint URL in the LIFF tab of the LINE Developers console.

Existing LIFF apps aren't effected until the setting is changed

It's necessary to change the setting in LINE Developers console to use the new specs in existing LIFF apps. Existing LIFF apps aren't affected by the new spec until the setting is changed.

Methods for converting additional information in the LIFF URL

To use the new specs, set Methods for converting additional information in the LIFF URL to Concatenate.
Don't change the setting if your existing LIFF app doesn't support the new specs. If setting to Replace (Backward compatibility mode), the LIFF app isn't affected by the new specs.

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

When executing the liff.permanentLink.createUrl() method, an exception is thrown if the current page URL doesn't start with the URL specified in Endpoint URL.

try {
    const myLink = liff.permanentLink.createUrl()
}
catch (err) {
    console.log(err.code + ':' + err.message);
}

Especially when setting Methods for converting additional information in the LIFF URL to Replace (Backward compatibility mode), the paths and query parameters (/2020campaign/?key=value) specified in Endpoint URL may not be included in the secondary redirect URL. In this case, you can't get a permanent link because the liff.permanentLink.createUrl() method meets the above conditions.

For more information, see liff.permanentLink.createUrl() in the LIFF v2 API reference.

# You can now get the send results of liff.shareTargetPicker()

As announced on April 21, 2020, you can now get the send results of liff.shareTargetPicker().

Before the spec change, the LIFF app was able to confirm whether the target picker was displayed, but not whether the message was sent after that.

After the change, the LIFF app is able to check whether the message has been sent, so you can change the behavior of the LIFF app depending on the user's situation.

Note
  • The return value of liff.shareTargetPicker() is changed due to this spec change.
  • This spec change doesn't affect users using LINE 10.3.0 - 10.10.0.

# Sample code for this spec change

We recommend you to handle the return value according to the LINE versions that users are using as shown below:

if (liff.isApiAvailable('shareTargetPicker')) {
  liff.shareTargetPicker([
    {
      'type': 'text',
      'text': 'Hello, World!'
    }
  ])
    .then(function (res) {
      if (res) {
        // succeeded in sending a message through TargetPicker
        console.log(`[${res.status}] Message sent!`)
      } else {
        const [majorVer, minorVer] = (liff.getLineVersion() || "").split('.');
        if (parseInt(majorVer) == 10 && parseInt(minorVer) < 11) {
          // LINE 10.3.0 - 10.10.0
          // Old LINE will access here regardless of user's action
          console.log('TargetPicker was opened at least. Whether succeeded to send message is unclear')
        } else {
          // LINE 10.11.0 -
          // sending message canceled
          console.log('TargetPicker was closed!')
        }
      }
    }).catch(function (error) {
      // something went wrong before sending a message
      console.log('something wrong happen')
    })
}

For more information, see liff.shareTargetPicker() in the LIFF v2 API reference.

# An error code returned by liff.sendMessages() added

Previously, if passing the wrong parameters to liff.sendMessages(), 400 was returned as the error code of LiffError. After the spec change, INVALID_ARGUMENT is returned instead.

As long as the processing isn't split by error codes, this spec change doesn't effect your LIFF app.

Before the spec change:

liff.sendMessages([
  {
    type: 'text',
    text: 'Hello, World!'
  }
])
  .then(() => {
    console.log('message sent');
  })
  .catch((err) => {
    // Returns "400" if invalid arguments are passed
    if (err.code === "400") {
      console.log("message format error!");
    }
  });

After the spec change:

liff.sendMessages([
  {
    type: 'text',
    text: 'Hello, World!'
  }
])
  .then(() => {
    console.log('message sent');
  })
  .catch((err) => {
    // Returns "INVALID_ARGUMENT" if invalid arguments are passed
    if (err.code === "INVALID_ARGUMENT") {
      console.log("message format error!");
    }
  });

For more information, see Error details in the LIFF v2 API reference.

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: 2020/6/24 Time: 15:30-16:14 JST (GMT+9)

# Cause

Issues with our servers.

# Details

The LINE Login process did not work properly in some cases.

Auto login and LINE login with Single Sign On (SSO) were not affected.

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

The key IDs to identify Channel Access Tokens have been added

The endpoint to Get all valid channel access tokens v2.1 returns re-encrypted channel access tokens for security reasons. Even for the same channel access token, the value changes when issuing and getting it, making it difficult to manage and identify the token.

With this update, when Issuing the channel access token v2.1, a unique key ID (key_id) paired with the token is also returned. You can use the newly added Get all valid channel access token key IDs v2.1 endpoint to identify paired channel access tokens.

Plan to deprecate endpoint

Due to this update, we'll soon deprecate the Get all valid channel access tokens v2.1 endpoint (early July). If you are using this endpoint, change your bot to use the newly added Get all valid channel access token key IDs v2.1 endpoint instead.

Learn more about Issue channel access token v2.1 in the Messaging API documentation.

LIFF v2.2.0 released: LIFF error codes added

The LiffError codes passed when Promise is rejected in the following methods have been made more detailed, making the cause of the problem easier to understand.

For more information, view the Error Response descriptions for these methods:

The location of the "Linked OA" setting was moved within the LINE Developers console

The location of the Linked OA setting in specific channel types was moved within the LINE Developers console.

Items Before the change After the change
Location of Linked OA Under the LINE Login tab in a channel Under the Basic settings tab in a channel

# Affected channel types

  • LINE Login
  • [BETA] Blockchain Service

# Impact

The behavior of existing LINE Login or Blockchain service channels will not be impacted by this update.

New channel types added after this update on the LINE Developers console which include the Linked OA setting will have the updated location applied.

For information on how to configure Linked OA, see Link a LINE Official Account with your channel.

Messaging API update for June 2020

We added new endpoints to the Messaging API. These are the new features added to this update:

Endpoints

This is a summary of each new feature. For details, see each new feature in the Messaging API reference.

# Get group summary

Gets the group ID, group name, and group icon URL of a group where the LINE Official Account is a member.

For more information, see Get group summary in the Messaging API reference.

# Get number of users in a group

Gets the count of users in a group. You can get the user in group count even if the user hasn't added the LINE Official Account as a friend or has blocked the LINE Official Account.

For more information, see Get number of users in a group in the Messaging API reference.

# Get number of users in a room

Gets the count of users in a room. You can get the users in room count even if the user hasn't added the LINE Official Account as a friend or has blocked the LINE Official Account.

For more information, see Get number of users in a room in the Messaging API reference.

Flex Message Simulator tutorial now available

We published our first tutorial about using the Flex Message Simulator.

Following this tutorial, you will obtain hands-on experience and knowledge about how to use the Flex Message Simulator. By the end of the tutorial, you will have created this digital business card using Flex Message:

Final Output

We encourage you to take this opportunity to learn to use the Flex Message Simulator and create your own unique Flex Message.

[Updated] Publish API documentation to get a permanent link

Added on July 15, 2020

There was a mistake in the API method name. We've corrected the mistake and apologize for any inconvenience caused by this error.

Incorrect:

liff.permanentLink.setExtraQueryParams()

Correct:

liff.permanentLink.setExtraQueryParam()

The LIFF SDK keeps a permanent link for the current page. We'll publish the documentation of the API that handles this permanent link.

  • liff.permanentLink.createUrl()
  • liff.permanentLink.setExtraQueryParam()

These APIs are already included in the latest LIFF SDK, so the LIFF SDK version doesn't change.

For more information on how to get a permanent link, see Get a permanent link for the current page in the LIFF documentation.

[Updated] You can soon add and use paths to your LIFF endpoint URL

Added on May 29, 2020

This specification change was scheduled to take place in the last week of May, 2020, but in consideration of the impact on existing LIFF applications, we will apply the following changes:

  • As announced on May 20, 2020, we will add the functionality to allow paths in endpoint URLs.
  • We plan to change specifications in such a way that existing LIFF apps will not be affected.
  • Specification change is scheduled for the second half of June 2020.

We apologize again for the inconvenience caused by the repeated specification changes.

Currently, developers are able to enter the path (/path), query parameters (?key=value), and URL fragments (#URL-fragment) in the URL in the LIFF tab of the console, but only the domain name and query parameters of the URL string are used.

With the upcoming update, these improvements will be made to the LIFF endpoint URL:

  • The path (/path) can be used.
  • The URL fragments (/#URL-fragment) can no longer be entered.

For example, if you're deploying the LIFF app on Heroku, you can enter https://{Heroku app name}.herokuapp.com/path/?key=value as the Endpoint URL in the Basic information section of the LINE Developers console.

LIFF URL with paths appended in the console

The URL scheme must use https.

Being able to use the paths you entered in the console means less time is required to publish new web pages. For example, when publishing a page for a campaign, you can register the campaign page such as https://example.com/2020campaign directly in the endpoint URL.

Note

The endpoint URLs registered in the console and the URL scheme for opening a LIFF app differ in the use of URL fragments. Be careful not to confuse them.

Endpoint URL:
https://example.com/2020campaign or https://example.com/2020campaign/?key=value
You can't add URL fragments.

URL scheme for opening a LIFF app:
https://liff.line.me/{liffId}/path_A/path_B/#URL-fragment
You can add URL fragments.

Learn more about Adding a LIFF app to your channel in the LIFF documentation.

We apologize for the confusion caused by the previous specification. We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

# Scheduled date of specification change

Second half of June, 2020

OGP tags are now available in the LIFF app

By setting an OGP tag for each page of your LIFF app, for example, you can display any title, description, or thumbnail image when sharing the URL of your LIFF app (https://liff.line.me/{liffId}) in the LINE talk room, and so on.

These are the OGP tags supported by LIFF. For more information on OGP tags, see The Open Graph protocol.

<html lang="ja" prefix="og: http://ogp.me/ns#">
<meta property="og:title" content="The title">
<meta property="og:type" content="`website`, `blog`, or `article`">
<meta property="og:description" content="A one to two sentence description">
<meta property="og:url" content="The URL">
<meta property="og:site_name" content="The name that represents the overall site">
<meta property="og:image" content="An image URL">
Note

When sharing the URL of the LIFF app in the format of line://app/{liffId} (deprecated), the OGP tag will be ignored.

Messaging API update for May 2020

We made several improvements to the Messaging API.

# Message character limit and media file usage conditions have been changed

The character limit for text messages and the conditions for media files that can be used have changed. See this table for a comparison of the previous and current situation:

  • Text message

    Items Previous Current
    Max character limit 2000 5000
  • Rich menu object (Image)

    Items Previous Current
    Image size
    (width x height)
    2500px × 1686px
    2500px × 843px
    1200px × 810px
    1200px × 405px
    800px × 540px
    800px × 270px
    800px or more x 2500px or less*

    * The width/height aspect ratio should be at least 1.45.

  • Image message (Image)

    Items Previous Current
    File format JPEG JPG, JPEG, PNG
    Max image size 4096px × 4096px No limit
    Max file size 1MB 10MB
  • Video message (Video)

    Items Previous Current
    Max length 1 minute No limit
    Max file size 10MB 200MB
  • Audio message (Audio)

    Items Previous Current
    Max length 1 minute No limit
    Max file size 10MB 200MB
  • Imagemap message (Image)

    Items Previous Current
    Max file size 1MB 10MB
  • Imagemap message (Video)

    Items Previous Current
    Max length 1 minute No limit
    Max file size 10MB 200MB
  • Image message / Video message / Imagemap message (Preview image)

    Items Previous Current
    File format JPEG JPEG, PNG
    Max image size 240px x 240px No limit

# Getting LINE emoji information from the text object of a webhook event

If the text sent by users contains a LINE emoji, the emojis property of the text message object received by webhook contains information about the used LINE emoji as a LINE Emoji object.

LINE emoji information has been added to the webhook message event object. If the text containing a LINE emoji is sent by users, the emojis property will contain information about the used LINE emoji as a LINE emoji object.

LINE emoji are identified by a productId and emojiId:

{
  "replyToken": "nHuyWiB7yP5Zw52FIkcQobQuGDXCTA",
  "type": "message",
  "mode": "active",
  "timestamp": 1462629479859,
  "source": {
    "type": "user",
    "userId": "U4af4980629..."
  },
  "message": {
    "id": "325708",
    "type": "text",
    "text": "Hello, world! (love)",
    "emojis": [
      {
        "index": 14,
        "length": 6,
        "productId": "5ac1bfd5040ab15980c9b435",
        "emojiId": "001"
      }
    ]
  }
}

For details, see the Text section in the Messaging API reference.

# Safely retrying a failed API request

If an error occurs when sending a message using the Messaging API, or if the request times out, you may not know if the message was correctly delivered to users. Executing the same request causes users to receive the same message twice if the first request was received correctly.

You can safely retry the same request by adding a retry key (X-Line-Retry-Key) to the HTTP request header.

An arbitrarily generated UUID in hexadecimal notation (example: 123e4567-e89b-12d3-a456-426614174000) is specified as the value of a retry key. No matter how many times the API request containing the same UUID value of a retry key is executed, it is always accepted only once, preventing the same process from being duplicated. The retry key can now be used to design a secure API request retry.

curl -v -X POST https://api.line.me/v2/bot/message/push \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer {CHANNEL_ACCESS_TOKEN}' \
-H 'X-Line-Retry-Key: {UUID}' \
-d '{
    "messages": [
        {
            "type": "text",
            "text": "Hello, user"
        }
    ]
}'

For details, see Retrying a failed API request.

LIFF Versioning policy and life cycle have been released

We released the LIFF Versioning policy to clarify the purpose of each version of LIFF. We've also released the life cycle of each MAJOR version so that developers can make appropriate preparations for the version upgrade of LIFF.

Use the latest version of LIFF SDK

As announced on October 16, 2019, LIFF v1 will be discontinued. After discontinuation, you cannot open LIFF apps that used LIFF v1.

For more information about the MAJOR version life cycle and the dates when LIFF v1 will be discontinued, see Life cycle of the LIFF SDK in the LIFF documentation.

# The LIFF Versioning policy

Beginning with LIFF v2.2.0, the version number of LIFF will follow the rules set by Semantic Versioning (SemVer).

SemVer defines this version format:

MAJOR.MINOR.PATCH

For example, in v1.2.3, 1 is the MAJOR version, 2 is the MINOR version, and 3 is the PATCH version.

The LIFF Versioning policy also explains the life cycle of the MAJOR version and provides an explanation for what each version (MAJOR, MINOR, PATCH) means for developers.

# LIFF SDK (sdk.js) update policy

Since the LIFF v2.1.13 release, we prepare these two types of CDN paths. When Integrating the LIFF SDK into LIFF app, specify the CDN path that suits your purpose.

CDN path Description
CDN edge path This is a method to specify only the MAJOR version. You can always use the new version of the LIFF SDK without updating your LIFF app.
e.g.: https://static.line-scdn.net/liff/edge/2/sdk.js
CDN fixed path This is a method to specify up to the PATCH version. You can continue to use the specified PATCH version as long as you don't update the LIFF app. It is not updated automatically and is not affected by the LIFF SDK update.
e.g.: https://static.line-scdn.net/liff/edge/versions/2.1.13/sdk.js

Example of specifying a CDN edge path:

<script charset="utf-8" src="https://static.line-scdn.net/liff/edge/2/sdk.js"></script>
The CDN path to maintain backwards compatibility

In order to certify the behavior of the created LIFF app, we will continue to provide the LIFF SDK with the following CDN path. The LIFF SDK available with this CDN path is the same version as the LIFF SDK available with the CDN edge path.

CDN path for backwards compatibility:
https://static.line-scdn.net/liff/edge/2.1/sdk.js

Note

The CDN path to maintain backwards compatibility may be discontinued regardless of Life Cycle Schedule of the LIFF SDK. We recommend changing the CDN path specified in your LIFF app to the CDN edge path.

We will inform you as soon as the policy is decided.

Learn more about the LIFF Versioning policy in the LIFF documentation.

Notice about resumption of service for some APIs for 'Audience' and 'Insight'

We announced the outage of APIs for "Audience" and "Insight" on April 22, 2020. The APIs are now available with a limit.

Please note that depending on the delivery date and time of the message, the creation of impression-based regargeting audience may be limited, and a reference value may be returned.

  • Delivery date of the message subject to the limit (JST) : Until March 29, 2020 23:59:59
    There are no limits.

    • You can create an audience.
    • Normal statistics will be returned.

  • Delivery date of the message subject to the limit (JST) : Between March 30, 2020 00:00:00 and April 29, 2020 23:59:59
    There are limits.

    • You can't create an audience.
    • Reference values will be returned for overview.uniqueImpression and messages[].impression.

  • Delivery date of the message subject to the limit (JST) : From April 30, 2020 00:00:00
    There are limits.

    • You can create an audience. However, if a user opens a message during this time period in a LINE app with a version subject to this limit, the user will not receive a new message sent using the audience.
    • Normal statistics will be returned. However, the statistics will not include the number of times the user with a LINE version subject to the limit opened the messages sent during this period.

For more information, see the following pages:

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for the Messaging API (resolved)

We'd like to inform you about a service outage regarding the Messaging API. All functions provided by the Messaging API may have been affected by this outage.

The issue has now been resolved. The Messaging API has been operating normally since the following date and time. We apologize for the delayed announcement and any inconvenience that this may have caused.

# Date and time of outage

Date: April 24, 2020 Time: 14:41-17:46 (GMT+9)

# Cause

Network failure

# Affected services

All functions provided by the Messaging API may have been affected by this outage.

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

liff.getLineVersion() and liff.id added to LIFF v2

We added the liff.getLineVersion() method and the liff.id property to LIFF v2.

liff.getLineVersion() allows you to get the user's LINE version.

If a user opens the LIFF app using LINE's in-app browser, the LINE version of the user is returned as a string. If a user opens the LIFF app using an external browser, null is returned.

liff.id is the property that holds the LIFF app ID (String type) passed to liff.init().

Learn more about liff.getLineVersion() and liff.id in the LIFF v2 API reference.

[Updated] Notice about service outage in the aggregation of some APIs for 'Audience' and 'Insight'

Updated on May 1, 2020

The API we reported on April 22, 2020 is now available with a limit.

For more information, see the following pages:

We'd like to inform you about the following service outage regarding our Messaging API. We apologize for any inconvenience this may have caused.

# Date and time of outage

Date: 2020/04/13 Time: Since about 15:30 (GMT+9) (Ongoing)

# Details

After the time above, you may no longer be able to count impressions correctly in an audience for impression-based retargeting.

Therefore, we temporarily restrict the use of some features. Specifically, we will take the following actions.

We are currently investigating and responding to the issue.

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

Notice about the return value of liff.shareTargetPicker()

We will change the return value of liff.shareTargetPicker() on LIFF v2 in the future. If you are developing an app that uses the current specification, change the implementation.

Note

The specification for the return value of liff.shareTargetPicker() after the change isn't currently fixed.

# Summary

Before the specification change, the LIFF app could check whether the target picker could be displayed but couldn't check whether the message could be sent.

After the specification change, the LIFF app can check whether a message has been sent or not, so you can implement a change in LIFF app behavior to suit the user's situation.

# Before the specification change

# Sample

if (liff.isApiAvailable('shareTargetPicker')) {
  liff.shareTargetPicker([
    {
      type: "text",
      text: "Hello, World!"
    }
  ])
    .then(
      console.log("ShareTargetPicker was launched")
    ).catch(function(res) {
      console.log("Failed to launch ShareTargetPicker")
    })
}

# Syntax

liff.shareTargetPicker(messages)

# Return value

Returns a Promise object.

When the target picker is displayed, the Promise resolves.

If a problem occurs before the target picker is displayed, the Promise is rejected and a LiffError is passed. For more information on the LiffError object, see LIFF SDK errors.

Note
  • Situations after the target picker is displayed can't be detected, such as when the user doesn't select a destination in the displayed target picker.
  • In the callback function where the Promise has been resolved and rejected, the LIFF app won't work on some devices if the developer uses alert().

# After the specification change

# Sample

if (liff.isApiAvailable('shareTargetPicker')) {
  liff.shareTargetPicker([
    {
      type: "text",
      text: "Hello, World!"
    }
  ])
  .then(function(res) {
    if (res) {
      // succeeded to send message in TargetPicker
      console.log(`[${res.status}] Message [${this.msgType}] is sent!`)
    } else {
      // canceled to send message
      console.log('TargetPicker was closed!')
    }
  }).catch(function(error) {
    // something wrong happened before sending message properly
    console.log('something wrong happen')
  })
}

# Syntax

liff.shareTargetPicker(messages)

# Return value

Returns a Promise object.

If the message is sent correctly, the Promise is resolved and a success is passed.

If the user cancels and closes the target picker before sending the message, the Promise is resolved, but no success is passed.

If a problem occurs before the target picker is displayed, the Promise is rejected and a LiffError is passed. For more information on the LiffError object, see LIFF SDK errors.

We plan to change the error definition as the specification changes in the future.

Note

In the callback function where the Promise has been resolved and rejected, the LIFF app won't work on some devices if the developer uses alert().

# Scheduled date of specification change

TBD

[Updated] Messaging API update for April 2020

Updated on April 16, 2020

We've changed the following property names, which were announced on April 14 2020.

Before changes After changes
sticon emojis
sticon.sticonId emojis.emojiId

We made several improvements to the Messaging API.

# Use LINE emoji in messages

In addition to standard unicode emoji and (deprecated) LINE original emoji, you can now include LINE emoji when you send a text message with the Messaging API.

LINE emoji are identified by a productId and emojiId:

// Text message example with LINE emoji
{
    "type": "text",
    "text": "Look at this: $ It's a LINE emoji!",
    "emojis": [
        {
            "index": 14,
            "productId": "5ac1bfd5040ab15980c9b435",
            "emojiId": "001"
        }
    ]
}

For details, see the Text message section in the Messaging API reference.

# Get user's language

The Get profile endpoint now returns a language property in addition to other user profile information, provided one of these situations applies:

  • User has a LINE account created in Japan and has agreed to the Privacy Policy of LINE version 8.0.0 or later
  • User has a LINE account created in Taiwan, Thailand, or Indonesia and has agreed to the Privacy Policy of LINE version 8.9.0 or later

# Multicast recipient limit removed

Previously, messages sent with the Send multicast message endpoint were limited to a maximum number of recipients. This limit has been removed. Other rate limits remain in place. See this table for a comparison of the previous and current situation:

Bot type Previous limitations Current limitations
Bots associated with LINE Official Accounts 100,000 requests per minute
1,700 requests per second*
2,000,000 recipients per minute
100,000 requests per minute
1,700 requests per second*
Bots associated with LINE@ accounts 10,000 requests per minute
170 requests per second*
200,000 recipients per minute
10,000 requests per minute
170 requests per second*

* The rate limit in seconds is a guideline for mass transmission.

In addition, you can now target up to 500 user IDs (increased from 150) with a single multicast message.

For more details, see the Rate limits section of the Messaging API reference.

Full-text search is back

In the LINE Developers site redesign, announced January 27, 2020, we improved the speed of the site search by implementing title search instead of a full-text search.

We listened to the feedback and have reimplemented full-text search.

When you want to use the full-text search, enter the query in the search bar and select Full-text search from the menu.

Full-text search

Once selected, the full-text search results will appear.

Full-text search result

Thank you for the valuable feedback. LINE will continue to improve the LINE Developers site to offer a smoother experience for its users.

Channel access token v2.1 released

We released the latest version of the channel access token. This new version lets the user specify the expiration date and also provides security enhancements by switching to using a JSON Web Token (JWT) instead of the channel secret.

We recommend using the latest version of the channel access token.

Generate a JWT

You can use any JWT library or write your own code from scratch to Generate a JWT from your Assertion Signing Key. This is a necessary step in the Issue channel access token v2.1 API.

# New APIs

To learn the difference between the currently available channel access tokens, read Channel access tokens in the Messaging API documentation.

liff.isApiAvailable() added to LIFF v2

We added the method liff.isApiAvailable() to LIFF v2. This method checks whether a specified API can be used in the environment where the LIFF app was launched.

Note

The number of APIs you can specify is limited. Currently, you can only specify liff.shareTargetPicker(). We'll notify you when more APIs can be checked with liff.isApiAvailable() in the future.

# Check if share target picker is available

By executing liff.isApiAvailable() before you execute liff.shareTargetPicker(), you can avoid the user getting an error message on their screen if the share target picker isn't available in their device environment.

if (liff.isApiAvailable('shareTargetPicker')) {
  liff.shareTargetPicker([
    {
      type: "text",
      text: "Hello, World!"
    }
  ])
    .then(
      alert("ShareTargetPicker was launched")
    ).catch(function(res) {
      alert("Failed to launch ShareTargetPicker")
    })
}

Learn more from liff.isApiAvailable() in the LIFF v2 API reference.

The consent screen for LINE Login authorization has changed

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.

New "message sticker" resource type added to sticker message webhook event

Following the release of message stickers (stickers with a customizable text), we have added PER_STICKER_TEXT to the stickerResourceType property of the webhook event that notifies you when a sticker message is sent.

If a LINE user sends a message sticker to your LINE Official Account, you will receive a webhook event object containing stickerResourceType of PER_STICKER_TEXT.

For more information, see the Sticker section of the Messaging API reference.

LINE Beacon no longer supported on several LINE versions

As announced on March 10, 2020, LINE Beacon is no longer supported on the following LINE versions:

  • Japan: Any version before LINE 8.17.0
  • Taiwan: Any version before LINE 9.14.0
  • Thailand: Any version before LINE 9.8.0
  • Indonesia: Any version before LINE 9.8.0 (no change)

# Influence

Users that use these versions of LINE will not be detected when they enter or exit the reception area of a beacon.

  • Webhook beacon events are not sent to bot apps.
  • The beacon banner is not displayed for the corresponding user.

For more information about LINE Beacon, see Using Beacons.

We apologize for any inconvenience this may have caused. LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.

LINE URL scheme of 'line://' is deprecated

line:// is deprecated because it allows a takeover attack of the LINE URL scheme. Use https://line.me/R/ or https://liff.line.me/ instead.

A line:// takeover attack is an attack in which a user clicks on a URL following line://, a non-LINE app may start regardless of the intention of the LINE user. This attack is only established under certain conditions.

line:// may be discontinued in the future. If this is decided, an announcement will be made here.

For more information on LINE URL scheme, see "Using LINE features with the LINE URL scheme".

Reminder: Notice of domain name change for certain endpoints (Domain names must be updated by April 30, 2020)

As announced on November 8, 2019, the domain name of certain Messaging API endpoints has been changed from api.line.me to api-data.line.me.

# Target endpoint

# Influence

If you are using the above endpoints, please change your domain during the transition period.

Once the transition period ends, accessing an endpoint of the old domain name will return a 404 status code.

We apologize for any inconvenience this may case. Thank you for your understanding.

# Transition period

November 8, 2019 - April 30, 2020

You can now change the icon and display name of your LINE Official Account

The push/reply API request extension of the Messaging API to change icon and display name of LINE Official Account is now generally available. This was previously an optional feature for corporate users.

As shown by a green frame, you can specify icon or display name when sending a message from LINE Official Account.

Change icon and display name

For more information, see Change icon and display name.

# Properties added to Messaging API

sender.iconUrl for specifying icon and sender.name for specifying display name have been added to Messaging API. The properties can be specified in all the message objects.

For more information about each property, see “Change icon and display name” section of the Messaging API reference documentation.

LINE Beacon no longer supported on several LINE versions from March 25, 2020

LINE Beacon will no longer be supported on the following LINE versions:

  • Japan: Any version before LINE 8.17.0
  • Taiwan: Any version before LINE 9.14.0
  • Thailand: Any version before LINE 9.8.0
  • Indonesia: Any version before LINE 9.8.0 (no change)

This change will take effect from March 25, 2020 to March 26, 2020.

# Influence

Users that use these versions of LINE will not be detected when they enter or exit the reception area of a beacon.

  • Webhook beacon events are not sent to bot apps.
  • The beacon banner is not displayed for the corresponding user.

For more information about LINE Beacon, see Using Beacons.

We apologize for any inconvenience this may have caused. LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.

All Narrowcast and Audience Management documentation now available in English

All documentation about sending narrowcast messages and managing audiences with Messaging API is now available in English.

Newly translated content:

Previously translated content (see news for February 19, 2020):

For previous announcements about the Narrowcast and Audience Management features, see these past news posts:

liff.shareTargetPicker() and liff.ready added to LIFF v2

We added liff.shareTargetPicker() and liff.ready to LIFF v2.

# liff.shareTargetPicker()

Execute the liff.shareTargetPicker() method to display the target picker (screen for selecting a group or friend) and send the message created by the developer to the selected target. This message appears to your group or friends as if you had sent it.

target picker

For more information, see Sending messages to a user's friend (share target picker) in the LIFF documentation.

Target picker operating environment

Target picker is supported by LINE 10.3.0 for iOS and Android.

# liff.ready

With liff.ready, you can get the Promise object that resolves when you run liff.init() for the first time after starting the LIFF app. If you use liff.ready, you can execute any process after the completion of liff.init().

For more information, see liff.ready in the LIFF v2 API reference.

English documentation for Messaging API narrowcast features published

The documentation about sending narrowcast messages and managing audiences with Messaging API is now (partially) available in English:

Some content still remains in Japanese, but will be translated to English soon:

For the original announcements of the above Messaging API features, see these past news posts:

BLE functions for LIFF apps on LINE Things no longer provided when creating a new app

As of February 10, 2020, the new BLE function of the LIFF app will no longer be provided in the LINE Things Developer Trial when creating a new app.

Now, the LINE Things Developer Trial will only offer automatic communication.

The LINE Things Developer Trial does not plan to provide the BLE function of the LIFF app again.

We apologize for any inconvenience this may have caused. LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.

Notice about LIFF v1 APIs and discontinuation schedule change

We announced that the end-of-life of LINE Front-end Framework (LIFF) server API was scheduled for March 31, 2020. Due to feedback received, we will continue to provide the API.

As for LIFF v1, we will announce the discontinuation schedule as soon as it is decided. In the meantime, we recommend that you migrate from v1 to v2 as soon as possible.

Feature Schedule before this update Schedule after this update
LIFF v1 Client API Scheduled for discontinuation Scheduled for discontinuation (This has not changed)
LIFF v1 Server API Scheduled for discontinuation on March 31, 2020 Support continues
LIFF v1 will still be discontinued

As announced on October 16, 2019, LIFF v1 will be discontinued. Use the latest version of LIFF.

Users can no longer add LIFF apps to Messaging API channels

As announced on November 11, 2019, due to a function enhancement with LIFF v2, users can no longer add LIFF apps to Messaging API channels.

To find out about restrictions on LIFF apps already added to the Messaging API channel, and how to transition to the LINE Login channel, see the above news article.

Audience sharing now available

You can now use audiences created with the Messaging API in LINE Official Account Manager and LINE Ads.

Audiences help with advanced advertisement targeting. By using audiences, you can send messages to users who have opened a previous message or clicked on a message URL.

Audiences created earlier now automatically appear in LINE Official Account Manager and LINE Ads. You don't need to change any settings.

For more information about audiences, see Using audiences in the Messaging API documentation (English version coming soon).

Introducing the redesigned LINE Developers site

We're excited to introduce our new, redesigned LINE Developers site. We believe this update makes it easier to use the LINE Platform products and find the documentation you need.

Here are the key changes to the site:

# Pages load faster

The site is now a single-page application running on VuePress, resulting in much shorter page load times than before.

# Better readability

We've improved the responsive design of the API reference. The layout adapts to the size of your screen, making it easier to read API arguments and sample code.

As you type your search terms, suggestions appear instantly, helping you find the information you need more quickly.

Search Results

Note: Although the new search is faster, it only returns results based on page titles and headings. We'll collect internal feedback over the coming weeks to see if people are satisfied with this new search, or we need to adjust it.

(We're working hard to bring the user feedback form from the old site to the new site.)

# What's next?

In addition to bringing back the user feedback form, we'll continue looking for ways to make it easier for you to use the LINE Developers site and documentation.

Keep up-to-date with the latest developments by adding the LINE Developers Official Account as a friend with the QR code or button below.

QR code for the LINE Developers account

Add friend

Notice about Flex Message Simulator outage (resolved)

We'd like to inform you about a service outage regarding Flex Message Simulator. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

January 21, 2020 13:03 JST (GMT+9) - January 22, 2020 11:59 JST (GMT+9)

# Cause

Issues with our servers.

# Affected services

Flex Message Simulator (https://developers.line.biz/flex-simulator/)

# Details

During the specified time, Flex Message Simulator was inaccessible.

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

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:

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.

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.

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.

[Updated] Make sure the provider name is correct

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

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.

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.

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:

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.

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.

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

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:
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:

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.

New property added to "sticker message" webhook event

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 API documentation released

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.

Some LIFF functions suspended

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

# Impacted environments

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.

New LINE Developers console released

As previously announced, today we released a new version of the LINE Developers console.

This version of the console fixes several reported problems and adds various improvements to create a smoother, more reliable experience. Here are some highlights of the new release:

# Better grouping of settings

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.

Screenshot of Basic settings and Messaging API tabs

# Find providers by typing

Use the search field at the top of the provider list to filter by name and easily find the provider you're looking for.

Screenshot of search field at top of provider list

# Every role in one place

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.

Screenshot of Roles tab in channel information

We hope the new console makes it easier for you to create and manage channels. We'll continue working to improve your experience with future releases.

Maintenance notice: LINE Developers Console design update

We will perform maintenance on the LINE Developers console at the below time. We apologize for any inconvenience this may cause.

# Scheduled maintenance time

November 26, 2019 12:00-13:00 JST (+9 GMT)

# Impact

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.

# Details

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.

  • The provider list will have a filter function, letting you easily choose a provider.
  • When adding or editing an IP address on the Security tab, you can see the registered IP address.
  • You can manage the Admin, Member, and Tester users on the same tab. Before, Testers were managed on a different tab.

We also plan to improve usability by changing certain specifications.

LINE will continue to improve the quality of its services.

Users can no longer add LIFF apps to Messaging API channels

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.

# Scheduled change date

Early February 2020

# Impact

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.
Do not add LIFF apps to the Messaging API channel

At this time, users can add LIFF apps to the Messaging API channel. However, we strongly advise against it due to the following restrictions:

  • The bot link feature can't be used.
  • LIFF feature expansion may not be supported.
  • The LIFF app may not be usable in the future.

LIFF apps added to the LINE Login channel have no restrictions and can use all LIFF v2 functions.

# Transition to the LINE Login channel

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:

  • If you're using LIFF v2, change the LIFF app ID specified in liff.init().
  • The LIFF URL used to launch LIFF (e.g.: line://app/1234567890-AbcdEfgh) will change.
Remove LIFF apps added to Messaging API channel

To avoid confusion, delete the LIFF app added to the Messaging API channel after adding to the LINE Login channel.

Notice of domain name change for certain endpoints

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.

# Target endpoint

# Influence

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.

# Transition period

Today - April 30, 2020

Endpoint for obtaining user statistics now available in Thailand (TH)

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.

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

LIFF v2 released

LINE Front-end Framework (LIFF) v2 is a platform for web apps provided by LINE.

Use the latest version of LIFF

LIFF v1 will be deprecated.

# LIFF apps now run in external browsers

With LIFF v1, LIFF apps ran only in LINE's in-app 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.

# Get user profile and email

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.

# Read QR codes

You can start LINE's QR code reader and get the strings read by the user.

# Get LIFF app environment information

You can get the following details about the environment in which your LIFF app is running:

  • Operating system in which the LIFF app is running (iOS, Android, external browser)
  • Whether the LIFF app is running in the in-app browser (true, false)
  • Language settings

For more information, see LINE Front-end Framework.

New Messaging API endpoint for friend statistics

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.

Notice about service outage for the Messaging API (resolved)

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

Date: October 4, 2019

Time:

9:00-9:02 JST (GMT+9)

10:04 JST (GMT+9)

11:00-11:08 JST (GMT+9)

12:02-12:08 JST (GMT+9)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

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.

New Chinese-language news page

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:

language option

Notice about system maintenance

We're performing system maintenance at the below time. We apologize for any inconvenience.

# Scheduled maintenance time

September 26, 2019 16:20-16:50 JST (+9 GMT)

The maintenance will only last a few seconds and will take place somewhere in this time window.

# Impact

Messaging API, LINE Login, and LIFF operations may result in errors. Specifically, the following events can occur:

  • Messaging API (https://api.line.me/v2/bot/*) returns an error with status code 500.
  • An error with status code 500 is returned when a user logs in with LINE Login or starts a LIFF app.

Try out Messaging API calls in your browser

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

LINE SDK v4.x end-of-life on December 12th, 2019

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:

# Why we're doing this

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.

# Upgrading to a new SDK version

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.

Notice about service outage for the Messaging API (resolved)

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

Date: September 11, 2019 Time: 17:00–18:30 JST (GMT+9)

Date: September 12, 2019 Time: 13:00–13:30 JST (GMT+9)

# Cause

Server outage due to heavy load.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

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.

Notice about service outage for LINE Developers site (resolved)

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

Date: September 11th, 2019 Time: 13:46–15:58 JST (GMT+9)

# Cause

Issue with our servers.

# Details

During the specified time, the Statistics tab for Messaging API channels in 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.

Flex Message Simulator Update 1 (β) released

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.

Limitations

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.

Flex Message Simulator Update 1 (β)

Flex Message Update 1 examples

Notice about service outage for LINE Developers site (resolved)

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

Date: August 28, 2019 Time: 18:15 ~ 18:40 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

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.

Flex Message Update 1 released

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.

Flex Message example

Member users were able to retrieve Channel secret because of a bug (resolved)

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 time

Issue inception: September 21, 2017

Issue solved: July 17, 2019

# Details

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.

What is a 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.

Member user permissions

Originally, Member users can only view basic information and statistics for a channel. They don't have access to the channel secret.

# What you should do

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.

# How to issue a new channel secret

You can issue a new channel secret on the Channel settings tab in the LINE Developers console.

Forced reissue of channel secret

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.

# Acknowledgement

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.

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: July 18, 2019 Time: 9:38–10:40 JST (GMT+9)

# Cause

Issue with our servers.

# Details

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:

  • Web application
  • Desktop app

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

New Messaging API endpoints for friend statistics

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.

LINE SDK for Flutter released

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.

LINE Login: 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. If you haven't integrated LINE Login yet, we hope you'll consider doing so now.

Note

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.

# Date and time of outage

From: June 11, 2019
Until: June 18, 2019 14:33 JST (GMT+9)

# Cause

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

# Details

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.

Notice about service outage for LINE Login (resolved)

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

Date: June 17, 2019 Time: 11:41–13:01 JST (GMT+9)

# Cause

Issue with our servers.

# Details

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.

Notice about service outage for the Messaging API (resolved)

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

Date: June 14, 2019 Time: 10:35–12:19 JST (GMT+9)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*).

# Details

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.

Notice about service outage for the Messaging API (resolved)

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

Date: June 5, 2019 Time: 14:41–15:05 JST (GMT+9)

(Most errors were solved by 14:55.)

# Cause

Issue with our servers.

# Affected services

All Messaging API endpoints (https://api.line.me/v2/bot/*) and webhook.

# Details

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.

LINE Things: Automatic communication English documentation released

We released the English version of the LINE Things documentation about the "automatic communication" feature:

Automatic communication added to LINE Things Developers Trial

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.

Improved consent screen in LINE Front-end Framework

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.

New consent screen

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.

Changes associated with the integration of LINE@ accounts into LINE Official Accounts

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:

# Changes in the LINE Developers console

# Type of created accounts

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.

# Privacy policy and terms of use

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.

# Enhanced Messaging API features

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.

Migrating your LINE@ account under the Developer Trial plan

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.

Notice about service outage for LINE Developers site (resolved)

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

Date: April 4, 2019 Time: 14:00 ~ 15:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

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.

Messaging API: You can configure the rich menu setting for multiple users at a time

We added endpoints for the following rich menu operations:

For more information on how to use the rich menu features, see the following pages.

Documentation search feature enhanced

We enhanced the documentation search feature on the LINE Developers site.

Search results are more accurate, and keywords are highlighted in the result set so that you can find the necessary information more quickly.

Search bar

LINE SDK 5.1.0 for iOS Swift released

We released the LINE SDK 5.1.0 for iOS Swift. Get the SDK from our GitHub repository.

Changes:

  • Some model types support the Encodable protocol for easier serialization.
  • JSON conversion for Objective-C model wrapper classes is supported for future features.
  • You can get the raw ID token value for server verification.
  • Swift 5.0 and Xcode 10.2 are supported.

We won't stop looking for ways to make your coding life easier. Expect more improvements in future versions!

Notice about system maintenance

We will perform maintenance for LINE Login and the Social API. We apologize for any inconvenience caused by this.

# Scheduled maintenance time

March 05, 2019 05:30-06:30 JST (+9 GMT)

# Impact

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.

Notice about service outage for LINE Login and the Social API (resolved)

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

Date: February 26, 2019

Time: 6:46–7:16 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

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.

Introducing our new feedback form

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.

Feedback form

Notice about service outage for Messaging API (resolved)

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.

# Date and time of outage

  • Date: February 26, 2019
  • Time: Approximately 11:15-13:00 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when the following API endpoints were accessed:

  • Get content API: https://api.line.me/v2/bot/message/{messageId}/content
  • Rich menu API: https://api.line.me/v2/bot/richmenu/*

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LINE SDK 1.0.0 for Unity released

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.

Notice about service outage for the Messaging API (resolved)

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.

# Date and time of outage

  • Date: February 20, 2019
  • Time: Approximately 18:45-19:02 and 19:10-19:26 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

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.

Console: We changed how to check the number of your bot's friends

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.

Notice of LINE Developers site maintenance

On February 27, 2019, we will perform maintenance for the LINE Developers site. We apologize for any inconvenience caused by this.

# Scheduled maintenance time

February 27, 2019 12:00-13:00 JST (+9 GMT)

# Impact

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're archiving the LINE Platform feedback repository on GitHub

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.

You can get access tokens through LIFF SDK

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.

LINE Login: You can log in with a QR Code

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.

QR Code login

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.

LINE Things: English documentation released

We released the English version of the LINE Things documentation:

New endpoints added to Messaging API

We added new endpoints to the Messaging API. Use these endpoints to get the number of messages sent from your channel.

Learn more from these sections of the Messaging API reference:

Notice about service outage for the Messaging API (resolved)

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.

# Date and time of outage

  • Date: January 12, 2019
  • Time: 16:59-18:30 (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

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.

Specification change for the Messaging API

# The image and icon

Now you can specify any aspect ratio of images and icons within a certain range.

For more information, see the updated reference documentation below.

# URI action

Now you can set different action URLs for PC users (LINE for macOS and Windows) and smartphone users (LINE for iOS and Android).

For more information, see URI action.

LINE SDK 4.0.10 for Android released

The LINE SDK 4.0.10 for Android has been released. You can download the SDK from the following page.

Changes:

  • Fixed an issue where an activity is not found when authenticating with LINE Login after LINE is invalidated on the device.

We will continue to provide improvements so that you can code more easily.

[Update] Change to the imagemap message

We decided not to make the specification change of the imagemap message that we announced on November 14, 2018, for compatibility. We apologize for any inconveniences caused and appreciate your understanding.

You can continue to send imagemap messages even if you set actions in the area that does not fit the width and height of the image specified by the baseSize property.

However, the layout of such imagemap messages might be broken on the user device. We recommend setting actions within the area that fits the width and height of the image specified by the baseSize property.

The behavior of a consent screen displayed to LINE Login users has changed

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.

LINE Things Developer Trial released

LINE Things Developer Trial has been released. For usage, see the following guide and API reference:

These documentation sets will be translated into English soon.

LINE SDK 5.0.0 released

The LINE SDKs 5.0.0 for Android, iOS Swift, and iOS Objective-C have been released. For installation and usage instructions, see the following guides:

# Changes

# LINE Login v2.1 and Social API v2.1 are supported

You can set permissions to be granted to your app as scopes when users log in to your app with LINE Login. By setting scopes, you can get ID tokens when you get access tokens. Those tokens contain user information according to the scopes you set with the login request.

You can display an option to add your bot as a friend to users logging in to your app. You can get the friendship status between users and your bot with login responses and the Social API.

# New SDK version in Swift

Developed in Swift, the LINE SDK for iOS Swift provides a modern way of implementing LINE APIs. The LINE SDK 5.0.0 for iOS Objective-C is the last version of our Objective-C SDK.

# Open-source SDK

The LINE SDK for Android and iOS Swift are open-sourced. Visit the following repositories to check the provided code and samples.

# Detailed reference

Now you can access detailed reference based on the source code. For more information, see the following references:

Correction to documentation

There were errors in the news release and documentation for the new LIFF server API to update a LIFF app. We apologize for any inconvenience.

# News

【Incorrect】 The HTTP request to the API endpoint to update a LIFF app is changed from PUT to PATCH. Now you can partially update the properties of your LIFF apps.

【Correct】 The API endpoint for updating a LIFF app is changed. Now you can partially update the properties of your LIFF apps.

# API reference

【Incorrect】 PATCH https://api.line.me/liff/v1/apps/{liffId}

【Correct】 PUT https://api.line.me/liff/v1/apps/{liffId}

For more information, see Update LIFF app.

Renewed LIFF server API

Now you can set the following properties to your LIFF apps.

  • description property
  • features.ble property

The HTTP request to the API endpoint to update a LIFF app is changed from PUT to PATCH. Now you can partially update the properties of your LIFF apps.

For more information, see the following sections:

New webhook events are added for the Messaging API

We have added two webhook events: Member join event and member leave event.

For more information, see the following sections:

A new login method has been added

Now you can use your LINE Business ID to log in to the LINE Developers console.

If you are an enterprise user who satisfies both of the two conditions below, click "Log in with email" and enter the email address and password associated with your LINE Business ID to log in to the console.

  • You use the LINE Developers console for the first time.
  • You have a LINE Business ID.

Otherwise, click "Log in with LINE" and enter the email address and password associated with your LINE account to log in to the console.

Maintenance period for the LINE Developers site is extended

Today, we will perform maintenance for the LINE Developers site to change its domain name. Due to circumstances, the maintenance period is extended as below.

We apologize for any inconvenience and appreciate your understanding.

# Scheduled maintenance time

November 15, 2018 12:00-13:00 JST (+9 GMT)

The maintenance period is extended by 50 minutes.

# Impact

The LINE Developers site will be unavailable during the maintenance time.

In this maintenance the LINE Developers site's domain name will change from "developers.line.me" to "developers.line.biz". All accesses to the old domain will be redirected to the new domain.

Change to the imagemap message is scheduled

We'd like to inform you that we will change the specification of the imagemap message.

After the specification change, if the method of setting actions in imagemap messages is incorrect as below, an error occurs and you cannot send imagemap messages.

The current specification: You can send imagemap messages even if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

In this case, the layout of the imagemap displayed on the user device might be broken.

The new specification: You cannot send imagemap messages because the API request fails if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

This specification change will be released on November 27th.

Domain name change for the LINE Developers site

On November 15, 2018, we will perform maintenance for the LINE Developers site to change its domain name.

# Scheduled maintenance time

November 15, 2018 12:00-12:10 JST (+9 GMT)

# Impact

The LINE Developers site will be unavailable during the maintenance time.

In this maintenance the LINE Developers site's domain name will change from "developers.line.me" to "developers.line.biz". All accesses to the old domain will be redirected to the new domain.

Correction to documentation

There were errors in the description of the new destination property added to webhook events released yesterday. We correct it as below:

【Incorrect】The destination property includes the MID of a bot that should reeive the webhook events. The property value is a string that matches the regular expression, "u[0-9a-f]{32}".

【Correct】The destination property includes the user ID of a bot that should reeive the webhook events. The property value is a string that matches the regular expression, "U[0-9a-f]{32}".

For more information, see Request body.

Specification change for the Messaging API

# You can play videos in imagemap messages

Now you can play videos in imagemap messages.

For more information, see Imagemap message.

Note that this change doesn't include the validation of action areas of imagemap messages announced on October 24. We will inform you once we decide on our schedule.

# New properties are added to webhook events

  • The body of webhook events now includes the user ID (destination) of a bot that should receive the webhook events. For more information, see Request body.
  • New information is available in message objects for image, video, and audio messages. For more information, see Image, Video, and Audio.

Correction on November 9, 2018 : MID -> user ID

# Flex Messages can now be multicast

Now you can send Flex Messages with the /v2/bot/message/multicast endpoint.

For the /v2/bot/message/multicast endpoint, see Send multicast message in the Messaging API reference.

LIFF apps can now be added with the LINE Developers console

Now you can add LIFF apps with the LINE Developers console. As before, you can still add LIFF apps with the LIFF server API.

For more information, see Adding a LIFF app.

Change to the imagemap message is scheduled

We'd like to inform you that we will change the specification of the imagemap message.

After the specification change, if the method of setting actions in imagemap messages is incorrect as below, an error occurs and you cannot send imagemap messages.

The current specification: You can send imagemap messages even if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

In this case, the layout of the imagemap displayed on the user device might be broken.

The new specification: You cannot send imagemap messages because the API request fails if actions are set in the area that does not fit the width and height of the image specified by the baseSize property.

This specification change will be released in the week starting November 5th.

The scheme of the picture URL returned when getting a user profile has been changed

Now we support https as the scheme of the pictureUrl property. The response to the GET https://api.line.me/v2/bot/profile/{userId} request includes this property.

[Update] Discontinuation of the long-lived channel access token

We'd like to inform you of the change in the discontinuation of the long-lived channel access token that we announced in August.

We have concluded that discontinuing the long-lived channel access token by November can cause difficulty to many developers. Therefore, we will continue to support the long-lived channel access token and find alternative ways in the future that will not affect our developers.

Default rich menu can now be configured with the Messaging API

Now you can configure the default rich menu with the Messaging API.

Both default rich menus created using LINE@ Manager and the Messaging API are supported and can be used at the same time.

For more information on how to use the rich menu features, see the following pages.

More stickers are available for your bot

We have increased the number of sticker types available for bots from 342 to 462. You can create a smarter, more expressive bot with various new stickers.

For more information, see Sticker message and the sticker list.

Long-term channel access token to be discontinued

We'd like to inform you that we will discontinue the long-lived channel access token used with the Messaging API.

The discontinuation is scheduled in November 2018 with the removal of the endpoints of the Messaging API v1.

Note that the long-lived channel access token is issued only from the console. The following endpoint to issue a short-lived channel access token will not be affected.

https://api.line.me/v2/oauth/accessToken

We will provide further details for a replacement method soon.

Flex Message is now available on your desktop

Flex Message is now available on your desktop.

The feature is supported on LINE 5.9.0 for macOS and Windows.

In addition, we have added the following new Flex Message properties so that you can create messages in a more flexible way.

  • action property of the box
  • maxLines property of the text

For more information, see the following pages:

Quick reply released

We have released the quick reply feature for messages sent through the Messaging API. When a user receives a message that contains quick reply buttons, those buttons appear at the bottom of the chat screen. The user can simply tap one of the buttons to reply to your bot.

Quick reply sample

The quick reply feature is supported on LINE 8.11.0 and later for iOS and Android.

For more information, see Using quick replies.

The maximum number of LIFF apps has been increased

Now you can add up to 30 LIFF apps for one channel. The previous maximum number was 10.

For more information, see Add LIFF app in the LIFF API reference documentation.

An important message for our users in Thailand, Taiwan, and Indonesia

Important notice concerning LINE Official Accounts, LINE@ accounts, Business Connect accounts, and Customer Connect accounts The following message applies to our users in Thailand, Taiwan, and Indonesia. LINE Corporation will be collecting information from LINE Official Accounts, LINE@ accounts, Business Connect accounts, and Customer Connect accounts (OAs) in order to improve our services. You must agree to these terms by September 2, 2018.

Log in to LINE@ Manager

With these revised terms, we will work on improving services requested by OA users, such as visualization of delivery performance through message views, click counts, video views, etc. and targeting delivery based on user response logs to messages.

Clova Extensions Kit released

We have released the Clova Extensions Kit that allows you to develop skills for Clova, AI assistant from LINE. We have also released the Clova Developer Center for tutorials and documentation in Japanese.

Clova Developer Center

Now you can create skill channels in the LINE Developers console.

For more information, refer to the documentation on the Clova Developer Center.

Introducing the redesigned LINE Developers site

We are excited to introduce our new, redesigned LINE Developers site. We hope that this renewal will improve developer experience, making it easier to use the LINE Platform products. There are no major changes in the console functionality. Here, we'll take you through some of the key changes to the site.

# Changes in the console

  • We have added the provider list screen so that you can easily select the provider of the channel that you want to configure.
  • Now the role of the logged-in user is displayed in the provider and channel lists.
  • You can quickly access tools such as Flex Message Simulator and Bot Designer through the tool list in the navigation bar.

# Changes in the documentation site

  • Each page has breadcrumbs at the top so that you can easily keep track of the page structure.
  • The new navigation bar allows easier access to the API reference for each product. You can also browse the API reference within the feature guide as before.
  • Each page of the feature guides has a table of contents on the right side so that you can quickly move across sections.

# Conclusion

We will continue to make improvements to the LINE Developers site and our developer documentation to make it easier for you to develop apps using our products.

If you want to keep up-to-date with our latest developments, add the LINE Developers Official Account as a friend on LINE using the QR code or the button below.

QR code for the LINE Developers account

Add friend

Notice about service outage for the Messaging API (resolved)

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.

# Date of recovery

Date: June 27, 2018 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

When the Messaging API was called to unlink a rich menu from a user that was not in a chat with the bot, the rich menu was not unlinked from the user. This issue occured only to users with LINE 8.7.0 or later for iOS and rich menus configured at admin-official.line.me.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Login and the Social API (resolved)

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

Date: June 26, 2018

Time: 16:25–17:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

An error was returned when the following API features were accessed:

  • Get user profiles
  • Get friendship status
  • LINE Login

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Front-end Framework. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of recovery

Date: June 21, 2018 around 17:30 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

When a LIFF app was added to a channel, the permission to retrieve the user's email address was revoked if it had been granted to the channel. Please check if the email permission has been revoked or not from the LINE Developers console. Request the permission again if it has been revoked.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Flex Message released

We have released Flex Message, a new message type for the Messaging API. Flex Messages are messages with a customizable layout. You can customize the layout freely by combining multiple elements.

Flex Message samples

Flex Messages are only supported on LINE 6.7.0 and later for iOS and Android.

For more information, see Sending Flex Messages.

LINE Front-end Framework released

LINE Front-end Framework (LIFF) is a platform for web apps that run within LINE.

When launching a web app (LIFF app) registered in LIFF in LINE, the LIFF app can get data from the LINE Platform such as the LINE user ID. The LIFF app can use such data to provide features that utilize user information and send messages on behalf of the user.

For more information, see LINE Front-end Framework.

The maximum number of rich menus has been increased

Now you can set up to 1000 rich menus for one bot with the Messaging API. The previous maximum number was was 10.

For more information about rich menus, see Using rich menus.

LINE SDK for iOS 4.1.1 released

The LINE SDK for iOS version 4.1.1 has been released. You can download the SDK from the following page.

Changes:

  • Fixed an issue that the LineSDKLogin object has the access token in cache even after logout.

We will continue to provide improvements so that developers can code more easily.

Notice about service outage for LINE Developers site (resolved)

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

Date: April 11, 2018 Time: 12:00 ~ 22:00 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

During the date and time stated above, certain users could not access 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.

English documentation for the Account link feature released

The guide and API reference for the account link feature are now also available in English.

Check out the article at Linking user accounts and the Messaging API reference.

Account link feature released

You will now be able to securely link the user account for your existing service with the LINE account of the user if they have friended your bot. This will allow you to utilize the user information you already have and use LINE bots to provide even better services.

For more information, see Linking user accounts. We will let you know when English documents become available.

Notice about service outage for Messaging API (resolved)

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.

# Date and time of outage

Date: March 27, 2018 Time: 21:40 ~ 23:50 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

HTTP status code 500 was sometimes returned when the following API endpoints were accessed:

  • Get content API: https://api.line.me/v2/bot/message/{messageId}/content
  • Rich menu API: https://api.line.me/v2/bot/richmenu/*

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

Notice about service outage for LINE Developers site (resolved)

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

March 23, 2018 around 19:20 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

The icon image of a LINE@ account was not updated after setting or changing the icon image of the Messaging API (bot) channel that corresponds to the LINE@ account at the LINE Developers site.

This outage has now been resolved and the icon image of a LINE@ account can be configured by setting an icon image again on the "Channel settings" page.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

SSL root certificate authority for api.line.me will change

Please be advised that we will be updating the SSL certificate on the API server (api.line.me) for the LINE Platform on the following date and time. This update includes changing the root certification authority for the certificate from GeoTrust to Digicert.

# Planned date and time

Date: March 22, 2018 Time: 14:00-17:30 JST (GMT+9)

We appreciate your patience and apologize for any inconvenience this may cause.

LINE SDK for Android 4.0.8 released

The LINE SDK for Android version 4.0.8 has been released. You can download the SDK from the following page.

Changes:

  • Fixed an infinite loading indicator problem that occurs if the user attempts to log in before LINE has been opened for the first time.

We will continue to provide improvements so that you can code more easily.

LINE Bot Designer released

LINE Bot Designer lets you prototype LINE bots faster and easier without any programming knowledge. You can freely design chatbots in a desired scenario.

LINE Bot Designer free for use. Download it now. Anyone with a LINE account can use it.

For more information, see the LINE Bot Designer page.

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

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

LINE Login v1 to be discontinued

Note: This notice only applies to LINE Login v1 users. These changes do not apply if you are using the latest v2.1 or v2 endpoints.

Starting from March 31, 2018 we will start terminating LINE Login V1 endpoints. Please see the following schedule on the termination date for each endpoint. After an endpoint is terminated, any access to it will result in a 4XX status code as a response.

# Endpoints terminating on March 31, 2018
  • Issue access token: https://api.line.me/v1/oauth/accessToken
# Endpoints terminating on April 30, 2018
  • Get user profile: https://api.line.me/v1/profile
  • Logout: https://api.line.me/v1/oauth/logout
# Endpoints terminating on June 30, 2018
  • Verify access token: https://api.line.me/v1/oauth/verify
  • API endpoints for the LINE SDK for iOS and Android version 3.x or earlier

To avoid any issue related to the termination of LINE Login V1, please make sure to update your service to the latest LINE Login version. Please see the following page for more details on the latest LINE Login version.

Social API overview

Please also notice that the LINE user identifier is different between LINE Login V1 and LINE Login V2 or higher. If you are using the V1 user identifier on your service, you will need to convert the user identifier to use the latest LINE Login version. Please see the following page for more details on how to convert the LINE user identifier.

Converting an MID to a user ID

If you are a partner, we will contact you individually for more details.

New article on converting an MID to a user ID

Users are identified using a user ID in LINE Login v2 or later instead of an MID in v1. If you have integrated LINE Login v1 into your app and want to migrate it to v2 or later, you need to convert MIDs to user IDs.

For more information, see Converting an MID to a user ID.

Property for accessibility released

Now you can specify text to be spoken using the label property for imagemap messages and rich menus when the accessibility feature is enabled on the client device. This feature is supported on LINE 8.2.0 and later for iOS.

For more information, see the updated reference documentation below.

Introducing the Community site for developers

We are excited to introduce our new Community site added to the LINE Developers site.

Community site

You can find knowledge and examples from our developer community on the Community site, including expert tips from third-party developers and information about how to create attractive applications using the LINE APIs. Currently, the site has a Bot Directory, a showcase of chatbots available on LINE, and a Q&A section for development techniques.

Bot Directory and Q&A

New properties for template messages and postback actions released

# Default actions can now be set for template messages

The defaultAction property has been added to the column object for buttons and carousel template messages. As a result, you can indicate a single action to be executed when a user taps anywhere in the image, title, or text area.

For more information, see the updated reference documentation below.

# displayText property for postback actions released

We have released the displayText property and have deprecated the text property for postback actions. We recommend using displayText instead of the text property. Note that the dislayText and text properties cannot both be used at the same time.

For more information, see the Postback action reference documentation.

LINE SDK for Android 4.0.7 released

The LINE SDK for Android version 4.0.7 has been released. You can download the SDK from the following page.

Changes:

  • Fixed a crash that occurs if the user exits LINE using the home button and then opens the SDK app before LINE finishes the authentication process.

We will continue to provide improvements so that you can code more easily.

Let us announce the LINE API experts of the first quarter of 2018

LINE API Expert is a program that recognizes skilled engineers who have a deep understanding of the APIs provided by LINE and are influential in the community by giving them the title of "LINE API experts". In addition to providing an array of benefits, LINE will also support the various activities of these LINE API experts through this program.

The LINE API expert program was introduced at the LINE DEVELOPER DAY, September last year and a lot of engineers have applied through the LINE Developers site. Our internal review committee reviewed each item with a strict standard and came up with the final result. Please check the detail on the Expert List page or LINE Engineering Blog.

We look forward to see the selected members to actively engage in the developer community through meetups, online forum, SNS or blogs, and other means. LINE will be opened to the range of activities and will support their moves with all means.

For the Q1, a total of 22 qualified engineers have been selected from four Asia countries, including Japan.

Japan

Hirotada Kobayashi, Nobisuke Sugawara, Hiroyuki Hiki, Naohiro Fujie, Masao Wakasa

Taiwan

Caeser Chi, Cheng-Lung Sung, David Tung, Kuan-Hung Kuo, Richard Lee, Will Huang, Wolke Lin

Thailand

Annop Kobkij, Suphakit Annoppornchai, Teerachart Kortrakul, Winn Voravuthikunchai

Indonesia

David Su, Habibi Mustafa, M Gilang Januar, Michelle Neysa, Nur Rohman, Soesapto Joeni Hantoro

LINE SDK for iOS 4.1.0 released

The LINE SDK for iOS version 4.1.0 has been released. You can download the SDK from the following page.

Changes:

  • The web login process now uses a Safari View Controller instead of an external browser.

We will continue to provide improvements so that developers can code more easily.

Community SDK section released

We have released a community SDK section to our Messaging API SDKs page with Messaging API SDKs developed by our developer community. We currently have a C# (.NET) SDK and are looking to add more resources.

If you have developed a SDK or library for the Messaging API, see our Community contribution guidelines for information on how to submit your project to us for review.

Introducing our feedback form

In order to improve the quality of our documentation and products, we've added a feedback form to our documentation pages. If you would like to report any bugs in our documentation or would like to leave any suggestions, click the "Leave feedback" button on the bottom of our documentation pages and complete the form.

We greatly appreciate your feedback and we are committed to improving your experience using our developer products.

Feedback form

Notice about service outage for LINE Login and the Messaging API (resolved)

We'd like to inform you about a service outage regarding our Messaging API and LINE Login products. The issue has now been resolved but we sincerely apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: December 14, 2017
Time: 16:40–17:08 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Details

  1. Requests and responses (Messaging API and LINE Login) that contained user IDs either failed or returned incorrect user IDs.
  2. Webhooks for the Messaging API did not return correct user IDs.
  3. Push message requests with specified user IDs failed.

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

New article on sharing bots

We've added a new article on how you can gain more friends and expand the reach of your bot. For example, you can use a QR code, add an "Add friend" button, or link your bot with a LINE Login channel.

Check out the article at Sharing your bot with users.

Search feature released on website

We've added a new search feature to our site to make it easier for you to find the information you want. You can now search all of our content in the Products, Documentation, and FAQ sections of the site from the search bar found at the top of the side menu.

Search bar

LINE Login v1 to be discontinued

Note: This notice only applies to LINE Login v1 users. These changes do not apply if you are using the latest v2.1 or v2 endpoints.

We will be discontinuing the LINE Login v1 endpoints listed below on March 31, 2018. Once these endpoints are discontinued, a 4xx status code and error message will be returned.

  • Access token endpoint: https://api.line.me/v1/oauth/accessToken
  • Verify endpoint: https://api.line.me/v1/oauth/verify
  • Profile endpoint: https://api.line.me/v1/profile
  • Logout endpoint: https://api.line.me/v1/oauth/logout

Also note that versions 3.x.x and below of the LINE SDK for iOS and Android will no longer work after LINE Login v1 is discontinued.

If you are currently using LINE Login v1, we highly recommend updating your app to the latest version of LINE Login as soon as possible to avoid any issues when LINE Login v1 is discontinued. For information on the latest version of LINE Login, see the following pages.

New options for template message images

We have released imageAspectRatio, imageSize, and imageBackgroundColor fields for Buttons and Carousel template messages. Using these fields, you can configure the aspect ratio, size, and background color for images used in template messages. For more information, see the reference documentation below.

LINE URL scheme information released

We've added an article about the LINE URL scheme to our LINE Login and Messaging API documentation. You can use the URL schemes to help your users navigate to specific content such as the camera, location, or settings screens in LINE. The LINE URL scheme can be used in your bot (Messaging API) from within LINE or in your native or web apps to automatically open LINE.

See the new articles below.

Link your bot to your LINE Login channel

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 LINE Login. 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 Linking a bot with your LINE Login channel.

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 see the API reference for this resource, go to Get friendship status.

Note: This feature is not currently available to enterprise users. If you are an enterprise user and would like to use this feature, please contact your LINE representative.

LINE Login and Messaging API glossaries

To help you better understand the terms and concepts used in our documentation, we've added glossaries for both LINE Login and Messaging API.

Check them out using the links below.

Specification change for rich menu resources

We've made changes to the response of the rich menu resources of the Messaging API listed below. When sending a request to delete or upload a rich menu or to link or unlink a rich menu for a user, the LINE Platform will now return a 200 status code and an empty JSON object on success instead of returning only a 200 status code.

See the updated API reference documentation below.

LINE API Expert program released

We have released the new "LINE API Expert" program which was announced at LINE Developer Day 2017. This program recognizes skilled engineers, who have a deep understanding of the various APIs provided by LINE and are active in the community, by giving them the title of "LINE API expert." To apply for the program, visit the LINE API Expert page.

# The kind of "experts" we are looking for

We expect the following three things of the LINE API experts who represent this program.

  • A discerning eye and high overall technical abilities as an engineer
  • Deep understanding and development experience with developer APIs/SDKs provided by LINE
  • Active engagement in the developer community

# Incentives await

Everyone recognized as a LINE API expert is a valuable partner to LINE and we will provide various incentives to support the activities of our experts. Below are some examples.

  • We will provide LINE API experts with early-access to LINE developer products and will provide opportunities to give feedback directly to our LINE development teams and CTO.
  • We will provide venues for seminars and hackathons and dispatch evangelists and engineer support staff.

For more information about the incentives, see the LINE API Expert page.

# Accepting invitations now!

Although applications will be screened, there are no specific requirements necessary for applying. We are looking forward to your applications and to working together with engineers who are eager to be leaders in the LINE developer community and are striving to reach their next step as developers.

Column objects for template messages increased

We've increased the number of column objects that you can include in your carousel and image carousel template messages from 5 to 10 objects.

For more information, see the updated reference documentation below.

Rich menu features for Messaging API released

We've released rich menu features for the Messaging API which lets you display different rich menus to different users. By using the newly released rich menu endpoints, you can create, link, and manage your rich menus programmatically via the API instead of using LINE@ Manager. The rich menu endpoints provide greater freedom in designing rich menus and the ability to set postback actions to specified areas.

In addition to the current rich menu size of 2500x1686 on LINE@ Manager, you can now create smaller rich menus that are 2500x843 with the Messaging API. This smaller rich menu size lets you display more of the chat screen while still providing an interactive menu for the user.

Both rich menus created using LINE@ Manager and the Messaging API are supported and can be used at the same time.

Note: These rich menu features are only supported on LINE 7.14.0 and later for Android and iOS.

For more information on how to use the new rich menu features, see the following pages.

Notice about LINE Login service outage (resolved)

This is a notice to inform you about a recent service outage for LINE Login. The issue has now been resolved but we apologize for any inconvenience that this may have caused.

# Date and time

Date: October 16, 2017
Time: 16:30–17:36 JST (GMT+9)

# Cause

Issue with our servers.

# Situation

During the date and time stated above, certain channels may have received the following error when making an API call to retrieve an access token.

{"error":"invalid_grant","error_description":"authorization code expired or incompatible"}

We will continue to improve the quality of the services we provide to our developers and we greatly appreciate your understanding.

LINE SDK for Android 4.0.6 released

The LINE SDK for Android version 4.0.6 has been released. For more information on downloading the LINE SDK, see below.

Changes:

  • Fixed an infinite loading indicator problem that occurs when the user presses the back button while LINE's passcode prompt is on screen.

We will continue to provide improvements so that you can code more easily.

LINE Login v2.1 released

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

Here are some of the key changes.

# ID tokens

With LINE Login 2.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 have updated our authorization endpoints where you can use the new version 2.1 features. You can find more detailed information on the following pages.

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

Introducing the redesigned LINE Developers site

We are excited to introduce our new, redesigned LINE Developers site. We hope that this update will improve the experience for developers, making it easier to use our products (such as LINE Login and Messaging API) and to find the documentation that you need. Here, we'll take you through some of the key changes to the site.

READMORE

# LINE Developers console

Console top

The new and improved "LINE Developers console" makes it easier to create and manage your channels. You can login to the console to register a developer account, create a provider, and create channels for Messaging API and LINE Login.

If you have created channels on the LINE Business Center (discontinued on September 21, 2017), you'll be able to see and manage the channels from the LINE Developers console. Note that "Enterprises" on the LINE Business Center are called "Providers" on the LINE Developers console.

When creating a new Messaging API channel, you no longer need to go to the "Messaging API Settings" page of LINE@ Manager to enable API features and configure settings. Those settings are now available on the "Channel settings" page of the console. However, you will still need to use LINE@ Manager if you want to configure a rich menu and account page for your bot.

For information on how to create new channels for LINE Login and Messaging API, see the links below.

# Homepage and product overviews

We've overhauled our homepage and have made it easier to access the console, documentation, and news. We've also added product overview pages for LINE Login and Messaging API to the site.

# Documentation updates

We have updated our documentation structure, integrated our API reference docs into the site, and revised our existing documentation.

# Structure

Our documentation is now organized into the categories listed below, each with their own sidebars. You can also easily browse the documentation available from the Documentation overview page.

  • LINE Login
  • Messaging API
  • LINE SDK for iOS
  • LINE SDK for Android
  • Social API

In addition, you can find the links to the LINE Social Plugins and LINE Notify websites.

# Reference documentation

Our API and SDK reference documentation has been updated and integrated into the site. The existing reference documentation at https://devdocs.line.me will no longer be updated and discontinued in around one month. For the latest reference information, please use the new pages below.

# New and updated documentation

We have added various new articles for the Messaging API and have made updates to various other documents. Check out some of the new and updated articles below.

# Enterprise documentation

Our existing enterprise-facing content (Business Connect, mission stickers, link messages) has been separated from our public-facing content. If you are a partner and require access to the enterprise documentation, please contact your LINE representative for information.

# FAQ

We have a new frequently asked questions (FAQ) section where you can find answers to questions about LINE Login and Messaging API. Note that the questions from the line-bot-faq GitHub repository have been integrated into the FAQ section.

# Conclusion

We will continue to make improvements to the LINE Developers site and our developer documentation to make it easier for you to develop apps using our products.

If you want to keep up-to-date with our latest developments, add the LINE Developers Official Account as a friend on LINE using the QR code or the button below.

LINE Developers account QR code

Add friend

LINE Developers site redesign and maintenance

To improve the experience for developers and to make the process of creating channels for the Messaging API and LINE Login easier, we will be releasing a new redesigned site on September 21, 2017. Please note that the LINE Developers site will be unavailable at the following date and time.

Date: September 21, 2017

Time: 11:00–17:00 JST (GMT+9)

# Upcoming changes to the site

The following are some of the major changes that will be made to the site.

  • New look and feel of the website
  • More streamlined process for creating channels through the LINE Developers console. (The LINE Business Center will be discontinued.)
  • The current API reference (https://devdocs.line.me) page will be integrated into the LINE Developers site (https://developers.line.me)
  • Updates to our developer documentation

We will provide more details of the changes when the new version of the site is released.

New template message features released

We have released the following features for the Messaging API.

The image carousel template lets you send multiple images in a single message that users can cycle through like a carousel. You can then set template actions for when an image is tapped.

For more information, see the image carousel reference.

# Datetime picker action

With the datetime picker template action, you can provide an easy way for users to pick a date and time without having to type it in manually. The datetime picker action can be used in any type of template message and returns a postback event when the action is tapped.

Note: The datetime picker action is supported on LINE 7.9.0 and later for iOS and 7.12.0 and higher for Android.

For more information, see the datetime picker action reference.

Get user IDs and profiles of group and room members

We’ve released resources for the Messaging API which lets you get the user IDs and LINE user profiles of the members of a group or room that your bot is in.

For more information on how to use these resources, see the API reference items below.

LINE SDK for Android 4.0.5 released

The LINE SDK for Android version 4.0.5 has been released. For more information on downloading the LINE SDK, see below.

Changes:

  • Fixed an issue where a runtime error occurs upon calling startActivityForActivity with a login intent when using appcompat version 25.0.0 or higher.

We will continue to provide improvements so that you can code more easily.

Changes to the user consent process and data retrieved in webhooks

The user consent process and the data included in certain webhooks will change from LINE version 7.5.0 (iOS and Android). The details of the changes are shown below.

  1. Changes to the user consent process

    The way that users give consent to bots (LINE@ accounts and LINE Official Accounts) will change with the release of LINE version 7.5.0. Instead of requiring users to agree to a consent screen for every bot they want to add as a friend or start a chat with, from version 7.5.0, users will provide consent to all bots at once through a new consent screen (called the “Official Accounts Terms of Use”). After users have agreed to this screen once, they will be able to add other bots as friends and add them to chats in a single action.

    For more information on the user consent process, see User consent

  2. Changes to the Messaging API specifications

    Webhooks will include the user ID of users who send messages in a group or a room if the user has agreed to the “Official Accounts Terms of Use”. Note that the user ID will not be included in the webhook if the user is using a version of LINE below 7.5.0.

Messaging API SDK for Node.js released

We have released the Messaging API SDK for Node.js. This makes it easier for you to to build a bot on LINE with Node.js using the Messaging API.

See the Messaging API SDK repository below.

For more information on how to use the Messaging API SDK for Node.js, see the documentation.

LINE SDK for Android 4.0.4 released

The LINE SDK for Android version 4.0.4 has been released. For more information on download the LINE SDK, see below.

Changes:

  • Made a minor change to the SDK's authentication logic to fix a problem where onActivityResult does not get executed during app-to-app login.
  • Fixed a known issue in 4.0.2 where onActivityResult returns a result of "CANCEL" on the first time that a user logs into an application using app-to-app login.

We will continue to provide improvements so that you can code more easily.

Changes to the LINE Login review criteria

The LINE Login review criteria has been modified. Up until now, a review was required to change the status of LINE Login channels from "developing" to "published". However, from now on, LINE Login channels created on the LINE Business Center will automatically have the "published" status.

For existing LINE Login channels, you will be able to change the status to "published" from the Channel Console without a review.

Note that the LINE Login review criteria may change at a later date upon the release of new APIs or features. You should also make sure that your app complies with the LINE Login Button Usage Guidelines and LINE Developers Agreement.

LINE SDK for Android 4.0.2 released

The LINE SDK for Android version 4.0.2 has been released. You can download the SDK from the following page.

Changes:

  • Fixed an issue where browser login fails with an INTERNAL_ERROR on Android 4.x devices.

Known issues:

  • On Android 4.x devices, onActivityResult returns a result of "CANCEL" the first time that a user logs into an application using the app-to-app login. However, the user will be able to successfully log in from their second attempt. This issue is caused by a problem in LINE and will be resolved in a future update.

We will continue to provide improvements so that you can code more easily.

LINE SDK for iOS CocoaPod released

We have released the LINE SDK for iOS on CocoaPods. You can now download the LINE SDK for iOS using CocoaPods for your Objective-C and Swift projects.

For information on how to download the SDK with CocoaPods, see the link below.

We will continue to provide improvements so that developers can code more easily.

LINE Developers site temporarily unavailable on February 7

The LINE Developers site (https://developers.line.me) will be unavailable at the following date and time.

[Date]
February 7
15:00-16:00 JST (GMT+9)

[Impact]
You won’t be able to access https://developers.line.me

LINE SDK for iOS 4.0.1 released

The LINE SDK for iOS version 4.0.1 has been released. You can download the SDK from the following page.

Changes:

  • Fixed an issue which causes an authentication error when using Web Login.

We will continue to provide improvements so that developers can code more easily.

New versions of Web Login and the LINE SDK released

New versions of Web Login, LINE SDK for Android, and LINE SDK for iOS have been released. Details of each release are outlined below.

# Web Login v2

Key changes:

  • Endpoint URLs contain "v2" instead of "v1"
  • userId is returned in get user profile requests. mid is no longer returned in the response.
  • scope is returned with the default value of p for permission to get user profile information
  • error and state parameters are returned in error responses for authorization

For more information, see the updated documentation below.

You can also use the LINE Login starter application to help you get started with Web Login.

Note: Web Login v1 will be discontinued in January 2018. If you are using Web Login v1, please migrate to the Web Login v2 before that time.

# LINE SDK for Android 4.0.0

Key changes:

  • Implements the Auto Login feature using Chrome custom tabs, instead of app-to-app authorization
  • Automatically gets user profile information at login
  • Has a method to verify the access token
  • Has a method to refresh the access token
  • Has a method to log the user out

For more detailed information on how to use the LINE SDK for Android, see the updated documentation below.

Download the LINE SDK for Android

# LINE SDK for iOS 4.0.0

Key changes:

  • Automatically gets user profile information at login
  • Has a method to verify the access token
  • Has a method to refresh the access token
  • Has a method to log the user out

For more detailed information on how to use the LINE SDK for iOS, see the updated documentation below.

Download the LINE SDK for iOS

Note: The reference documentation for the LINE SDK for Android and iOS are currently only available in English.

We will continue to provide improvements so that developers can code more easily.

Multicast feature released

We've released the multicast feature which lets you send messages to multiple users at any time.

See the updated documentation in the API reference below.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS 3.2.2 released

The LINE SDK for iOS has been updated to version 3.2.2. You can download it from the LINE SDK archives on the following page:

Download LINE SDK

Changes:

  • Fixed an issue with bitcode.

We will continue to provide improvements so that developers can code more easily.

Specification change to API postponed

The date of the specification change to LINE Login (as stated in the November 22 post) will be postponed from December 15 to December 19. The details of the specification change as specified in the earlier post are shown below.

November 22 post:

Based on the OAuth 2.0 specification, we will add parameters [error, state] to the error response of LINE Login authentication.

These parameters will be added to the error response sent to the callback URL when the user selects cancel on the agreement screen which is displayed during the LINE Login process.

In addition, in accordance with the OAuth 2.0 specification, the errorCode and errorMessage parameters in the current error response will be deprecated and removed in the future.

Change to requirement on whitelisting LINE domains

Whitelisting LINE domains is no longer a requirement for using the LINE SDK for iOS. As such, the documentation on whitelisting LINE domains found in the "Settings for iOS 9 or later" section has been removed.

Important: Specification change to API

Based on the OAuth 2.0 specification, we will add parameters [error, state] to the error response of LINE Login authentication.

These parameters will be added to the error response sent to the callback URL when the user selects cancel on the agreement screen which is displayed during the LINE Login process.

In addition, in accordance with the OAuth 2.0 specification, the errorCode and errorMessage parameters in the current error response will be deprecated and removed in the future.

[Date]

December 15, 2016

LINE SDK for Android 3.1.21 released

The LINE SDK for Android has been updated to version 3.1.21. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Updated to prevent build warnings.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for Android 3.1.20 released

The LINE SDK for Android has been updated to version 3.1.20. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Updated build with Java 1.7 for compatibility.

We will continue to provide improvements so that developers can code more easily.

The LINE SDK for iOS 3.2.1 released and the LINE starter application revised

The LINE SDK for iOS has been updated to version 3.2.1. You can download it from the LINE SDK archives on the following page:

Download LINE SDK

Changes

  • LineAdapter+Login.framework and LineAdapterUI.framework merged to LineAdapter.framework.
  • Definition changed for swift.

In addition, the LINE starter application has been revised to make compatibility with this version of SDK. You can clone or download it from the below GitHub repository.

https://github.com/line/line-sdk-starter-ios

We will continue to provide improvements so that developers can code more easily.

Messaging API released and LINE Developers documentation updated

We've made some updates to the LINE Developers website. We've added new documentation together with the release of the Messaging API. Our API reference documentation has also been updated and redesigned. And we've made a couple of branding changes as well.

For more detailed information about the changes, see below:

  • Added "Overview", "Getting started", and API reference documentation for the Messaging API. For more information, see Messaging API.
  • Changed the look of the API reference documentation. See the new documentation here: API reference.
  • Made the following branding changes:
    • Web API includes the APIs used for integrating Web Login with your websites.
    • Social REST API includes REST APIs that you can call from your applications.
    • LINE Login, LINE SDK for Android, LINE SDK for iOS, Web API, and Social REST API are included in Social API
  • Added information on LINE Official Accounts and LINE@ accounts in "Account types".

Sending rich messages section updated

The "Sending rich messages" section of the LINE Developers site has been updated to include information about the "sendMessage" feature of rich messages.

For more information, go to https://developers.line.me/bot-api/api-reference.

LINE Developers site temporarily unavailable on June 23

The LINE Developers site (https://developers.line.me) will be unavailable at the following date and time.

[Date] June 23 20:00-21:00 JST (GMT+9)

[Impact] You won’t be able to access https://developers.line.me

Useful links have been added for BOT API Trial

We have added useful links to accelerate your development on BOT API Trial.

See all the links added from below.

Messaging API links

Channel Console unavailable temporarily on June 16

The LINE Developer Channel Console will be unavailable at the following date and time.

[Date]

June 16 01:00 ~ 05:30 JST (GMT+9)

[Impact]

You won't be able to modify your Channel at the time specified above.

List of stickers updated

Sticker images have been added to the sticker list which will allow developers to easily recognize the sticker ID.

Method for calling APIs for BOT API Trial changed

You are no longer required to register the IP address of your server to call APIs for BOT API Trial. If you register an IP address on the whitelist, API calls will be limited to that IP address. You can use the whitelist for security purposes.

Method for calling APIs for BOT API Trial changed

We are pleased to announce the launch of the LINE Developers Official Account.

The LINE Developers Official Account provides you with the latest updates on the LINE platform. By adding the Official Account to your friend list, you'll receive information on documentation updates, SDK releases, specification changes and more.

To add the LINE Developers Official Account to your friend list, scan the QR code below or if you are using a smartphone, tap the “Add Friends” button below.

Friends Added

QR code

We will continue to provide improvements so that developers can code more easily.

Let's Encrypt and StartSSL CA has been added

SSL CA root certificates for Let's Encrypt and StartSSL have been added for BOT API callback URL.

See the "Note" in the Registering a callback URL section to find a link to the full list of authorized CAs.

Changes to the LINE Developers site

To our valued partner developers, we have updated the LINE Developers site due to the release of the Business Center and BOT API.

Changes:

  • Arranged sections based on features or APIs
  • Sections now only contain APIs that are related to that particular section
  • Top page has been updated
  • BOT API section has been added
  • Javascript SDK section is now called Channel Web Applications
  • Other minor fixes

LINE SDK for Android version 3.1.19 released

The LINE SDK for Android has been updated to version 3.1.19. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Fixed login error issue when user attempts to login again

We will continue to provide improvements so that developers can code more easily.

LINE SDK for Android version 3.1.18 released

The LINE SDK for Android has been updated to version 3.1.18. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Added support for 64-bit architecture
  • Added the locale property to the login method
  • Fixed some bugs

We will continue to provide improvements so that developers can code more easily.

Important: Changes to the character limit for Channel names

To our valued partner developers,

We are planning to integrate our systems on March 23. As a result of the integration, Channel names that have more than 20 characters will be automatically truncated to 20 characters. If you have a Channel that has more than 20 characters in its name, we recommend that you change the name to something with 20 or fewer characters by March 22.

Thank you for your understanding and your continued cooperation.

LINE Developers

FAQ page published

We published a FAQ page today. This page lists frequently asked questions about the LINE platform.

Frequently Asked Questions

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.17 released

The LINE SDK for iOS has been updated to version 3.1.17. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Fixed an issue where return error message is not correct when a token refresh request fails.
  • Fixed an issue with iOS 9 where authorization process is not canceled when the cancel button is tapped.

We will continue to provide improvements so that developers can code more easily.

Using the LINE it! Button on Websites page published

We published the “Using the LINE it! Button on Websites” page today. This page explains how to add the LINE it! Button to websites. The LINE it! Button lets users share websites with their friends on LINE.

Using the LINE it! Button on Websites

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.15 released

The LINE SDK for iOS has been updated to version 3.1.15. You can download it from the LINE SDK archives on the following page:
Changes:
  • Fixed app-to-app authentication error on iOS9.
We will continue to provide improvements so that developers can code more easily.

Channel console access unavailable Oct 27

Outage Report:

Channel console access was unavailable on the following time due to server side issue.

October, 27 11:30 - 12:30 JST

We are sorry for any inconvenience caused by this outage.

LINE SDK for iOS version 3.1.14 released

The LINE SDK for iOS has been updated to version 3.1.14. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Fixed error when building for submission on Xcode 7.

We will continue to provide improvements so that developers can code more easily.

Settings for iOS 9 or later

For developers developing applications with the iOS 9 SDK, please use the following settings to ensure that your application works with iOS 9.

iOS - Settings for iOS 9 or later

We will continue to provide improvements so that developers can code more easily.

Specification change to API completed

The specifications of the following API has been changed as shown below as announced on August 31.

[API]
https://api.line.me/v1/oauth/accessToken

[Changes]

The expires_in value will be displayed in seconds instead of milliseconds.

It will be possible to refresh tokens before they expire. Currently, an error will occur when you refresh a token before it has expired.


[Reason]

To comply with OAuth2 specifications.


[Date and Time]
16:00 on September 14, 2015 (Finished)

LINE SDK for iOS version 3.1.13 released

The LINE SDK for iOS has been updated to version 3.1.13. You can download it from the LINE SDK archives on the following page:
Changes:
  • The "refreshWithResultBlock" method returns an error if the access token cannot be refreshed.
  • Minor bug fixes.
We will continue to provide improvements so that developers can code more easily.

Important: Specification change to API

We will be making changes to the specifications of an API on the LINE Login Platform.

[API]
https://api.line.me/v1/oauth/accessToken

[Changes]

The expires_in value will be displayed in seconds instead of milliseconds.

It will be possible to refresh tokens before they expire. Currently, an error will occur when you refresh a token before it has expired.


[Reason]

To comply with OAuth2 specifications.


[Date and Time]
16:00 on September 14, 2015

Description of the expires_in property modified

The description of the expires_in property has been modified. This change can be found in the Integrating Web Login page under the Retrieving Access Tokens section. The previous description for the expires_in property was incorrectly described as the elapsed time from epoch time. It has been corrected to describe the property as the elapsed time from when the response is generated.

This is only a modification of the documentation. The API has not been modified.

LINE Starter Application for iOS and Android released

The LINE Starter Application for iOS and Android has been released. The LINE Starter Application provides examples to help you get started on integrating the LINE SDK into your application.

The sources can be found on the following links.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.12 released

The LINE SDK for iOS has been updated to version 3.1.12. You can download it from the LINE SDK archives on the following page:
Changes:
  • Added new endpoints for the LINE Platform.
  • Added “clearLocalLoginInfo" method to remove login information from local cache.
  • Added function allowing users to switch accounts from the WebView login.
  • Added the capability to retrieve SDK version on the LineAdaptor.
We will continue to provide improvements so that developers can code more easily.

New feature which issues access tokens for testing released

We have introduced a new feature which lets you easily retrieve access tokens and call APIs to test your application.

Click the Issue button and log in to retrieve an access token with the PROFILE permission.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for Android version 3.1.16 released

The LINE SDK for Android has been updated to version 3.1.16. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • In this latest version of the LINE SDK for Android, you can create a sub class of WebLoginActivity to override the onResume method from this version. When doing this, you need to register the sub class with "jp.line.sdk.WebLoginActivityClass" metadata on the AndroidManifest.xml file.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.10 released

The LINE SDK for iOS has been updated to version 3.1.10. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Modified to specify "kSecAttrAccessible: kSecAttrAccessibleAfterFirstUnlock" when storing to KeyChain.
  • Added the expiresDate property to the LineApiClient.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for iOS version 3.1.9 released

The LINE SDK for iOS has been updated to version 3.1.9. You can download it from the LINE SDK archives on the following page:

Resources - Download LINE SDK

Changes:

  • Can no longer be used with iOS 4.9 and lower.
  • Removed the JSONKit dependency; NSJSONSerialization will be used instead.
  • Fixed the bug where the SDK crashes when the refresh token is null.

We received a lot of feedback about the SDK crashing when using JSONKit in a 64-bit environment so we decided to remove the JSONKit dependency.

We will continue to provide improvements so that developers can code more easily.

LINE SDK for Android version 3.1.13 released

The LINE SDK for Android has been updated to version 3.1.13. You can download it from the following page:

Resources - Download LINE SDK

In this version, not only does the LINE SDK support .so files for ARM architecture, it also supports other architectures. It includes some bug fixes as well.

We will continue to provide improvements so that developers can code more easily.

LINE Developers Site Update

We are happy to announce a design update to the LINE Developers site.

This update contains improvements to the look and feel of the site. We have made changes to the layout and have added a new search feature where you can search for information using keywords. Other than the overall layout, there have been no changes made to the Channel Management page.

We will continue to provide improvements so that developers can code more easily.