News: Articles for #Messaging API
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.
[Updated] Make sure the provider name is correctnote Added on January 9, 2020
This specification change was scheduled to take place on January 9, 2020, but has been postponed to January 16, 2020.
Starting January 16, 2020, LINE Official Accounts using the Messaging API will display the provider name registered by the developer at the bottom of the profile.
Corporate LINE Official Accounts may also have personal names registered as provider names. Make sure that the correct name is registered. The provider name can be changed from the LINE Developers Console.
*The provider name is displayed in the red frame
mode property added to Messaging API webhook events
We've added the
modeproperty to all Messaging API webhook events.
modeproperty is necessary for the channel multiplexing feature (under development). Now, all existing webhook events contain
modeproperty's value can change to
standbyif the channel administrator starts using channel multiplexing. The value of
modenever automatically changes to
Learn more about the
modeproperty by reading about the Common properties of webhook events in the Messaging API reference.
Problem with channel statistics in console (resolved)
There was an issue with the Statistics tab for Messaging API channels on the LINE Developers console. Due to an inconsistency in how the system handled timezones, the tab appeared to show different data for certain days than the TSV file that you can generate by clicking Download as TSV.
This problem only affected users outside the JST timezone, and only affected the presentation of the data. No data was deleted or damaged. you'll be able to retrieve and display all data as normal.
Issue inception: November 26, 2019
Issue solved: December 18, 2019
The issue has now been resolved, so you may retrieve and display all data as normal. We apologize for any inconvenience this may have caused.
A stay event was added to beacon event
New property added to "sticker message" webhook event
We added a new
stickerResourceTypeproperty to the webhook event that notifies you when a sticker message is sent.
Use this property to see what type of sticker was sent (still image, animated sticker, sticker with sound, etc.).
Learn more from the Sticker section of the Messaging API reference.
Notice of domain name change for certain endpoints
The domain name of certain Messaging API endpoints has been changed from api.line.me to api-data.line.me. There is no maintenance associated with this.
If you are using the above endpoints, please change your domain during the transition period. We apologize for any inconvenience this may case. Thank you for your understanding.
Once the transition period ends, accessing an endpoint of the old domain will return a
Today - April 30, 2020
Endpoint for obtaining user statistics now available in Thailand (TH)
New Messaging API endpoint for friend statistics
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
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)
Issue with our servers.
All Messaging API endpoints (https://api.line.me/v2/bot/*).
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.