# News

Introducing the LINE Developers Console feedback form

In order to improve the quality of the LINE Developers Console for our users, we've added a feedback form to the LINE Developers Console.

If you would like to report any bugs in the LINE Developers Console or would like to leave any suggestions, scroll down to the bottom of the page and click the feedback form icon.

LINE Developers Console feedback form icon

After clicking the icon, the feedback form will appear. You can then leave any feedback you may have for us.

LINE Develoeprs Console feedback form

We read every single feedback message, but we can't respond to questions asked through the feedback form. To get technical support, use the inquiry form (opens new window).

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

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

We'd like to inform you about a service outage regarding LINE Login and 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 outage

October 17, 2020 11:17 - 11:22 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Impact

  • LINE Login
  • LINE Front-end Framework (LIFF)
  • Social API (v2.0, v2.1)

# Details

The API returned status code 5xx 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 LINE Login and LINE Front-end Framework (resolved)

We'd like to inform you about a service outage regarding LINE Login and 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 outage

Date: October 15, 2020
Time: Around 18:34–18:42 JST (GMT+9)

# Cause of the outage

Issue with our servers.

# Impact

  • LINE Login
  • LINE Front-end Framework
  • Social API (v2.0, v2.1)

# Details

The API returned status code 5xx for some requests.

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

You can now log in to the LINE Developers Console using business accounts

You can now log in to the LINE Developers Console using business accounts.

Method of logging in to the LINE Developers Console Before update After update
LINE account
Business account

You do not need to link your business account with your LINE account in order to log in to the LINE Developers Console with your business account. However, if it is not linked, there are some restrictions on the functions that can be used.

For more information on business accounts, see LINE Business ID login options (opens new window) in the Help center.

For more information on the LINE Developers Console, see the Overview in the LINE Developers Console documentation.

We will continue to work on improving the quality of the LINE Developers Console. We look forward to your continued support.

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

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

The initial plan was to complete the transition by April 30, 2020, but was extended to October 30, 2020 based on the usage situation.

# 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 cause. Thank you for your understanding.

# Transition period

November 8, 2019 - October 30, 2020 14:00

[Updated] Flex Message Update 2 released

Added October 22, 2020

Flex message's play animated images feature has been temporarily disabled due to a technical issue. As of current, regardless of the value of the animated property in the image component, animated images cannot be played.

We sincerely apologize for any inconvenience this may have caused. We will notify you through this news article once the issue is fixed and the feature has been enabled again.

Flex Message Update 2 has been released for the Messaging API.

Flex Message Update 2 includes these improvements:

# Changed the maximum number of bubbles that can be included in a carousel

We changed the maximum number of bubbles that can be included as child elements of a carousel container. This table provides a side-by-side comparison of values before and after the change.

# Added more component alignment options

We added the justifyContent and alignItems properties to Flex Message box components. These properties let you specify how child elements and free space should be arranged; for example, you can choose to evenly distribute the child elements or keep them all centered.

flex-start flex-center flex-end space-between space-around space-evenly

For more information, see Arranging a box's child elements and free space in the Messaging API documentation.

# Allowed gradients to be used as a box's background image

You can use a linear gradient as the background image for a box component by setting its background.type property equal to linearGradient.

Linear gradient at 0 degrees Linear gradient at 45 degrees Linear gradient at 90 degrees

For more information, see Linear gradient backgrounds in the Messaging API documentation.

# Allowed an empty array to be specified as the value of a box's contents property

You can now specify an empty array as the value of a box component's contents property.

  • Box component

    Item Before After
    contents property Empty arrays can't be specified Empty arrays can be specified
    When would it be helpful to specify an empty array?

    When using box components for decoration like the four squares shown below, it used to be necessary to add filler components as child elements to each of the boxes. Starting with Flex Message Update 2, you only need to specify an empty array.

    offset property example 1

    Let's compare the JSON data for the yellow box component on the left before and after this change:

    • Before
    {
        "type": "box",
        "layout": "vertical",
        "contents": [
            {
            "type": "filler"
            }
        ],
        "width": "30px",
        "height": "30px",
        "backgroundColor": "#FFFF7F"
    }
    
    • After
    {
        "type": "box",
        "layout": "vertical",
        "contents": [],
        "width": "30px",
        "height": "30px",
        "backgroundColor": "#FFFF7F"
    }
    

# Added support for animated images

Added October 22, 2020

Flex Message's play animated images feature has been temporarily disabled due to a technical issue. As of current, regardless of the value of the animated property in the image component, animated images cannot be played.

We sincerely apologize for any inconvenience this may have caused. We will notify you through this news article once the issue is fixed and the feature has been enabled again.

It is now possible to specify animated images (APNG) in the image component of Flex Message.

For more information, see the Image component in the Messaging API Reference.

# Changed how sizes are specified

We changed how you specify a component's size. This table provides a side-by-side comparison of values before and after the change.

# Allowed text to automatically shrink to fit a component's width

We added the adjustMode property to text and button components. If you specify a value of shrink-to-fit for this adjustMode property, the text's font size will automatically shrink to fit the width of the component.

Automatically shrink fonts to fit

For more information, see the Text and Button components in the Messaging API reference.

# Spacer has been discontinued

The spacer component, which was previously deprecated, has been discontinued. We recommend setting the padding of the box without using a spacer from now on.

For more information, see Box padding in the Messaging API documentation.

# Added support for Update 2 in the Flex Message Simulator

Flex Message Simulator now supports the new properties and objects introduced in Flex Message Update 2, as well.

Using Flex Message Simulator, you can easily generate JSON data for Flex Messages and visually examine how they're laid out.

Caveats

Flex Message Simulator doesn't make any guarantees about the layout of a Flex Message. A Flex Message's appearance may vary from one device to the next. In addition to the version of the LINE app being used, a device's operating system, resolution, language settings, and fonts may affect how messages are rendered.

TLS 1.0 and TLS 1.1 support by the webhook notification source will be discontinued at the end of January 2021

The following updates are planned for the LINE Platform, the source of webhook notifications for the Messaging API.

If you are using a webhook, please confirm communication from the new environment during the transition period.

What is a webhook?

A webhook is one of the features of LINE's Messaging API. It's a system in which the LINE Platform notifies the bot server of the provider (corporate or developer) of events such as adding friends and sending messages via HTTPS POST requests.

You can specify the bot server to which you want to be notified of webhooks by specifying the webhook URL in the LINE Developers Console. For more information on webhooks, see Receiving messages (webhooks) in the Messaging API documentation.

# Supported SSL/TLS protocol versions

We no longer support TLS 1.0 and TLS 1.1.

See the table below for the differences before and after the transition.

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

# Supported HTTP versions

See the table below for differences before and after the transition.

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

# Supported root certification authorities

Webhook URLs (the bot server to which webhooks are notified) must be configured with an SSL/TLS certificate issued by a trusted certification authority. Self-signed certificates aren't allowed.

See the table below for differences before and after the transition.

Before transition After transition
Available SSL/TLS Certificates An SSL/TLS certificate issued by a "Certificate authority trusted by LINE" SSL/TLS certificates issued by a root certification authority that's widely trusted by most browsers

The "Certificate authority trusted by LINE" list will be removed at the end of the transition period.

# Transition period

October 6, 2020 - January 31, 2021 JST (GMT+9)

# Impact

If you're using Messaging API webhooks, we recommend that you use one of the following methods during the migration period to verify that the new LINE Platform can be used to communicate with the bot server.

# Verification method 1: Verify with an endpoint for webhook URL validation

Please verify the connection by using the endpoint for webhook URL test.

Return status code 200 for the communication request
  • The LINE Platform sends an HTTP POST request that doesn't include a webhook event to the webhook URL (bot server) to confirm communication. Design your bot server to return status code 200.

    Example HTTP POST request without a webhook event:

    {
        "destination": "xxxxxxxxxx",
        "events": []
    }
    

# Verification method 2: Use the webhook URL's "Verify" button in the LINE Developers Console

In the LINE Developers Console, click the Webhook URL's "Verify" button to perform the verification.

send target

The webhook URL's "Verify" button will be available soon

The Webhook URL's "Verify" button will soon be able to confirm communication from the environment after migration.

We will inform you when it becomes available.

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

Messaging API update for October 2020

We added new endpoints to the Messaging API.

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

# Get bot info

Gets basic information about the bot, such as:

  • Bot's user ID
  • Bot's basic ID
  • Bot's premium ID
  • Bot's display name
  • Profile image URL
  • Bot response mode ("Chat" or "Bot")
  • If the bot is set to automatically read messages

For more information, see Get bot info in the Messaging API reference.

# Get webhook endpoint information

Gets this information about the webhook endpoint:

  • Webhook URL
  • Webhook usage status (enabled or disabled)

For more information, see Get webhook endpoint information in the Messaging API reference.

# Set webhook endpoint URL

Sets the webhook endpoint URL. It may take up to 1 minute for changes to take place due to caching.

For more information, see Set webhook endpoint URL in the Messaging API reference.

# Test webhook endpoint

Checks if the configured webhook endpoint can receive a test webhook event.

For more information, see Test webhook endpoint in the Messaging API reference.

LIFF v2.3.3 released

We've released LIFF v2.3.3.
This bug has been fixed in LIFF v2.3.3:

There are no feature updates in this release.

# Fixed a bug that redirects users to unintended URLs when the endpoint URL ends with /

Under these conditions, accessing a LIFF URL causes a redirect to an unintended URL with a double path separator (//).

  • The URL specified in Endpoint URL contains a path and ends in /. Example: https://example.com/campaign/
  • Methods for converting additional information in the LIFF URL is set to Concatenate.
  • The LIFF URL contains a path (/path). Example: https://liff.line.me/{liffId}/path

In LIFF v2.3.3, the bug has been fixed so that the user is redirected to the correct URL even under the above conditions.

Item LIFF URL Primary redirect URL Secondary redirect URL
Before spec change https://liff.line.me/{liffId}/path https://example.com/campaign/?liff.state={urlEncode(/path)} https://example.com/campaign//path
After spec change https://liff.line.me/{liffId}/path https://example.com/campaign?liff.state={urlEncode(path)} https://example.com/campaign/path
Impact on other versions
  • If you are using LIFF v2.3.x, we recommend that you update to this patch version.
  • This bug has already been fixed in LIFF v2.4.1.

For more information on what happens when accessing LIFF URLs, see Operation from accessing LIFF URL to opening LIFF App in the LIFF documentation.

LIFF v2.4.1 released

We have released LIFF v2.4.1.
The changes in LIFF v2.4.1 are as follows:

# Fixed an issue with the feature to open another LIFF app without closing a LIFF app

We've found that the feature to open another LIFF app without closing the LIFF app, which we announced on August 31, 2020, has a bug and didn't work correctly even if the operating conditions were met.

In LIFF v2.4.1, the operating conditions have been changed as follows and the bug has been fixed.

Items Before the changes After the changes
LIFF SDK 2.4.0 2.4.1
LINE 10.16.0 10.18.0
The use of LIFF v2.4.0 is no longer recommended

Due to the above bug, the use of LIFF v2.4.0 is no longer recommended. If you are using LIFF v2.4.0, we recommend that you update to v2.4.1.

For more information, see Opening a LIFF app from another LIFF app in the LIFF document.

# Added a feature to liff.isApiAvailable() to check whether the transition between LIFF apps is possible

liff.isApiAvailable(), a method which checks if an API is available, can now be used to check if transitioning between LIFF apps is possible.

You can now execute liff.isApiAvailable('multipleLiffTransition') to confirm whether transitioning between LIFF apps is possible before opening another LIFF app. By using this feature, you can prevent an error when opening another app.

if (liff.isApiAvailable('multipleLiffTransition')) {
  window.location.href = "https://line.me/{liffId}", // URL for another LIFF app
}
Get information about transitioning between LIFF apps with liff.getContext()

You can now also use liff.getContext(), a method which obtains information about a LIFF app, to obtain information such as whether transitioning between LIFF app is possible, and the executable LINE version.

  • availability.multipleLiffTransition.permission: Indicates whether transitioning between LIFF apps is possible.
  • availability.multipleLiffTransition.minVer: Indicates the minimum LINE version that supports the transition between LIFF apps.

Below is an example of the return value of liff.getContext().

{
    "type": "utou",
    "utouId": "UU29e6eb36812f484fd275d41b5af4e760926c516d8c9faa35…b1e8de8fbb6ecb263ee8724e48118565e3368d39778fe648d",
    "userId": "U70e153189a29f1188b045366285346bc",
    "viewType": "full",
    "accessTokenHash": "ArIXhlwQMAZyW7SDHm7L2g",
    "availability": {
        "shareTargetPicker": {
            "permission": true,
            "minVer": "10.3.0"
        },
        "multipleLiffTransition": {
            "permission": true,
            "minVer": "10.18.0"
        }
    }
}

For more information, see liff.isApiAvailable() or liff.getContext() in the LIFF API reference.

# Fixed behavior of liff.init() being called twice

If you execute liff.init() more than once under the condition that the LIFF App is successfully initialized, a rejected Promise object was returned with an error message.

In LIFF v2.4.1, the error has been fixed so that if you execute liff.init() more than once under the condition that liff.init() succeeds, a resolved Promise object will be returned, and a warning message will be displayed.

For more information on initializing your LIFF App, see the LIFF document Initializing LIFF App.

Notice about service outage for LINE Login (resolved)

We'd like to inform you about a service outage regarding the LINE Login. We've released a version of LINE that resolved the issue.

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

# Date and time of outage

August 20, 2020 - September, 21, 2020 JST (GMT+9)

# Cause

Issue with LINE for iOS and iPadOS.

# Details

When LINE Login was integrated into an iOS app with LINE SDK for iOS, some LINE Login processes didn't work properly.

Normally, in iOS apps with the LINE Login feature, these processes launch LINE.

  1. A user presses the LINE Login button on the iOS app.
  2. LINE is launched with a universal link.
  3. If step 2 fails, LINE is launched with a custom URL scheme.

Although LINE supports universal links, LINE may not be able to be launched with some universal links on certain devices or operating systems.

If you proceeded to step 3 in the above situation, LINE Login didn't work properly on some versions of LINE, and an alert saying Unable to connect. Update to the latest version of LINE or recheck the URL. was displayed on LINE.

# Affected services

If all of these conditions are met, the LINE Login process didn't work properly and an error message was displayed.

  • A user uses LINE for iOS or iPadOS.
  • A user uses LINE version 10.14.0 or 10.14.1.
  • LINE isn't launched with a universal link on a user's environment.
  • LINE Login was integrated into an iOS app with the LINE SDK for iOS Swift or LINE SDK for iOS Objective-C 5.0.0 or later.

If all of the above conditions are met, updating user's LINE version to 10.15.0 or later will resolve the issue.

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

Redelivery object has been added to the criteria for narrowing down the narrowcast message target

Redelivery object has been added to the criteria for narrowing down the narrowcast message target in the Messaging API. Using the redelivery object, you can send a message conditioned on users who have previously received a narrowcast message.

# Redelivery object was added

Narrowcast messages are usually sent to all users who added a specific LINE Official Account as a friend. However, by specifying the demographic filter object when you send a narrowcast message, you can narrow down the target of your message based on certain conditions.

narrowcast message

To narrow down the target by a recipient object, in addition to the existing audience object, you can now specify the redelivery object.

By specifying the request ID in the redelivery object, you can send a message to users who have previously received a narrowcast message.

Conditions for specifying the request ID

The request ID specified in the requestId property must satisfy all of these conditions:

  • The request ID was issued by the delivering a narrowcast message
  • The narrowcast message was delivered within the past seven days
  • The delivery process is completed (The value of the phase property is succeeded in the response of the Get narrowcast message status endpoint)

For more information on redelivery object, see:

# Specify the target using the operator object (AND, OR, NOT)

Similar to existing audience objects, you can specify the target based on complex conditions using operators (AND, OR, NOT) with the redelivery object.

Below is an example of a recipient object with users with a specific chat tag and (AND) users who received a narrowcast message previously delivered set as the target:

send target

"recipient": {
    "type": "operator",
    "and": [
        {
            "type": "audience",
            "audienceGroupId": 5614991017776
        },
        {
            "type": "redelivery",
            "requestId": "5b59509c-c57b-11e9-aa8c-2a2ae2dbcce4"
        }
    ]
}

For more information about narrowing down the narrowcast message target, see these:

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. We apologize for any inconvenience that this may have caused.

# Date and time of outage

Date: September 15, 2020 Time: 11:37-11:53 (GMT+9)

# Cause

Issue with our servers

# Details

The Messaging API call returned a status code 403 even if the request was correct.

# Affected services

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

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

LIFF v2.1.14, v2.2.1, v2.3.2 released

LIFF v2.1.14, v2.2.1, v2.3.2 were released. The changes are as follows:

# Fixed error in which the URL fragment entered in the LIFF endpoint URL was not correctly handled by liff.permanentLink.createUrl()


Affected version

  • LIFF v2.3.2

Changes

When the LIFF endpoint URL contained a URL fragment (#URL-fragment), despite the Methods for converting additional information in the LIFF URL being set to Replace (Backward compatibility mode), the URL fragment was included in the permanent link returned after executing liff.permanentLink.createUrl().

Conditions under which this problem occurs
  • A URL fragment is included in the LIFF endpoint URL
  • Methods for converting additional information in the LIFF URL is set to Replace (Backward compatibility mode)

For example, when the Endpoint URL is set to https://example.com/path#section and liff.permanentLink.createUrl() is executed, https://liff.line.me/{liffId}/path?liff.state=#section would be returned as the permanent link. In LIFF v.2.3.2, the bug is fixed so that https://liff.line.me/{liffId} would be correctly returned.

# Fixed error in which the query parameter entered in the LIFF endpoint URL was not correctly handled by liff.permanentLink.createUrl()


Affected version

  • LIFF v2.3.2

Changes

When the LIFF endpoint URL contained a query parameter (?key=value), the query parameter would infinitely multiply in the permanent link returned after executing liff.permanentLink.createUrl().

Conditions under which this problem occurs
  • The query parameter in the LIFF endpoint URL matches the query parameter in the LIFF URL when executing liff.permanentLink.createUrl().
  • Methods for converting additional information in the LIFF URL is set to Concatenate

For example, when the Endpoint URL is set to https://example.com/path1/?q1=v1&q2=v2 and liff.permanentLink.createUrl() is executed in https://liff.line.me/{liffid}/?q1=v1&q2=v2, a permanent link with the query parameter infinitely multiplied such as https://liff.line.me/{liffid}/?q1=v1&q1=v1&q2=v2&q2=v2 would be returned.

In LIFF v.2.3.2, the bug is fixed so that https://liff.line.me/{liffid}/?q1=v1&q2=v2 would be correctly returned.

# Fixed error in which the path entered in the LIFF Endpoint URL was not correctly handled by liff.permanentLink.createUrl()


Affected versions

  • LIFF v2.3.2

Changes

When path is included in the LIFF endpoint URL and a slash (/) is used at the end of the path, the permanent link obtained by executing liff.permanentLink.createUrl() would redirect you to URL without the ending slash as shown below.

Conditions under which this problem occurs
  • Path (/path/) is included in the LIFF endpoint URL, and a slash (/) is used at the end of the path
  • Query parameter (?key=value) or URL fragment (#URL-fragment) is included in the LIFF endpoint URL
  • Methods for converting additional information in the LIFF URL is set to Concatenate

For example, if Endpoint URL is set tohttps://example.com/path/?id=xxxxxxx, accessing a permanent link obtained by executing liff.permanentLink.createUrl() would redirect you to a URL without the ending slash, such as https://example.com/path?id=xxxxxxx.

In LIFF v2.3.2, the error has been fixed so that you are correctly redirected to https://example.com/path/?id=xxxxxxx.

LIFF v2.4.0 has already been fixed

As announced on August 31, 2020, this bug fix has already been reflected in LIFF v2.4.0.

# Fixed error in which fragment was not included in the secondary redirect URL


Affected version

  • LIFF v2.3.2

Changes

When a fragment was included in the LIFF endpoint URL or LIFF URL, regardless of settings based on Methods for converting additional information in the LIFF URL, the secondary redirect URL would not include a fragment. This error has been fixed.

For more details on the secondary redirect URL or how it is affected by settings based on Methods for converting additional information in the LIFF URL, see the LIFF document Operation from accessing LIFF URL to opening LIFF App.

# Fixed bug in which LIFF URLs were redirected to unintended URLs


Affected versions

  • LIFF v2.1.14
  • LIFF v2.2.1
  • LIFF v2.3.2

Changes

In the primary redirect destination URL, additional information specified in the LIFF URL (ex:path/?key=value) is included in the liff.state query parameter. When additional information was included in the liff.state query parameter, there was bug in which you were redirected to unintended URLs as shown below.

Conditions under which this problem occurs
  • There is no / at the beginning of the liff.state query parameter
  • Methods for converting additional information in the LIFF URL is set to Replace (Backward compatibility mode)

For example, when Endpoint URL is set to https://example.com, and the liff.state query parameter was path, the domain name and path would not be separated by /, resulting in being redirected to https://example.compath.
In LIFF v2.1.14, v2.2.1, v2.3.2, the bug has been fixed so that you are correctly redirected to https://example.com/path.

Regarding vulnerability caused by unintended redirects

There is a possibility that users are redirected to malicious websites due to this bug. If you are using a LIFF SDK version before v2.4.0, we recommend that you update it.

For more information on what happens when accessing LIFF URLs, see the LIFF document Operation from accessing LIFF URL to opening LIFF App.

Notice about service outage for LINE Notify (resolved)

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

# Date and time of outage

September 11, 2020 15:16 JST (GMT+9) - September 11, 2020 16:42 JST (GMT+9)

# Cause of the outage

Issues with our operations.

# Affected services

LINE Notify (opens new window)

# Details

During the date and time stated above, LINE Notify was unable to send messages. It has been resolved and messages are now being sent properly.

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

Messaging API update for September 2020

We've added new features to the Messaging API.

These are the features added in this update:

# Narrowcast messages can now be sent within the maximum number of messages that can be delivered

The limit.upToRemainingQuota property has been added to narrowcast messages.

By specifying this property when delivering a narrowcast message, you can send the message within the maximum number of messages that can be delivered.

What is the benefit of using the limit.upToRemainingQuota property?

If you try to send narrowcast messages that exceed the maximum number of messages that can be delivered, the delivery will fail.

For this reason, it was necessary to specify the maximum number of messages to send before sending narrowcast messages.

For example, if you can send up to 750 messages in a month, you'll send them with the limit.max property set to 750.

However, if you set the limit.upToRemainingQuota property to true, even if the number of messages to be sent exceeds the maximum number of messages that can be sent, the message won't fail and will automatically be sent within the limit.

The advantage of this property is that it automatically delivers within the maximum number of targets without having to check how many messages you can still send.

The distribution targets will be randomly selected.

For more information, see the limit.upToRemainingQuota property in the Send narrowcast message section of the Messaging API reference.

For more information on the maximum number of messages that can be delivered, see Messaging API pricing.

# The maximum size of JSON data that defines a bubble is 30 KB

The maximum size of JSON data that defines a bubble in Flex Messages has changed.

Subject Before change After change
Maximum size 10KB 30KB

For more information about Flex Message bubble containers, see Bubble in the Messaging API reference.

[Updated] LIFF v2.4.0 released

Added on September 24, 2020

LIFF v2.4.0 is no longer recommended due to a bug in the transition to another LIFF app without closing your current LIFF app feature.

Items Before the changes After the changes
LIFF SDK 2.4.0 2.4.1
LINE 10.16.0 10.18.0

If you are using LIFF v2.4.0, we recommend that you update to v2.4.1.

We have released LIFF v2.4.0. The changes in LIFF v2.4.0 are as follows:

# You can now use liff.closeWindow() before the LIFF app is initialized

You can now use the liff.closeWindow() method before the initialization of the LIFF app, even before the initialization of the LIFF app by liff.init() has finished.

Condition to execute the liff.closeWindow() method before initializing the LIFF app

To use the liff.closeWindow() method before the initialization of the LIFF app by liff.init() has finished, your LIFF SDK version must be v2.4.0 or later, and the user's LINE version must be 10.15.0 or later.

You can close the LIFF app with the liff.closeWindow() method if the LIFF app fails to initialize due to a network error, the user's LINE version, etc., as shown below.

liff
  .init({
    liffId: "123456-abcedfg" // Use own liffId
  })
  .then(() => {
    // Start to use liff's api
  })
  .catch((err) => {
    // Error happens during initialization
    console.log(err.code, err.message);
    liff.closeWindow();
  });

For more information, see liff.closeWindow() in the LIFF API Reference.

# You can now transition to another LIFF app without closing your current LIFF app

If you click the link to another LIFF app within a LIFF app whose screen is on Full display, you can display the other app while still having the LIFF browser open.
The LIFF browser doesn't close, so you can return to the original LIFF app with the return button from the LIFF browser.

Conditions for moving to another LIFF app without closing the current LIFF app (added on September 24, 2020)

There was a bug in LIFF v2.4.0 that prevented the feature from working properly. These changes have been made to the operating conditions for this feature:

  • LIFF SDK v2.4.1 or later and LINE 10.18.0 or later
  • The original LIFF app screen is set to Full display
  • The LIFF app to which you are moving is correctly initialized by liff.init()

LIFF-apps-transition

For more information, see Opening a LIFF app from another LIFF app in the LIFF Document.

# The error that LIFF URLs are redirected to unexpected URLs was fixed

An additional information (path/?key=value) specified in a LIFF URL is included in the liff.state query parameter for the primary redirected URL. When the liff.state query parameter contains an additional information, it might be redirected to an unexpected secondary redirected URL as follows.

Conditions that cause this error
  • When the liff.state query parameter doesn't begin with /
  • When setting Methods for converting additional information in the LIFF URL to Replace (Backward compatibility mode)

For example, if Endpoint URL is set to https://example.com and the liff.state query parameter is assigned to path, it was redirected to https://example.compath because the domain name and the path were not separated by /.
In the LIFF v2.4.0, this error has been fixed so that the URL above is now correctly redirected to https://example.com/path.

For more information on behaviors when accessing a LIFF URL, see Behaviors from accessing the LIFF URL to opening the LIFF app.

# liff.permanentLink.createUrl() error was fixed

When information, such as query parameter (?key=value) or URL fragment (#URL-fragment), was included in the LIFF endpoint URL, on occasion, the additional information section was not accurately reflected in the permanent link when liff.permanentLink.createUrl() was executed. This error has been fixed.

# The error of fragment not being included in the secondary redirct URL was fixed

When a fragment was included in the LIFF endpoint URL or LIFF URL, regardless of settings based on Methods for converting additional information in the LIFF URL, the secondary redirect URL would not include a fragment. This error has been fixed.

For more details on the secondary redirect URL or how it is affected by settings based on Methods for converting additional information in the LIFF URL, see the LIFF document Operation from accessing LIFF URL to opening LIFF App.

Certificate authority that can be used in the Webhook URL added

The webhook URL must use HTTPS and have an SSL certificate issued by a certificate authority trusted by LINE.

The following certificate authorities have been added to the list of certificate authorities trusted by LINE.

CN=TWCA Global Root CA, OU=Root CA, O=TAIWAN-CA, C=TW

For more information on configuring Webhook URL settings, see Webhook URL settings.

LINE Blockchain Platform is now available

The LINE Blockchain Platform, which consists of these three components, is now available.

# LINE Blockchain

LINE Blockchain is a blockchain platform developed and operated by LINE with performance and reliability designed to serve and withstand hundreds of millions of LINE users.

Learn more about LINE Blockchain (opens new window).

# LINE Blockchain Developers

LINE Blockchain Developers provides the console and APIs for services using LINE Blockchain. Using this service, developers can easily navigate through the console and develop in a familiar environment.

Learn more about LINE Blockchain Developers (opens new window).

# BITMAX Wallet

BITMAX Wallet is an integrated wallet that allows users to store and transfer digital assets of LINE Blockchain services. Users can retrieve information on their assets on LINE Blockchain or send assets to others. Service providers must integrate BITMAX Wallet to their own services to let the users access or transfer their assets within the services.

As BITMAX Wallet uses LINE accounts, the assigned user wallets are mapped on a one on one basis to the user’s LINE account. Once registered to BITMAX Wallet, users can select a chain and browse either Cashew based tokens or Daphne based tokens.

Learn more about BITMAX Wallet (opens new window).

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

From: August 4, 2020 around 11:00 JST (GMT+9)
Until: August 14, 2020 around 13:00 JST (GMT+9)

# Cause

Issue with our servers.

# Details

During the specified time, the statistics graph in the Statistics tab for Messaging API channels in the LINE Developers Console was not displayed as intended. It is resolved now and the graph is being displayed properly.

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

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

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

The initial plan was to complete the transition by April 30, 2020, but we extended the transition period to October 30, 2020, based on the usage situation.

# 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 cause. Thank you for your understanding.

# Transition period

November 8, 2019 - October 30, 2020 14:00

The endpoint to get statistics is now available in Indonesia (ID)

The endpoint of the Messaging API to get statistics is now available in Indonesia (ID).

Before, LINE Official Accounts created by Indonesian (ID) users weren't able to obtain this statistic. This update has removed this restriction.

[Updated] Messaging API update for August 2020

We've added new webhook events and an API endpoint to the Messaging API.

These are the features added in this update:

# Unsend event has been added

In addition to existing webhook events, such as join, leave, and send messages, a new "Unsend event" has been added, which indicates that the message has been cancelled.

# Video viewing complete event has been added

A new "Video viewing complete event" has been added. This event occurs when a user finishes watching a video with a trackingId property for video identification.

# The audiences property is now optional instead of required for a certain endpoint

The audiences property has been changed from required to optional for the following endpoint.

This spec change allows you to prepare an audience by creating an audience with no recipient specified first, and then adding user IDs or IFAs to the audience later.

# Recipients of an audience can be now specified by file

You can now specify the recipients of an audience by file.

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

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

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.

已新增識別 Channel Access Token 的 Key ID

基於資安的原因,Get all valid channel access tokens v2.1 的 Endpoint 會回傳重新加密後的 channel access tokens。

藉由這次的更新,在產生 channel access token v2.1 時會回傳一個對應 token 的 unique key ID (key_id)。您可以使用新的 Get all valid channel access token key IDs v2.1 的 Endpoint 來識別對應的 channel access tokens。

預計會棄用的 Endpoint

由於此次的更新,我們預計於七月上旬建議勿用 Get all valid channel access tokens v2.1 的 Endpoint。如果您正在使用此 Endpoint,請將您的 Bot 修改為新的 Get all valid channel access token key IDs v2.1 的 Endpoint。

更多關於發行channel access token v2.1的內容,請參考Messaging API技術文件。

發布 LIFF v2.2.0 追加的 LIFF error code

關於下列的方法,當 Promise 被 reject 時皆已追加 LiffError code 的資訊於其中,以便讓錯誤訊息更容易被理解。

更多訊息,請見各方法的Error Response說明:

「Linked OA」於 LINE Developers console 內的設定位置已變更

LINE Developers console 中特定 channel 類型的 Linked OA 設定位置已變更。

項目 變更前 變更後
Linked OA的位置 位於channel中的LINE Login分頁 channel中的Basic Settings分頁

# 受影響的channel類型

  • LINE Login
  • [BETA] Blockchain Service

# 影響

既有的 LINE Login 或是 Blockchain service channel 行為將不會受此項更新影響。

未來於LINE Developers console中新增包含Linked OA設定的新channel類型,將會適用此更新位置。

關於Linked OA的設定方法,請參考利用您的channel連結LINE官方帳號

Messaging API更新(2020年6月)

Messaging API 追加了新的 endpoint。以下為本次更新的功能:

Endpoint

新功能的敘述如下。若需了解更多細節,請查閱 Messaging API reference 中各個新功能的說明。

# 取得群組的資訊

當你的 LINE 官方帳號是群組的其中一員時,可取得的群組 ID、群組名稱以及群組圖示連結。

關於更多資訊,請查看Messaging API reference中的取得群組的資訊

# 取得群組裡的成員總數

取得群組中的成員總數。即使其中的成員尚未將LINE官方帳號加為好友,或是已將LINE官方帳號封鎖,您都可以取得群組成員的總數。

關於更多資訊,請查看Messaging API reference中的取得群組裡的成員總數

# 取得聊天室的成員總數

取得聊天室的成員總數。即使其中的成員未將LINE官方帳號加為好友,或是已將LINE官方帳號封鎖,您都可以取得聊天室成員的總數。

關於更多資訊,請查看Messaging API reference中的取得聊天室的成員總數

Flex Message Simulator 的教學指南

我們發布了第一個關於使用Flex Message Simulator (opens new window)的教學指南。

遵循教學指南,您將能獲得關於使用Flex Message Simulator的實際操作經驗與知識。並且,在教學指南的最後,您將會使用Flex Message製作出如下方的出數位名片:

Final Output

我們鼓勵您把握這次機會去學習如何使用Flex Message Simulator並創造出屬於您獨特的 Flex Message。

已發布永久鏈結的 API 至文件上

LIFF SDK 能夠為當前的頁面建立一個永久鏈結。 我們將會發布建立永久鏈結的方法並放置於API 文件上。

  • liff.permanentLink.createUrl()
  • liff.permanentLink.setExtraQueryParams()

這些 API 已包含在最新的 LIFF SDK 中,因此當前 LIFF SDK 的版本不需變動。

更多關於取得永久連結的資訊,請參考LIFF技術文件中的Get a permanent link for the current page

[更新] 近期內你將可以在LIFF endpoint URL中增加路徑(path)功能

2020年5月29日註記

這項規格更動原本預計在2020年5月的最後一週施行,但因考量到對現有LIFF app的影響,我們將改採取下列措施:

  • 如2020年5月20日的通知內容,我們將在endpoint URL中新增使用路徑的功能。
  • 我們計畫以不影響現有LIFF app的方式來新增此規格。
  • 規格更動預計於2020年6月下半施行。

對於重複的規格變動所造成混淆,我們致上誠摯的歉意。

目前開發者可在LINE Developers Console的LIFF tab的URL後輸入路徑 (/path)、query parameters (?key=value)與URL fragments (#URL-fragment),但僅有Domain Name與URL中的query parameters會被使用。

隨著接下來的更新內容,LIFF endpoint URL將會有以下更動:

  • 可使用路徑 (/path)。
  • 不可再輸入URL fragment (#URL-fragment)。

舉例而言,如果您在Heroku部屬LIFF app,您可以在LINE Developers Console的基本資訊中輸入https://{Heroku app name}.herokuapp.com/path/?key=value作為Endpoint URL

附有路徑的LIFF URL追加至console

URL scheme請務必使用https。

能在console中輸入的路徑(path)意味著可以降低發布新頁面所需的時間。例如,當前發布頁面為活動頁面時,您可以直接在endpoint URL中輸入您的活動頁面網址https://example.com/2020campaign上去。

注意

對於在console中註冊endpoint URL以及用來開啟LIFF app的URL scheme,兩者URL fragment的使用條件並不相同。請多加留意避免混淆。

Endpoint URL:
https://example.com/2020campaignhttps://example.com/2020campaign/?key=value
不可增加URL fragment。

用來開啟LIFF app的URL scheme:
https://liff.line.me/{liffId}/path_A/path_B/#URL-fragment
可以加上URL fragment。

欲知更多巧參閱LIFF的技術文件中關於Adding a LIFF app to your channel的部分。

對於舊有規格所造成的混淆,我們致上真摯的歉意。我們將會持續改善提供給開發者的服務品質,同時感謝您的諒解。

# 預計變更規格的日期

2020年6月下半。

在LIFF app中已可使用OGP標籤

目前可以在LIFF app中的各個頁面中設定OGP標籤。例如在聊天室內分享您的LIFF app連結(https://liff.line.me/{liffId})時,您將可以隨意設置標題、說明、與縮圖等等。

下方為LIFF可支援的OGP標籤。 更多關於OGP標籤的訊息,請參考The Open Graph protocol (opens new window)

<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">
注意

當使用line://app/{liffId}(不建議使用)的形式分享連結時,OGP標籤將會被忽略。

Messaging API更新(2020年5月)

我們對Messaging API做了幾項改善。

# 訊息的字數限制與影音檔案使用條件的調整

目前已調整針對文字訊息的字數限制以及影音檔案使用條件。請參考下方表格比對變更前後的差異。

  • 文字訊息

    項目 變更前 變更後
    最大字數 2000 5000
  • 圖文選單(Richmenu)物件 (圖片)

    項目 變更前 變更後
    圖片尺寸
    (寬度 x 高度)
    2500px × 1686px
    2500px × 843px
    1200px × 810px
    1200px × 405px
    800px × 540px
    800px × 270px
    800px以上 x 2500px以下 *

    * 寬度/長度的比例應至少為1.45。

  • 圖片訊息 (圖片)

    項目 變更前 變更後
    檔案格式 JPEG JPG, JPEG, PNG
    圖片尺寸上限 4096px × 4096px 無限制
    檔案大小上限 1MB 10MB
  • 影片訊息 (影片)

    項目 變更前 變更後
    長度上限 1分鐘 無限制
    檔案大小上限 10MB 200MB
  • 語音訊息 (語音)

    項目 變更前 變更後
    長度上限 1分鐘 無限制
    檔案大小上限 10MB 200MB
  • Imagemap訊息 (圖片)

    項目 變更前 變更後
    檔案大小上限 1MB 10MB
  • Imagemap訊息 (影片)

    項目 變更前 變更後
    長度上限 1分鐘 無限制
    檔案大小上限 10MB 200MB
  • 圖片訊息 / 影片訊息 / Imagemap訊息 (預覽圖片)

    項目 變更前 變更後
    檔案格式 JPEG JPEG, PNG
    圖片尺寸上限 240px x 240px 無限制

# 從webhook event的message物件中取得LINE表情貼資訊

如果使用者傳送的文字中包含LINE表情貼,則在webhook接收到文字訊息物件時會包含emojis的屬性,相關資訊被歸納在LINE emoji物件當中。

LINE表情貼種類是由productIdemojiId來識別:

{
  "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"
      }
    ]
  }
}

更多細節請參考Messaging API reference中的Text部分。

# 安全地重新呼叫已失敗的API請求

如果在使用Messaging API傳送訊息時出現錯誤,或是請求超時,您將無法得知訊息是否有正確地傳給使用者。而重新發送相同請求時,若第一次的請求已成功傳送,將可能導致使用者接收到同樣的訊息兩次。

您可以將retry key(X-Line-Retry-Key)追加至HTTP Header來安全地重新發送相同的請求。

Retry key的值是由十六進制隨機產生的UUID(例如: 123e4567-e89b-12d3-a456-426614174000)。無論API請求時使用多少次含有相同UUID的retry key,終將只會有一次請求被接受,避免重複執行相同請求。而透過retry key,能使API請求在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"
        }
    ]
}'

更多資訊請參考重新嘗試失敗的API請求

LIFF版本政策與生命週期已釋出

為了使各個LIFF版本的目的更明確,我們將公開LIFF版本政策。 我們同時也公開了各個主要版本的生命週期,讓使用者可以為LIFF的版本升級做適當的準備。

請使用最新版本的LIFF SDK

2019年10月16日的通知,LIFF v1將會被中止。 在中止後,您將無法使用LIFF v1來開啟LIFF app。

更多關於主要版本的生命週期與LIFF v1的中止時間,請參考LIFF技術文件中的LIFF SDK生命週期

# LIFF版本政策

自LIFF v2.2.0開始,LIFF的版本號將會遵循Semantic Versioning (opens new window) (SemVer)所設定的規範。

SemVer定義了下方的版本格式:

主版號(MAJOR).次版號(MINOR).修訂號(PATCH)

舉例而言,在v1.2.3, 1是主版號,2是次版號,3則是修訂號。

LIFF版本政策解釋了主要版本的生命週期並就各個版本(主要版本、次要版本、修訂版本)對開發者的意義提出說明。

# LIFF SDK (sdk.js)的更新政策

自LIFF v2.1.13發布後,我們準備了兩種CDN路徑。 在將LIFF SDK整合至LIFF app時,請指定符合您目的的CDN路徑。

CDN路徑 說明
CDN edge路徑 僅指定主要版本的方法。 不用更新您的LIFF app,也可以使用最新版本的LIFF SDK。
例: https://static.line-scdn.net/liff/edge/2/sdk.js
CDN固定路徑 可指定至修訂版本的方法。只要未更新LIFF app,即可繼續使用指定的修訂版本。由於其不會自動更新,故不會受到LIFF SDK升級的影響。
例: https://static.line-scdn.net/liff/edge/versions/2.1.13/sdk.js

使用Edge路徑的範例:

<script charset="utf-8" src="https://static.line-scdn.net/liff/edge/2/sdk.js"></script>
關於維持向下相容的CDN路徑

為了確保已上線的LIFF app運作,我們將提供下列CDN路徑來維持LIFF SDK的作業。使用此CDN路徑的LIFF SDK會與CDN edge路徑的LIFF SDK同一版本。

維持向下相容的CDN路徑為:
https://static.line-scdn.net/liff/edge/2.1/sdk.js

注意

我們建議您將LIFF app中向下相容的CDN路徑改為CDN edge路徑。因為無論LIFF SDK的生命週期預計為何時,使用向下相容的CDN路徑都可能遭到中止。

待方針確立後我們會盡速通知。

在LIFF技術文件中查看更多關於LIFF版本政策的資訊。

「受眾群體」(Audience)與「分析」(Insight)的部分API恢復通知

我們在2020年4月22日發布了[更新] 關於Audience和Insight在一些集成式API中服務故障的問題。上述API現已可在受限制的狀況下使用。

請留意相關訊息的傳送日期與時間,關於建立曝光再行銷的受眾群可能會受限制,以及統計資料可能會有相關回傳值。

  • 訊息發送的時間(JST): ~2020年3月29日,23:59:59
    狀態:現已無限制。

    • 受眾群體已可以創建。
    • 統計資料已可正常回傳。

  • 訊息發送的時間(JST): 2020年3月30日 00:00:00~2020年4月29日23:59:59
    狀態:有限制。

    • 受眾群體無法創建。
    • 統計資料中的 overview.uniqueImpressionmessages[].impression會有相關回傳值。

  • 訊息發送的時間(JST): 2020年4月30日 00:00:00~
    狀態:有限制。

    • 受眾群體已可以創建。但是,如果有使用者在這段時間內使用受限制的LINE版本開啟訊息,該使用者將無法接收到使用受眾群體所送出的新訊息。
    • 統計資料已可正常回傳。但是,統計資料中將不包含使用者在這段時間內利用受限制的LINE版本開啟訊息的次數。

關於更多資訊,請參考下方頁面:

我們將會持續改善我們向各位發開者提供的服務品質,並對於您的理解致上真誠的感謝。

Messaging API服務中斷通知 (已修復)

我們必須通知您關於Messaging API近期發生的服務中斷問題。 所有由Messaging API提供的功能皆有可能受到影響。

這項問題目前已解決。Messaging API自下方的發生時間後已恢復正常運作。對於遲來的通知與此問題所造成的不便,我們致上誠摯的歉意。

# 發生時間

日期: 2020年4月24日

時間: 14:41-17:46 (GMT+9)

# 原因

網路故障

# 影響範圍

所有由Messaging API提供的功能皆有可能受到此問題影響。

LINE將會持續改善我們的服務品質以避免未來發生相關問題。感謝您的諒解。

LIFF v2 已提供 liff.getLineVersion() 與 liff.id 的用法

目前已將方法 - liff.getLineVersion() 與屬性 - liff.id 新增至 LIFF v2 當中。

liff.getLineVersion() 將允許取得使用者的 LINE 版本。

如果使用者是藉由LINE內建瀏覽器開啟LIFF app,該使用者的LINE版本即會以字串回傳。如果使用者是以外部瀏覽器開啟LIFF app,則會回傳null

liff.id 的屬性為 liff.init() 初始化後所持有的 LIFF app ID (字串型態)。

欲了解更多請參考LIFF v2 API reference中的liff.getLineVersion()liff.id

[更新] 關於 Audience 和 Insight 在一些集成式 API 中服務故障的問題

2020年5月1日更新

在 2020 年 4 月 22 日我們回報了此 API,目前已可在有限制的狀況下使用它。

關於更多訊息,請參考下方頁面:

Messaging API 發生了下列故障的問題。對此造成您的不便,我們致上誠摯的歉意。

# 發生時間

日期: 2020 年 4 月 13 日

時間:約 15:30~ (GMT+9) (持續中)

# 細節

在上述時間發生之後,無法準確計算出曝光再行銷的受眾群的曝光量。

因此我們暫時限制了部分功能的使用。整體來說,我們將會採取以下行動:

我們正積極的調查與修復此問題。

LINE 將會持續改善我們的服務品質以避免未來發生相關問題。感謝您的諒解。

提醒:關於 liff.shareTargetPicker() 回傳值的修改通知

由於我們將會更改 LIFF v2 的 liff.shareTargetPicker() 回傳值。 若您目前的實作正使用到此功能,請參考相關規格並修改。

注意

目前尚未確定關於變更後的 liff.shareTargetPicker() 回傳值規格。

# 概要

在規格改變前,LIFF app 僅可確認 target picker 是否已顯示,但無法確認訊息是否已被傳送。

在規格改變後,LIFF app 不僅可以確認訊息是否已被傳送,並且能配合使用情境,進行相關功能的實作。

# 尚未變更規格之前

# 範例

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")
    })
}

# 語法

liff.shareTargetPicker(messages)

# 回傳值

回傳Promise物件。

當 target picker 顯示後,Promise 會被 resolve。

如果 target picker 在顯示前發生錯誤,除了 Promise 會被 reject 外,並且會發送 LiffError。更多關於 LiffError 物件的資訊,請參考 LIFF SDK errors 文件

注意
  • 若使用者在顯示 target picker 時未選擇傳送目的地,將無法確認 target picker 顯示後的情況。
  • Promise 被 resolve 與 reject 的 callback 函數中,LIFF app 在某些裝置中無法使用 alert()

# 規格變更之後

# 範例

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')
  })
}

# 語法

liff.shareTargetPicker(messages)

# 回傳值

回傳Promise物件。

如果訊息被正確傳送,Promise 會被 resolve 並發送含有成功狀態的訊息。

如果使用者在訊息被傳送前取消或關閉 target picker,Promise 會被 resolve,但不會發送含有成功狀態的訊息。

如果 target picker 在顯示前發生錯誤,除了 Promise 會被 reject 外,並且會發送 LiffError。更多關於 LiffError 物件的資訊,請參考 LIFF SDK errors 文件

之後我們預計會隨著規格的變更,並修改 Error 的定義。

注意

Promise 被 resolve 與 reject 的 callback 函數中,LIFF app 在某些裝置中無法使用 alert()

# 預計規格變更的時間

未定。

【更新】Messaging API升級(2020年4月)

2020年4月16日更新

2020年4月14日通知的下列Property名稱已變更。

變更前 變更後
sticon emojis
sticon.sticonId emojis.emojiId

Messaging API進行了下列改善。

# 利用文字訊息傳送LINE表情貼

利用Messaging API傳送文字訊息之際,可傳送Unicode定義的表情貼、LINE獨家定義的表情貼(不建議),現在更可傳送LINE表情貼了。

LINE表情貼以productIdemojiId指定。

// 含有LINE表情貼的文字訊息示例
{
    "type": "text",
    "text": "Look at this: $ It's a LINE emoji!",
    "emojis": [
        {
            "index": 14,
            "productId": "5ac1bfd5040ab15980c9b435",
            "emojiId": "001"
        }
    ]
}

詳情請參閱《Messaging API reference》的「文字訊息」。

# 取得用戶語言

取得個人資料端點,既存的用戶個人資料資訊會和languageProperty一起退回。

languageProperty僅會在下列任一情況下退回。

  • 用戶使用在日本建立的LINE帳號,且同意LINE 8.0.0版本之後的隱私權政策
  • 用戶使用在台灣、泰國,或印尼建立的LINE帳號,且同意LINE 8.9.0版本之後的隱私權政策

# Multicast的收訊人數限制已刪除

傳送Multicast訊息 端點原本有限制1分鐘的收訊人數,此限制已在今天刪除。其他速度限制將繼續適用。關於變更前的限制和變更後的差異,請參閱下表。

Bot種類 變更前 變更後
LINE官方帳號綁定的Bot 100,000 Request/分
1,700 Request/秒(※)
2,000,000 收訊人/分
100,000 Request/分
1,700 Request/秒(※)
LINE@帳號綁定的Bot 10,000 Request/分
170 Request/秒(※)
200,000 收訊人/分
10,000 Request/分
170 Request/秒(※)

※1秒單位的速度限制為大量傳送時的大概速度。

不僅如此,傳送Multicast訊息時,最多可指定500筆用戶ID(原為150筆,增加至500筆)。

詳情請參閱《Messaging API reference》的「速度制限」。

全文搜尋功能已恢復

LINE Developers網站在2020年1月27日更新,透過網站的重新設計 (opens new window),以期利用標題搜尋而非全文搜尋,來達成站內搜尋的高速化。

網站上線後,我們根據各位的意見,再次安裝了全文搜尋功能。

若想利用全文搜尋,請輸入搜尋關鍵字,並選擇全文搜尋

全文搜尋

只要選擇全文搜尋,就會顯示全文搜尋的結果。

全文搜尋結果

非常感謝各位提供的寶貴意見。我們今後仍會繼續努力提升LINE Developers網站及開發人員專用文件的品質。

Channel Access Token v2.1已上線

Channel Access Token的最新版本已上線。新版本除了能指定Token的有效期限之外,亦可用JSON Web Token(JWT)來取代Channel Secret強化安全性。

建議您使用Channel Access Token最新版本。

JWT的生成方法

可使用任意的JWT函式庫 (opens new window),亦可自己寫Code 由Assertion Signing Key生成JWT。生成JWT是發行Channel Access Token v2.1必要的手續。

# 新追加的API

關於現在可利用的Channel Access Token種類及其不同,請參閱《Messaging API Document》的「Channel Access Token」。

LIFF v2已追加liff.isApiAvailable()

LIFF v2已追加liff.isApiAvailable()。 可確認指定的API是否能在LIFF應用程式啟動的環境下使用。

注意

可指定的API有限。 目前的適用對象為liff.shareTargetPicker()。 今後在可於liff.isApiAvailable()指定的API增加時,將再次通知。

# 確認可否使用Target Picker

透過事先執行liff.isApiAvailable(),在不可使用Target Picker的環境下執行liff.shareTargetPicker()之際,可避免用戶畫面顯示錯誤訊息。

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

詳情請參閱《LIFF v2 API Reference》的「liff.isApiAvailable()」。

LINE Login允許存取的畫面變更

我們修改了LINE Login允許存取畫面的部分設計與文字,以更加方便使用者的閱讀與使用。

# 變更

  • 為了讓使用者更加容易了解在畫面上應採取的動作,我們刪除了畫面標題允許存取並將畫面說明修改為此服務提供者要求以下的存取權限
  • 您可以藉由點選要求存取的項目中的Arrow icon圖示,來決定是否要顯示或隱藏各項的說明文。
  • 我們將許可的按鈕放大使其更加明顯。

Improved LINE Login Consent Screen

本次修改的許可畫面將會出現在app向使用者請求存取權限的過程中。更多資訊請查看要求授權

新「訊息貼圖」的資源型態已新增至貼圖訊息的webhook事件

隨著LINE訊息貼圖 (可輸入客製化文字的貼圖)的推出,對用於通知貼圖訊息傳送的webhook事件,我們在其stickerResourceType屬性中新增了PER_STICKER_TEXT

如果一位LINE使用者向您的LINE官方帳號傳送了訊息貼圖,您將會收到一則包含PER_STICKER_TEXT stickerResourceType的webhook事件物件。

更多資訊請查看『Messaging API參考資料』中的貼圖

LINE Beacon已中止於多個版本的服務

March 10, 2020所通知,LINE Beacon已不再適用於LINE的下列版本:

  • 日本: LINE 8.17.0之前的任何版本
  • 台灣: LINE 9.14.0之前的任何版本
  • 泰國: LINE 9.8.0之前的任何版本
  • 印尼: LINE 9.8.0之前的任何版本 (無異動)

# 影響

以上版本的使用者無論是進入或離開LINE Beacon的發送範圍,都將無法被偵測到。

  • Webhook Beacon事件將不會傳送給bot app。
  • 該當使用者將無法看到Beacon橫幅廣告。

更多關於LINE Beacon的資訊,請查看使用Beacons

對於這項改變可能造成的不便,我們致上誠摯的歉意。我們將會持續改善LINE的服務品質。感謝您的諒解。

不建議使用LINE URL scheme 'line://'

由於LINE URL scheme line://可能會產生接管攻擊,因此不建議使用。請改用https://line.me/R/https://liff.line.me/

line://接管攻擊是指使用者在點擊line://時,其他非LINE的app可能會不顧使用者的意願自動開始執行。這項攻擊僅會在特定的情況下發生。

line://將來有可能會受到中止。如有進一步的決定,我們會在此通知。

更多關於LINE URL scheme的資訊,請查看『透過LINE URL scheme使用LINE功能』。

提醒: Endpoint 網域名稱變更通知

如同 2019 年 11 月 8 日新聞所述,部分 Messaging API endpoint 的網域名稱 (domain name) 由 api.line.me 變更為 api-data.line.me.

# 變更網域名稱的 endpoint:

# 影響

使用以上 endpoint 的開發者,請於轉換期限前變更網域名稱。

轉換期結束後,使用以上 endpoint 的舊網域名稱將會顯示 404 錯誤訊息。

如造成任何不便,敬請見諒,感謝配合。

# 轉換期間

2019 年 11 月 8 日 起至 2020 年 4 月 30 日

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.

所有 Narrowcast 及 Audience Management 英文技術文件正式上線

介紹如何透過 Messaging API 發送 Narrowcast 訊息、管理受眾的英文技術文件,已全數上線。

最新英文文件:

之前翻譯為英文的文件 (請見新聞 2020 年 2 月 19 日):

上述 Narrowcast 及 Audience Management 功能的相關新聞:

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.

Messaging API narrowcast 英文技術文件正式上線

介紹如何透過 Messaging API 發送 narrowcast 訊息、管理受眾的 (部分) 英文技術文件正式上線:

部份文件仍為日文,近期內將翻譯為英文:

欲查看上述 Messaging API 功能的相關新聞,請至:

LINE Things 停止為新 app 提供 LIFF app BLE 新功能

自 2020 年 2 月 10 日起,LINE Things Developer Trial 已停止提供 LIFF app BLE 新功能,且未來將不會恢復提供; 目前僅提供自動通訊功能 (automatic communication)。

2020 年 2 月 10 日之後建立的新 app 將無法於 LINE Things Developer Trial 中使用 LIFF app BLE 新功能。

LINE 團隊持續改善服務品質,如造成不便敬請包涵。

LIFF v1 API 及停用日期變更

日前新聞宣佈 LIFF v1 Server API 將於 2020 年 3 月 31 日停用,因考量用戶意見,將繼續提供相關 API。

LIFF v1 停用日期確認後,將即時發佈相關通知。同時,請 v1 用戶儘快改用 v2。

功能 原訂停用日期 新的停用日期
LIFF v1 Client API 未來將停用 未來將停用 (此計畫維持不變)
LIFF v1 Server API 2020 年 3 月 31 日停用 繼續提供服務
未來仍將停用 LIFF v1

如同 2019 年 10 月 16 日新聞所述,LIFF v1 將被停用,請改用最新版本。

使用者無法在 Messaging API channel 新增 LIFF app

如同 2019 年 11 月 11 日新聞所述,由於 LIFF v2 功能改善,使用者無法繼續在 Messaging API channel 新增 LIFF app。

欲了解已在 Messaging API channel 新增的 LIFF app 將受到哪些限制,以及如何改將 LIFF app 綁定至 LINE Login channel,請查看 2019 年 11 月 11 日發佈的新聞內容。

受眾群體分享功能正式上線

現在,開發者可於 LINE Official Account Manager 和 LINE Ad,使用以 Messaging API 建立的受眾群體 (Audience)。

受眾群體協助更精準地將廣告訊息發送給真正感興趣的用戶,透過使用受眾群體,開發者可將訊息傳送給之前曾開啟訊息,或點擊訊息連結的用戶。

之前建立過的受眾群體,將自動顯示於 LINE Official Account Manager 和 LINE Ad 中,開發者不須更改任何設定。

如欲取得更多受眾群體相關訊息,請查看 Messaging API 技術文件中的 Using audiences

全新設計的 LINE Developers 網站正式上線

全新設計的 LINE Developers 網站已正式上線,協助開發者更輕鬆地使用 LINE Platform 並找到所需的技術文件。

本次網站更新的重點包含:

# 網頁加載速度更快

現在,本網站為在 VuePress 上執行的單頁應用 (single-page application),大幅縮短網頁加載時間。

# 經優化的瀏覽體驗

經優化的 API reference 響應式設計 (responsive design),讓網頁配合螢幕尺寸自動調整版面,開發者可更輕鬆地閱讀 API 介紹與範例程式碼。

# 更強大的搜尋功能

只要輸入欲搜尋的關鍵字,搜尋欄位下方便會顯示相關建議,協助開發者更快找到所需的資訊。

Search Results

注意

儘管新的搜尋功能更為強大,搜尋建議仍僅會顯示頁面標題及頁首文字。LINE 團隊將於未來數週內收集內部建議,以了解使用者對於新搜尋功能的滿意度,並適時進行調整。

(LINE 團隊也正積極將開發者意見調查表整合至新網站。)

# 接下來呢?

除了將開發者意見調查表整合至新網站,LINE 團隊也將持續改善網站功能,協助開發者更輕鬆地使用 LINE Developers 網頁與技術文件。

請掃描下方 QR code 或點選 "Add friend" 按鍵,將「LINE開發者官方社群」官方帳號加為好友,以取得最新訊息:

QR code for the LINE Developers account

將 LINE 開發者官方帳號 (中文) 加為好友: Add friend (opens new window)

將 LINE 開發者官方帳號 (日文/英文) 加為好友: Add friend (opens new window)

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 將於 2020 年 3 月 31 日停用

LINE Front-end Framework (LIFF) v1 Server API 將於 2020 年 3 月 31 日起停止使用,下列 API 功能將被移除:

請使用最新版 LIFF

即日起請改用 LIFF v2。如同 2019 年 10 月 16 日新聞所述,LIFF v1 即將停用。

# 請使用 LIFF v2

上方所列的 Server API 功能可透過 LINE Developers Console 繼續使用,欲了解如何在 channel 新增 LIFF app,請查看:

如欲透過 LINE Developers Console 使用上列其他 3 項 Server API 功能,請點選該連結、查看技術文件。

LINE 團隊將持續改善服務品質,感謝您的配合。

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.

如使用已中止的 LIFF SDK API,請調整程式碼

如同 2019 年 11 月 29 日新聞所述,基於特定技術考量,下列使用於 iOS 的 LINE (v9.19.0 或之後版本) API 功能已被暫停使用:

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

自今日起,end user 於 iOS 使用的 LINE (v9.19.0 或之後版本) LIFF app 部分 API 功能如下:

API 功能
liff.scanCode() API 為 undefined
liff.bluetooth.* 如呼叫 liff.initPlugins(['bluetooth']) 時,Bluetooth plug-in 無法初始化,將顯示 FORBIDDEN 錯誤訊息。

如開發者使用 liff.scanCode(),強烈建議參考上述說明,確認功能可正常運作。

調整前:

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

調整後:

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

如欲取得更多相關訊息,請至 LIFF v2 API reference

LINE 團隊正積極改善服務品質,造成不便敬請包涵!

[Updated] 請確認 provider 名稱正確

2020 年 1 月 9 日追加說明

本功能原訂於 2020 年 1 月 9 日上線,但因故改於 2020 年 1 月 16 日上線。

自 2020 年 1 月 16 日起,使用 Messaging API 的 LINE 官方帳號,將於用戶資料下方顯示開發者註冊的 provider 名稱。

企業 LINE 官方帳號亦可能將個人名稱註冊為 provider 名稱,請確認所註冊的名稱正確無誤。Provider 可於 LINE Developers Console 進行更改。

用戶資料

*Provider 名稱如紅框中所示

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.

Messaging API webhook event 新增屬性 "mode"

Messaging API webhook event 新增屬性 mode

modechannel multiplexing 功能的必要屬性 (開發中)。目前,所有 webhook event 皆包含 "mode": "active"

mode 的值不會自動切換為 standby。若 channel 管理者開始使用 channel multiplexing 功能,可選擇將 mode 的值更改為 standby

如欲取得更多 mode 屬性相關訊息,請查看 Messaging API reference - webhook events 中的 Common properties 內容。

LINE SDK v4.x 相關內容移除

如同 2019 年 9 月 13 日 新聞所述,所有 LINE SDK v4.x 相關內容已自本網站移除,而原本導向這些內容的鏈結,已改為導向下列頁面:

LINE Developers Console - channel statistics 資料顯示問題 (已解決)

之前由於不同系統的時差設定有異,LINE Developers Console 中 Messaging API channel Statistics 表單所顯示的部份日期,與 TSV 檔案中所顯示的不一致 (TSV 檔案可透過點選 Download as TSV 按鍵產生)。

當時此狀況僅影響日本標準時間 (JST) 以外時區的資料顯示,且不會刪除或損毀資料。

# 發生時間

2019/11/26~2019/12/18

目前,此問題已排除,開發者可重新取得正常顯示的資料。之前所造成的不便,敬請包涵!

Beacon event 新增 stay event

Messaging API beacon event 新增 stay event,可指出用戶目前位於 beacon 所涵蓋的範圍內。

如欲使用 stay event,歡迎與 LINE for Business (opens new window) 團隊聯繫。

新的 LINE Login 通知訊息

當用戶使用 LINE Login v2.1 登入網頁,來自官方 LINE 帳號的登入通知訊息,內容會因登入方式而有所不同。

自 2019 年 12 月 9 日起,無論登入方式為何,用戶將收到統一的通知訊息內容。

LINE Login notification message

dummy dummy
登入成功 LINE系統提醒您,您目前已在 X 上登入 Y (Z)。
IP位址: {ip_address}
登入位置: {Location}
若您本人並未執行上述操作,請盡速由此連結的畫面中點選登出: {device_link}
如有疑慮,您可由此變更LINE密碼: {help_link}
登入失敗 LINE系統提醒您,剛剛有人嘗試在 X 上使用您的帳號登 Y (Z),但並未成功。
IP位址: {ip_address}
登入位置: {Location}
若您本人並未執行上述操作,請透過此連結來確認登入中的裝置: {device_link}
如有疑慮,您可由此變更LINE密碼:

請注意 (Z) 代表網頁連結,在某些情況下可能會被刪除。

# 適用對象

所有使用 LINE Login v2.1 登入網頁的 LINE 用戶。

Webhook event 新增屬性"貼圖訊息"

Webhook event 新增 stickerResourceType 屬性,開發者在收到貼圖訊息後,將可於訊息通知中取得此屬性。

開發者可透過此屬性,查看接收到的貼圖類型 (靜態貼圖、動態貼圖、動態有聲貼圖,或其他類型貼圖)。

如欲取得更多資訊,請至 Messaging API reference - Sticker 介紹。

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.

部分 LIFF 功能暫停使用

基於特定技術考量,下列 LIFF 功能已被暫停使用;恢復使用後,將即時發佈相關通知:

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

# 受影響之作業環境

環境 版本
LINE for iOS 上述功能暫時無法於 iOS 9.19.0 或之後版本中取得。
LINE for Android 目前不受影響,但近期內將發佈相關新聞。

LINE 團隊正積極排除此問題,造成不便敬請包涵!

新版 LINE Developers Console 上線

即日起,新版 LINE Developers Console 正式上線。

新版 console 修正數項問題並改善多項功能,提供更為順暢、可靠的使用者體驗,以下介紹新版 console 的功能重點:

# 經優化的設定分類

現在,每個 channel 的第一個表單皆為 Basic settings,表單包含核心設定選項。而第二個表單根據 channel 類型命名 (LINE Login、Messaging API,或 Clova skill),並包含與該類型相關的設定選項。

Screenshot of Basic settings and Messaging API tabs

# 輸入名稱以尋找 provider

開發者可於 provider 列表上方的搜尋欄位輸入名稱,輕鬆找到欲搜尋的 provider。

Screenshot of search field at top of provider list

# 於同一頁面管理各類型使用者

使用舊版 console 須於兩個不同的頁面中,管理 Admin、Member 與 Tester 等類型的使用者。現在起,只要在 Roles 表單中,便可搜尋並新增使用者。

Screenshot of Roles tab in channel information

新版 console 協助開發者更輕鬆地新增及管理 channel,LINE 團隊亦將持續為開發者提供更完善的使用者體驗。

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.

停止在 Messaging API channel 新增 LIFF app

LIFF v2 即將改以 LINE Login channel 為核心。此外,將全面停止開發者在 Messaging API channel 新增 LIFF app。強烈建議開發者改在 LINE Login channel 新增 LIFF app。

# 變更生效日期

2020 年 2 月

# 影響

Channel 類型 影響
LINE Login channel 未受影響。
Messaging API channel 變更後,將無法再在 Messaging API channel 新增 LIFF app。原本綁定 Messaging API channels 的 LIFF app 於變更後仍可使用。
請勿再在 Messaging API channel 新增 LIFF app

目前,開發者仍可在 Messaging API channel 新增 LIFF app,然而,基於以下限制,強烈建議開發者停止繼續在 Messaging API channel 新增 LIFF app:

  • Bot link 無法使用。
  • LIFF 延伸功能可能不受支援。
  • LIFF app 未來可能無法繼續使用。

在 LINE Login channel 新增的 LIFF app 並無以上限制,且可使用 LIFF v2 所有功能。

# 將 LIFF app 綁定至 LINE Login channel

為繼續使用原本綁定 Messaging API channel 的 LIFF app,請在 LINE Login channel 新增該 LIFF app。新增後,LINE Developers Console 將發佈新的 LIFF app ID。因此,請注意:

  • 使用 LIFF v2 的開發者,請改用 liff.init()所指定的 LIFF app ID。
  • LIFF 上線所使用的 LIFF URL(例如:line://app/1234567890-AbcdEfgh)將被變更。
請移除綁定 Messaging API channel 的 LIFF app

為避免混淆,在 LINE Login channel 新增 LIFF app 後,請刪除原本綁定 Messaging API channel 的 LIFF app。

Endpoint 網域名稱變更通知

部分 Messaging API endpoint 的網域名稱 (domain name) 由 api.line.me 變更為 api-data.line.me,本次變更不包含任何 maintenance。

# 變更網域名稱的 endpoint:

# 影響

使用以上 endpoint 的開發者,請於轉換期限前變更網域名稱。如造成任何不便,敬請見諒,感謝配合。

轉換期結束後,使用以上 endpoint 的舊網域名稱將會顯示 404 錯誤訊息。

# 轉換期間

即日起至 2020 年 4 月 30 日

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

最新 ID token verification endpoint 正式上線

當開發者的後端伺服器收到來自 LINE Login v2.1 或 LINE SDK 的 ID token,開發者需要驗證此 ID token 是否可靠。

過去開發者必須使用 JWT library (opens new window),或自行撰寫用以譯解和驗證的程式碼。

在最新 ID token verification endpoint 正式上線後,開發者只須將 HTTP request 發送至 verification endpoint,便可確認 ID token 是否可靠。

如欲了解如何驗證 ID token,請查看 Transfer ID token to back-end server

LIFF v2 正式上線

LINE Front-end Framework (LIFF) v2 為 LINE 運作 app 的平台。

請使用最新版 LIFF

LIFF v1 未來將被終止使用。

# 現在起,LIFF app 可於外部瀏覽器中執行

使用 LIFF v1,LIFF app 只能在 LINE app 瀏覽器中執行。使用 LIFF v2,LIFF app 則可於外部瀏覽器中執行。開發者可使用與一般 web 應用相同的開發環境進行 LIFF app 開發。

# 取得用戶資料與 email

由於與 LINE Login v2.1 的相容性已獲得改善,現在,開發者可從 LINE 平台取得用戶 ID 和 email address。LIFF app 可使用此數據,提供與用戶資料和發送電子郵件相關的功能。

此外,LIFF app 在外部瀏覽器中執行時,開發者仍可使用 LINE Login (網頁登入流程),這也代表即使 LIFF app 正在外部瀏覽器中執行,開發者也可使用相同的訊息。

# 讀取 QR code

開發者可使用 LINE QR code reader 取得用戶所讀取的字串。

# 取得 LIFF app 設定詳細資料

開發者可取得下列有關 LIFF app 設定的詳細資料:

  • 執行 LIFF app 的作業系統 (iOS / Android / 外部瀏覽器)
  • LIFF app 是否正在 app 內的瀏覽器中執行 (是 / 否)
  • 語言設定

如欲取得更多資料,請至 LINE Front-end Framework

最新 Messaging API endpoint 提供互動數據資料

最新 Messaging API endpoint 正式上線,提供詳細數據資料,協助開發者了解用戶與 LINE 官方帳號 (OA) 發送的訊息進行哪些互動。

此 endpoint 提供的數據資料,與 LINE Official Account manager (opens new window)Insight 表單所顯示的數據資料相同。

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.

LINE Developers News - 中文版即日起上線

即日起,LINE Developers News 將精選主題,為開發者提供中文新聞,與英文新聞 (opens new window)日文新聞 (opens new window)同步,讓開發者更快速、更輕鬆地掌握最新 LINE 開發相關訊息。

如欲將語言設定為中文,請於 LINE Developers 新聞網頁右下角的語言選單中,選取「繁體中文」,便可查看中文版新聞內容:

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 LINE Developers Console). Depending on the call, there are also other fields to fill in.

For now, this feature is only enabled for a small number of operations. We plan to increase the number in future releases to cover more Messaging API functionality.

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 the LINE Developers Console was not working as intended.

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

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

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

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

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.

LINE Developers 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 (opens new window) on GitHub on February 15, 2019.

Please send your questions about the LINE Platform to the Q&A (opens new window) 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 LINE Developers 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 LINE Developers 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 (opens new window) 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 LINE Developers Console. This 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 (opens new window)

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 (opens new window) 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 (opens new window) 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 LINE Developers Console functionality. Here, we'll take you through some of the key changes to the site.

# Changes in the LINE Developers 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 (opens new window)

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 LINE Developers 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 (opens new window) 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 (opens new window) 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 (opens new window) page or LINE Engineering Blog (opens new window).

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 (opens new window) 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 (opens new window) 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 (opens new window) 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 (opens new window). 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 (opens new window) specification which is an identity layer on top of OAuth 2.0.

Here are some of the key changes.

# ID tokens

With LINE Login 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 LINE Developers 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 (opens new window) to enable API features and configure settings. Those settings are now available on the "Channel settings" page of the LINE Developers 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 LINE Developers 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 (opens new window) and LINE Notify (opens new window) 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 (opens new window) 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 (opens new window) 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 (opens new window)

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 (opens new window) will be discontinued.)
  • The current API reference (opens new window) (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 (opens new window).

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 (opens new window) and LINE Developers Agreement (opens new window).

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

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

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

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

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.