In Chats mode, click on a rich menu from the Rich Menu pane located on the bottom right to activate it.
In Chats mode, click on a rich menu from the Rich Menu pane located on the bottom right to activate it.
Check if you have included "http://" or "https://" in the URL. The link must be in the same URL format as used on browsers.
Message actions will work normally when added to the chat in Chats mode.
The actual LINE chatbot only accepts URLs starting with "https://" to ensure security. LINE Bot Designer doesn't have this limitation to encourage the creation of any chatbot prototype.
The company name displayed on the bottom of the profile page is your Provider name. You can change your Provider name by following these steps:
For Certified providers (Certified providers have a certified provider badge before their company name)
You need to submit an application to LINE, so contact your sales representative.
For non-Certified providers
From the LINE Developers Console, select provider, click Settings, and from the Provider settings, and click the Edit button under Provider name.
*It will take some time before the change of provider name is reflected on your profile page.
See The number of channels that can be created in the LINE Developers Console documentation.
You can find your Channel ID on the LINE Official Account Manager (opens new window) or the LINE Developers Console.
LINE Official Account Manager (requires Admin role):
Select account from accounts list and click Settings in the top-right corner of the page. Click Messaging API from the side menu, and you will see your Channel ID next to Channel Info.
LINE Developers Console:
From the LINE Developers Console, select provider, and then select channel. You can find your Channel ID under Basic settings.
You can find your Provider ID on the LINE Developers Console.
If you have Provider Admin role:
From the LINE Developers Console, select provider and then click Settings. You can find your Provider ID under Provider settings.
If you don't have Provider Admin role:
From the LINE Developers Console, select provider. From the page displayed, you will see your Provider ID in the segment after /provider/
in the URL.
There is no technical support desk for individual developers. See Documentation for information on the development process and specifications of the LINE APIs. For questions and advice regarding development, see the voluntary Q&A (opens new window) in the LINE Developers Community.
If you are a corporate customer and need technical support for LINE APIs, contact our Technology Partners (opens new window) for technical support. Any inquiry regarding the LINE APIs should be through our Technology partners.
To report a problem encountered on the LINE Platform or make a request for improvement, contact us using the help center's Inquiry form (opens new window). Note that we may not be able to respond to all inquiries.
If you need technical support, see How do I contact technical support for inquiring about LINE APIs? in the FAQ.
In the LIFF browser and LINE's in-app browser, the user's social login with google account isn't allowed. This is because Google's OAuth 2.0 Policies (opens new window) disallow authorization requests from WebView to Google.
Therefore, when the user tries social login with google account in the LIFF browser or LINE's in-app browser, an error with a status code 403
and an error code disallowed_useragent
(opens new window) will be displayed.
You can use LINE Profile+ to get a user's phone number. For more information, see LINE Profile+ scopes in the Options for corporate customers documentation.
LINE Profile+ is only available to corporate users who have completed certain applications. If you wish you use LINE Profile+, contact your sales representative or contact our Sales partners (opens new window).
About the user ID issued by a certain provider, in the case that the corresponding LINE account is deleted, the same user ID won't be reused for other LINE accounts within the provider.
For more information on user IDs, see What are the user ID, group ID, room ID, and one-on-one chat ID values?
User IDs are issued by each channel provider. Once a user ID (userId) is issued for a specific provider, it won't change unless the user deletes their LINE account.
The user ID won't change even if the user transfers their LINE account to another device.
If a user deletes their LINE account and then re-creates a LINE account with the same phone number, the user ID will change.
For more information on user IDs, see What are the user ID, group ID, room ID, and one-on-one chat ID values?
The user ID used by the LINE Platform identifies a user and has the following characteristics:
The value is generated by the LINE Platform, not by a user. This is different from the LINE ID on LINE used to search for friends.
Different user IDs are generated based on the provider of the channel. As long as channels have the same provider, regardless of whether the channel is for LINE Login or Messaging API, the same user ID is used for the users of the channels.
The user ID value is a string that matches the regular expression, U[0-9a-f]{32}
.
The group ID used for group chats and the room ID used for multi-person chats are values generated by the LINE Platform to identify group chats and multi-person chats.
The group ID is a string that matches the regular expression, C[0-9a-f]{32}
, and the room ID is a string that matches the regular expression, R[0-9a-f]{32}
.
In a LINE Front-end Framework (LIFF) app, the one-on-one chat ID (utou ID) is used to identify a one-on-one chat in addition to the three types of IDs mentioned above.
The one-on-one chat ID value is a string that matches the regular expression, UU[0-9a-f]{128}
.
You can check the current status of a LINE API outage using these methods:
General LINE SDK users cannot use restricted API resources such as Graph and User Message APIs. Currently those resources are LINE internal use only.
You can download the LINE SDK from the LINE API SDKs page.
LINE uses Open Graph Protocol tags from websites to generate URL previews.
The three OGP tags used by LINE:
# | Open Graph Protocol tag | Example |
---|---|---|
1 | og:title | <meta property="og:title" content="LINE : Free Calls & Messages"> |
2 | og:description | <meta property="og:description" content="LINE is a new communication app"> |
3 | og:image | <meta property="og:image" content="http://static.naver.jp/line_lp/img/ogp.png"> |
Example of URL preview:
Even if you don't configure OGP tags, any text or image within the URL will be automatically retrieved to generate a URL preview.
For example, for the Title, if there is no available information in og:title
, the text within the title tag will be displayed. Likewise, for the Summary, if there is no available information in og:description
, the text within either the description tag or the body will be displayed (If there is no retrievable information, nothing will be displayed in the preview).
LINE uses only the three OGP tags listed above. URL previews will not include information contained in any other OGP tags.
A cache-deletion tool (opens new window) for deleting the LINE server side cache of your URL preview is now available.
The behavior depends on the specifications of the OS, such as Android or iOS.
This isn't controlled by the LINE app.
The supported browsers are Google Chrome, Safari, and Microsoft Edge.
Internet Explorer isn't supported.
Auto login can be used in these situations. You don't need to perform any special configurations when implementing LINE Login into your web app to use Auto login.
iOS
Android
Auto login isn't supported for devices other than iOS and Android devices, devices where LINE isn't installed, and in browsers other than the Safari browser for iOS.
Also, we use iOS's Universal links (opens new window) and Android's App Links (opens new window) features to perform auto login on external browsers. Check the official documentation for each OS for information on concepts such as how the dialog is displayed when using these features, the OS requirements for using these features, and how to disable these features.
For more information, see Auto login in the LINE Login documentation.
Auto login is enabled when accessing a web app that incorporates LINE Login with PKCE implementation from the Yahoo! Japan app. For more information on PKCE support for LINE Login, see PKCE support for LINE Login in the LINE Login documentation.
NLChannelGatewayErrorDomain
errors (for example, NLChannelGatewayErrorDomain Error 102
) can occur if there are incorrect or missing settings in the LINE Developers Console.
If your iOS application is getting this error, confirm the following items:
To delete the bot, you need to delete your LINE Official Account.
Currently, you can't get the list of group chats and multi-person chats that your LINE Official Account is participating in.
Currently, there is no function to switch the language of messages or rich menus based on the user's language.
Use the Get profile endpoint to get the user's language, and then send messages or set up a per-user rich menu based on the user's language.
If you send a message specifying a user who has blocked the LINE Official Account or a user who deleted their account, no error will occur and status code 200 will be returned as a response.
In this case, no message will be sent to the user.
When you get content, the file format of the binary data returned in the response is indicated in the Content-Type
(opens new window) header of the response.
By checking the value of the Content-Type
header, you can find out the file format of the content. Examples of file format indicated by the Content-Type
header are as follows:
Content sent by users | Content-Type header example |
---|---|
Image | image/jpeg |
Video | video/mp4 |
Audio | audio/x-m4a |
File | text/plain |
With the Get group chat summary API, you can get the name, and URL of the icon of the group chat that the LINE Official Account is participating in.
Characters in a text are counted in UTF-16 code units (16-bit). Characters expressed in multiple code units, such as some kanji characters and Unicode emojis, are counted as multiple characters instead of one character.
However, some properties are counted in grapheme cluster (opens new window) units rather than UTF-16 code units. For more information, see Counting characters in a text in the Messaging API documentation.
Also, unlike Unicode emojis, LINE emojis provided by LINE are internally converted to the alternative text (e.g., (love)
), so they're counted by the number of characters in the alternative text.
Examples of counting the number of characters in UTF-16 code units are as follows:
Character | UTF-16 encoded value | Number of code units | Number of characters |
---|---|---|---|
a | 0061 | 1 | 1 character |
あ | 3042 | 1 | 1 character |
\n | 000A | 1 | 1 character |
邊 | 908A | 1 | 1 character |
𠀋 | D840 DC0B | 2 | 2 characters |
👋 | D83D DC4B | 2 | 2 characters |
👋🏻 | D83D DC4B D83C DFFB | 4 | 4 characters |
If you specify a user who doesn't actually receive the message, such as a user ID that blocked the LINE Official Account or a user ID that doesn't exist, the message won't be counted even if you call the API for sending the message.
The number of messages is counted by the number of people to whom the message was sent. In this example, if there are five people in the group chat or multi-person chat where you sent the message, the number of messages counted is five. The number of message objects specified in a single request doesn't affect the number of messages sent.
For message count when you send a message to a user who doesn't receive the message, see If I send a message to a user who doesn't receive the message, is it still counted as one message?.
For more information on pricing, see Messaging API pricing.
The order in which messages are displayed depends on how the messages are sent.
If endpoints used for sending messages are executed multiple times, the order in which the endpoints are executed and the order in which the messages will be displayed won't be necessarily the same.
If an endpoint for sending messages is executed once and multiple messages are specified in the request body, the messages will be displayed in the order specified in the request body.
Yes.
If multiple message objects are set in the request body when sending a message, the messages will be delivered in the order they are set from the top.
Message IDs are assigned a value that is unique throughout the Messaging API environment.
It doesn't mean that it's unique for each channel or message type, such as an image.
We don't disclose IP addresses.
We prevent unauthorized requests through SSL communication and Verifying signatures included in the webhook.
Your account may not have been set up to allow webhooks. To allow webhooks, enable Use webhook on the Messaging API tab of your channel settings on the LINE Developers Console.
End users can't save on Keep or forward videos sent from a LINE Official Account.
It's possible that Allow bot to join group chats setting is disabled on your LINE Official Account, or that another LINE Official Account has already joined the group chat or multi-person chat you invited.
For more information, see Adding the LINE Official Account to a group chat or multi-person chat in the Messaging API documentation.
Depending response settings on the LINE Official Account Manager, the LINE Official Account will automatically send replies.
Click Edit in Auto-reply messages on the Messaging API tab of your channel settings on the LINE Developers Console to access LINE Official Account Manager and check Response setting.
LINE Official Account will automatically send replies in these cases:
The iPad that created the LINE account or the iPad that took over the LINE account can display rich menus.
Other iPads can't display rich menus.
You can check the LINE settings screen to see if your iPad can display rich menus.
If Delete Account appears in Settings > Accounts, the iPad can display rich menus.
If Logout appears in Settings > Accounts, the iPad can't display rich menus.
Yes, adding buttons is easy for both PC and mobile web pages.
After selecting a button type and language, copy the code and paste it where you want the button to be added on the website. For detailed steps, see the Installation guide.
You can see the total number of shares, added friends, and likes.
LINE Share button: If you turn on the share counter when you add the LINE Share button, the number of shares will appear along with the button.
Add friend button: You can set the Add friend button with a counter that shows the number of added friends.
Like button: The number of likes will appear regardless of the button type you use.
We currently don't offer statistics based on dates, age, or gender.
Currently, we don't offer support by phone. If you have any questions, contact us.
The Add friend button can't be used to add LINE official accounts that have been blocked by/hidden from the LINE app, or if the LINE official account has already reached the maximum number of friends.
To set the Add friend button, you need a LINE official account ID. For details about creating a LINE official account, see the LINE Official Account Help page (opens new window).
Yes, you can delete LINE official accounts from your friend list in the LINE app.
There are currently issues with the "Like" and "Add friend" buttons not working properly due to the Safari browser's policy changes. This issue is occurring with similar services as well, and not just with LINE Social Plugins.
We are closely keeping track of this issue so that it can be resolved as soon as possible.
However, note that the following configuration will allow you to use the "Add Friend" button in the Safari browser.
[PC Safari setting]
Depending on the browser policy, the Social Plugins' "Like" button may not work on the mobile version of the browser. This is a problem not only for LINE Social Plugins, but also for all similar services, and it can be solved by changing the settings of the mobile app.
[Chrome settings]
[Safari settings]
Use of the LINE Share button is prohibited on websites that lead to illegal products/services, adult/excessively violent content, or spam sites. Refer to the guidelines for details.
If you want to add the LINE Share button to native apps, refer to the Using LINE features with the LINE URL scheme page, not the LINE Social Plugins page.
There is no feature for viewing the history of the websites you've shared.
The LINE Share button lets you share URLs and text. You can share the URL of a website with photos or videos, but you can't share photos or videos directly.
Yes, you can use a custom icon that you made for the LINE Share button. For information on how to set your own button icon, see the Using custom icons.
When designing your button icon, make sure to refer to the design guide.
Yes, the LINE Share browser extension makes sharing selected text easy. After installing the extension on the Chrome or Whale browser, you can select text and quickly share it with the LINE Share feature.
Download the LINE Share extension for Chrome here (opens new window).
Download the LINE Share extension for Whale here (opens new window).
Content appears in the Keep Memo chat room only when you share it from a mobile device and select Keep Memo.
If you share content from a PC and select Keep, that content is saved in Keep and not in the Keep Memo chat room.
• To check saved content on LINE for PC: Click the Keep icon at the top left of LINE for PC.
• To check saved content on your smartphone: From the Home tab on LINE, tap your profile at the top of the screen > Keep.
A "blocked by CORS policy" error message may appear and the share counter API may not work in some cases. If you see this error, it means the API is restricted due to the same-origin policy, which is meant to prevent other origin resources on the internet from being accessed.
When using a custom icon, a server-side request is required for the share counter API to work.
If you have any questions about this or any other error, contact us (opens new window).
It's possible the character encoding is incorrect. Check to make sure that you shared percent-encoded text with UTF-8 character encoding.