# FAQ entries tagged #Message

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.

If a message is sent to a user ID that doesn't exist, this error will be returned with status code 400.

"message": "Failed to send messages"

Note that the user ID is a value issued for each provider. If you send a message with a user ID issued by another provider, it will be treated as if you sent the message to a user ID that doesn't exist.

For more information on user IDs, see What are the user ID, group ID, room ID, and one-on-one chat ID values?

The character count in a text message depends on the character type.

  • Alphabet/full-width characters: 1 character

  • Line break characters: 1 character per line break character (\n: 1 character, \r\n: 2 characters)

  • Emojis defined by Unicode and LINE

    • Emojis in Basic Multilingual Plane (for example, ☎): 1 character

    • Emojis on the supplementary plane that are represented using surrogate pairs: 2 characters

      This includes emojis defined by LINE and Unicode.

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 chat room or group 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.

For message count when you send a message to a user who doesn't receive the message, see If I send a message to a user who doesn't receive the message, is it still counted as one message?.

For more information on pricing, see Messaging API pricing.

Yes.

If multiple message objects are set in the request body when sending a message, the messages will be delivered in the order they are set from the top.

Message IDs are assigned a value that is unique throughout the Messaging API environment.

It doesn't mean that it's unique for each channel or message type, such as an image.