News: Articles for #Messaging API

  • 2019/02/19

    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 official account management tools. 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 official account management tools, 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.

  • 2019/01/17

    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:

  • 2019/01/15

    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.

  • 2018/12/18

    Specification change for the Messaging API

    The image component and icon component

    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.

  • 2018/11/27

    [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.

  • 2018/11/15

    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:

  • 2018/11/14

    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.

  • 2018/11/09

    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.

  • 2018/11/08

    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 messages in the Messaging API reference.

  • 2018/10/24

    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.