LINE Service Messages vs Messaging API: Which Should Your MINI App Use?
LINE service messages and Messaging API messages solve different jobs. Use a service message when a verified LINE MINI App must confirm or follow up on an action completed inside the app, such as a reservation or shipment. Use the Messaging API when a LINE Official Account needs conversational replies, flexible push messages, or broadcasts. One is not a more powerful version of the other.
Key takeaways
- Service messages are transactional notifications tied to a user action in a LINE MINI App; advertisements, coupons, product promotion, and unrelated event notices are prohibited.
- The Messaging API belongs to a LINE Official Account and supports reply, push, multicast, narrowcast, and broadcast patterns with flexible message objects.
- Production service messages require a verified MINI App, a reviewed template, and a user-bound service notification token; Messaging API messages use channel credentials and recipient or reply tokens.
- Service messages appear in the regional LINE MINI App notice chat and can reach a MINI App user who has not added the related Official Account as a friend.
- If you need both transactional updates and open-ended support, keep the two message paths separate and join them with your own reservation or order ID.
LINE service messages vs Messaging API messages
The official service message guide defines service messages as confirmations or responses to an action a user took in a LINE MINI App. The official Messaging API guide describes messages sent by a bot attached to a LINE Official Account. That product boundary is more important than the similarity of the word “message.”
| Decision point | LINE MINI App service message | LINE Messaging API message |
|---|---|---|
| Primary purpose | Confirm, report the result of, or remind the user about an action completed in the MINI App | Reply to users or send one-to-one and one-to-many messages from an Official Account |
| Trigger | A qualifying user action inside the MINI App | A user event for reply messages, or an application decision for push, multicast, narrowcast, or broadcast |
| Recipient | The user bound to a service notification token | A user, group, multi-person chat, audience, or Official Account friends, depending on the send method |
| Message design | A LINE-provided, reviewed service-message template with approved variables and links | Text, image, video, audio, sticker, location, imagemap, template, Flex, and other supported message objects |
| Production gate | Verified MINI App plus an approved template | Messaging API channel connected to a LINE Official Account, subject to the selected send method and recipient rules |
| Chat room | Regional MINI App notice chat, such as “LINE MINI App Notice” in Thailand | The chat with the LINE Official Account |
| Volume boundary | Normally up to five messages for one qualifying action; the approved use case can set a different limit | Monthly message allowance and endpoint limits under the applicable Official Account plan |
| Pricing model | LINE describes the MINI App service-message feature as free | Messaging API message counts and plan pricing depend on the market and Official Account plan |
Choose a service message for an action-linked transaction
Choose the Service Message API when the notification would not exist without a specific MINI App action. Typical official examples include reservation confirmation, check-in completion, shipment completion, and a reminder for a reservation or purchased ticket.
The server first exchanges a LIFF access token at POST /message/v3/notifier/token, then sends an approved template with POST /message/v3/notifier/send?target=service. A service notification token is bound to one user and the action flow. It is not a permanent LINE user address or a general push credential.
The content boundary is strict. Discounts, shopping rewards, new-product announcements, coupons, promotions, and general event notices do not become valid service messages merely because the MINI App is verified. If the operation needs template preparation, use the service-message template review checklist. If the implementation already exists but fails, use the Service Message API error runbook.
Choose Messaging API for Official Account conversation and outreach
Choose the Messaging API when the sender should be the LINE Official Account. Reply messages respond to a user message or action with a reply token. Push messages target an eligible user, group, or multi-person chat. Multicast, narrowcast, and broadcast cover larger recipient sets under their respective rules.
This path supports a broader set of message objects and is designed for bot conversations, support, and Official Account communication. It also follows Official Account friendship, recipient, monthly allowance, pricing, and rate-limit rules. A Messaging API push message is therefore not a substitute for the special ability of a service message to notify a MINI App user who has not added the Official Account as a friend.
A practical decision tree
- Did the user complete a reservation, order, queue, check-in, or similar action inside your MINI App? If yes, continue evaluating a service message.
- Is the notification only a confirmation, action result, or reminder for that same action? If no, do not use a service message.
- Is the MINI App verified for production and is the exact template approved? If yes, use the Service Message API and preserve the renewed notification token after each send.
- Should the message come from your Official Account, reply to a chat, or reach an audience? Use the Messaging API and select reply, push, multicast, narrowcast, or broadcast based on the recipient model.
- Will users ask free-form support questions after the notification? Design a separate conversation intake path, then correlate it with the transaction in your own system.
Do not send the same operational update through both paths by default. Duplicate notifications confuse users and make delivery, consent, and support ownership harder to audit.
Where UnifyPort fits
UnifyPort does not issue LINE service notification tokens, approve MINI App templates, grant verified status, create an Official Account, or replace the Messaging API’s official outbound features. Use LINE’s official APIs for those jobs.
UnifyPort fits a separate requirement: receiving ordinary customer messages from a connected LINE account and delivering supported messages as normalized message.received events. If a webhook endpoint has a signing_secret, deliveries include X-Device-Timestamp and X-Device-Signature; verify the HMAC-SHA256 signature against the raw body before routing a conversation.
That separation is useful when a service message confirms a reservation and the customer later starts an ordinary support chat. Store the reservation ID in your application, then associate the support conversation without treating the service notification token as a chat identity. Review the LINE authorization guide and the provider message-support matrix before relying on any send or receive capability.
Limitations and trade-offs
The official Service Message API is the correct and only path for platform-native MINI App service messages. An unofficial interface cannot change verification status, approve a template, expand the action-linked content policy, or increase the approved message count.
The Messaging API is the better official choice for rich Official Account conversations and audience messaging, but it brings the recipient, quota, and pricing model of an Official Account. UnifyPort’s ordinary-account message path is useful for supported customer conversations; it does not turn those conversations into MINI App service messages or grant Official Account audience features.
FAQ
What is a LINE service message?
A LINE service message is a transactional notification from a LINE MINI App that confirms, reports the result of, or reminds a user about an action completed in that MINI App. Production use requires a verified MINI App and an approved template.
Is a LINE service message the same as a push message?
No. A service message uses a user-bound service notification token and a reviewed MINI App template. A Messaging API push message comes from a LINE Official Account and follows its recipient, quota, and pricing rules.
Do users need to add an Official Account to receive a service message?
No. LINE states that a service message can reach a MINI App user even if that user has not added the related LINE Official Account as a friend. The message appears in the regional MINI App notice chat.
Can service messages contain promotions or coupons?
No. LINE prohibits advertisements and event notifications, including discounts, rewards, new products, coupons, and promotions. Use an eligible Official Account messaging method for marketing, subject to its own rules.
Can one product use both APIs?
Yes. Use service messages for approved action-linked MINI App updates and the Messaging API for Official Account conversations or audience messaging. Keep credentials and message state separate, and correlate both paths with your own business ID.
Next step
Start with LINE’s official service-message decision and implementation guide. If your separate requirement is ordinary LINE customer-message intake, verify the current boundary in UnifyPort’s provider message-support matrix.
Sources
Official LINE sources checked on August 7, 2026: