Skip to main content
GuidesAPI ReferenceSupport

The 8x8 LINE Channel

Welcome to the 8x8 integration for LINE. This documentation covers both LINE products available on the 8x8 Messaging Apps platform: the two-way LINE Official Account channel and the one-way LINE Official Notification channel.

Why Use LINE for Business?​

LINE is the most popular chat application in Japan, Thailand, and Taiwan. LINE Official Account is LINE's business messaging product. It lets a business hold the same kind of one-to-one conversation with a customer that the customer already has with their friends on LINE, and it is the only route to a LINE user for a business.

  • Friend-based reach: You exchange messages with users who have added your LINE Official Account as a friend, which means your audience has opted in by adding you.
  • In-app discoverability: Accounts that pass LINE's review receive a Verified account badge and appear in LINE in-app search results. Unverified accounts do not appear in search.
  • Two-way conversations: The LINE Official Account channel supports both inbound and outbound messages, so you can run support and service journeys, not just notifications.
  • One API across channels: LINE uses the same 8x8 Messaging Apps send endpoint and webhook envelope formats as SMS, WhatsApp, Viber, and RCS.

What is the 8x8 Integration for LINE?​

8x8 connects your LINE Official Account to the 8x8 Messaging Apps platform, so your application sends and receives LINE messages through the same API and the same webhook you already use for other channels.

8x8 is a LINE-registered Agency (AGP) partner and can provision and manage a LINE Official Account on your behalf. If you already own a LINE Official Account, 8x8 can connect that instead. Both routes are documented in Account Provisioning and Onboarding.

You work with LINE on 8x8 through the 8x8 Messaging Apps API: send and receive LINE messages programmatically from your own application, CRM, or backend system.

Two LINE Products on 8x8​

LINE appears twice in the 8x8 channel list, as two genuinely different products with different endpoints, different recipient keys, and different capabilities. Choose deliberately.

FeatureLINE Official AccountLINE Official Notification
Channel type valuelineLineNotification
DirectionInbound and outboundOutbound only
Recipient keyed byuser.channelUserId (LINE user ID)user.msisdn (phone number)
Send endpointPOST /api/v1/subaccounts/{subAccountId}/messagesPOST /api/v1/subaccounts/{subAccountId}/lon
TemplatesNot supportedRequired, and must be pre-approved by LINE
Text limit5,000 characters (LINE limit)500 characters per template
Content typesText, Image, Video, Audio, LocationText and Button, inside an approved template
Delivery statuses reportedAccepted, SentAccepted, Sent, Delivered

The last row is the one most likely to change your design. The line channel reports Accepted and Sent but not Delivered or Read, so you can confirm that a message was accepted by LINE but cannot confirm that the recipient's device received it. The LineNotification channel goes one step further and additionally reports Delivered. See LOA Delivery Receipts for details.

Key Takeaway: These are not two modes of one channel. They are two channels, each on its own 8x8 sub-account with its own bearer token, and they identify the recipient in incompatible ways. A phone number cannot be used to send on the line channel, and a LINE user ID cannot be used to send on LineNotification.

Where to Start​

For All Users (Start Here) Read the fundamentals first. LINE identifies recipients differently from every phone-number-based channel, and that difference shapes your data model.

For Business and Operations Users Learn what LINE requires before a single message can be sent, what information you have to supply, and how long it takes.

For Developers and Integrators Start with authentication and the send endpoint, then work through the payload catalogue and the webhook contract.