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.
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.
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.
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.
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.
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}.
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.
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
Auto login can be used when accessing a web app where LINE Login v2.0 or v2.1 is implemented using LINE's in-app browser or the Safari browser.
Android
Auto login can be used when accessing a web app where LINE Login v2.0 or v2.1 is implemented using LINE's in-app browser or external browsers such as Chrome.
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.
About automatic login from the Yahoo! JAPAN app
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:
The iOS bundle ID is registered on the LINE Login tab of your channel settings on the LINE Developers Console
The iOS universal link is registered on the LINE Login tab of your channel settings on the LINE Developers Console
The LINE account that you are using to log in with is registered in the Roles section of the LINE Developers Console
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.
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:
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.
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:
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.
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.
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.
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.
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:
If Greeting message is set to Enabled, it will automatically send replies when user adds your LINE Official Account as a friend.
If Auto-response is set to Enabled, it will automatically send replies according to the preset conditions.
If Chat is set to On, depending on the Chat response method setting, it may automatically send replies.
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.
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.
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.
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]
Mobile device settings > Select Chrome app > Set Chrome as default browser app
For iOS, go to settings > Select Chrome app > Allow Cross-site tracking
Launch the Chrome app > Select the kebab menu (three-dot icon) next to the omnibox (address bar) > select settings > select content settings (iOS) or site settings (Android) > Turn off Pop-up blocker
[Safari settings]
Mobile device settings > Select Safari app > Set Safari as default browser
For iOS, go to Settings > Select Safari App > Allow Cross-site Tracking
Mobile device settings > Select Safari app > Turn off Pop-up blocker
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.
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.
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.
