News: Articles for #Messaging API

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

  • 2018/10/03

    The scheme of the picture URL returned when getting a user profile has been changed

    Now we support https as the scheme of the pictureUrl property. The response to the GET https://api.line.me/v2/bot/profile/{userId} request includes this property.

  • 2018/09/27

    [Update] Discontinuation of the long-lived channel access token

    We'd like to inform you of the change in the discontinuation of the long-lived channel access token that we announced in August.

    We have concluded that discontinuing the long-lived channel access token by November can cause difficulty to many developers. Therefore, we will continue to support the long-lived channel access token and find alternative ways in the future that will not affect our developers.

  • 2018/09/19

    Default rich menu can now be configured with the Messaging API

    Now you can configure the default rich menu with the Messaging API.

    Both default rich menus created using LINE@ Manager and the Messaging API are supported and can be used at the same time.

    For more information on how to use the rich menu features, see the following pages.

  • 2018/09/11

    More stickers are available for your bot

    We have increased the number of sticker types available for bots from 342 to 462. You can create a smarter, more expressive bot with various new stickers.

    For more information, see Sticker message and the sticker list.