As announced on October 6, 2020, January 18, 2021, and January 28, 2021, the following updates have been made to the LINE Platform, which is the source for webhook notifications for the Messaging API.
As announced on October 6, 2020 and January 18, 2021, we're planning these updates to the LINE platform, which is source for webhook notifications for the Messaging API. If you're using a webhook, confirm communication from the new environment during the transition period.
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.
After the transition, there may be changes to uppercase and lowercase letters in the field name of the Request header when sending a webhook from the LINE Platform. *1
Before transition
After transition
Header field name example
X-Line-Signature
x-line-signature
In addition, uppercase and lowercase letters may change without notice in the future as the LINE server is updated. The bot server that receives the webhook should handle the header field name without case distinction. *2
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 this table 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.
If you're using Messaging API webhooks, we recommend that you use one of these 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
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.
LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.
As announced on October 6, 2020, we're planning these updates to the LINE platform, which is source for webhook notifications for the Messaging API. If you're using a webhook, confirm communication from the new environment during the transition period.
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.
After the transition, there may be changes to uppercase and lowercase letters in the field name of the Request header when sending a webhook from the LINE Platform. *1
Before transition
After transition
Header field name example
X-Line-Signature
x-line-signature
In addition, uppercase and lowercase letters may change without notice in the future as the LINE server is updated. The bot server that receives the webhook should handle the header field name without case distinction. *2
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 this table 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.
If you're using Messaging API webhooks, we recommend that you use one of these 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
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.
LINE will continue to improve the quality of its services to its customers. Thank you for your understanding.
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.
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.
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.
LINE will continue to improve the quality of its services to prevent future outages. Thank you for your understanding.
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.
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.
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.
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.
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.
