LINE's Official Account Is Only Available in Three Countries — Here's What Teams Everywhere Else Do — UnifyPort
You’re running a customer support operation that needs to receive LINE messages. Maybe you’re a Singapore-based team serving customers in Thailand, a Vietnamese company with Japanese suppliers, or a Chinese cross-border operation managing conversations across Southeast Asia. LINE has over 200 million active users, and in several of your key markets, it’s the messaging app people actually use.
So you go to the LINE Developers portal to set up a webhook. You quickly learn that the Messaging API requires a LINE Official Account. You go to register one. And that’s where you discover that LINE’s verification process doesn’t accept applications from your country.
The three-country wall
LINE’s Official Account verification is currently restricted to businesses registered in three countries: Japan, Taiwan, and Thailand. If your business entity is incorporated anywhere else — Singapore, Vietnam, China, South Korea, the United States, Indonesia, the Philippines — LINE’s review team will not process your application.
This wasn’t always the case. LINE previously accepted applications from four countries, including Indonesia. The eligible list has narrowed, not expanded.
The restriction applies specifically to Verified Official Accounts — the tier that removes the 500-follower cap and grants access to the full Messaging API feature set. Unverified OAs are available to anyone, but they cap your follower count at 500, making them impractical for any real customer-facing use case.
Here’s the disconnect: LINE’s user base extends far beyond these three countries. Indonesian users alone account for tens of millions of LINE accounts. Overseas Chinese communities, Korean expats in Southeast Asia, global brands with regional operations — millions of LINE users exist in markets where the developer infrastructure to reach them doesn’t.
Four paths, evaluated
If you’re outside Japan, Taiwan, and Thailand and need to receive LINE messages, these are your realistic options.
Path A: Register a local entity in an eligible country
What it involves: Incorporate a subsidiary or branch office in Japan, Taiwan, or Thailand. Use that entity’s registration documents to apply for a Verified LINE Official Account.
Timeline: Company incorporation takes 2–8 weeks depending on the country. LINE’s OA verification adds up to 60 business days on top. Total: 3–5 months minimum.
Cost: $2,000–$10,000+ for incorporation fees, registered agent, and ongoing compliance. Annual maintenance adds $1,000–$3,000.
When it makes sense: You’re establishing a real operational presence in one of these markets — hiring locally, opening an office, running campaigns that need the official brand badge and broadcast features.
When it doesn’t: All you need is to receive inbound messages from LINE users. Incorporating a foreign entity to answer customer questions is infrastructure that doesn’t match the problem.
Path B: Work through a LINE partner agency
What it involves: Contract with a LINE-certified agency or BSP that already holds OA infrastructure. They register a sub-account on your behalf and pass messages through their system.
Timeline: 2–6 weeks for onboarding and setup.
Cost: Monthly platform fees ($200–$1,000+), often plus per-message fees. Pricing varies widely and typically scales with volume.
When it makes sense: You need outbound broadcast features — push notifications, rich menus, LINE-specific interactive content — and can’t get your own OA.
When it doesn’t: You only need inbound reception. You’re paying for an intermediary’s outbound infrastructure to solve a receive-only problem.
Path C: Use an Unverified Official Account
What it involves: Register an Unverified OA (available globally, no geographic restriction) and connect it to the Messaging API.
Timeline: Same-day setup.
Cost: Free.
The catch: A 500-follower hard cap. Once 500 LINE users have added your account, no new users can follow it. For any customer-facing operation with real traffic, you hit this ceiling within weeks — sometimes days.
When it makes sense: Internal tools, small closed groups, or proof-of-concept testing before committing to a larger investment.
When it doesn’t: Any production customer support or engagement use case.
Path D: Unofficial inbound interface
What it involves: Connect a LINE account — personal or business, any tier — to an unofficial inbound interface that delivers messages to your webhook without going through LINE’s OA registration process.
Timeline: Same-day. Account connection takes minutes; first webhook event arrives within the hour.
Cost: No per-message billing. No OA registration fees. No agency intermediary.
Geographic restriction: None. Works regardless of where your business is incorporated.
With UnifyPort, the LINE connection flow is:
- Create an account with
provider=lineandauth_mode=qrcode - Scan the QR code in the LINE app to authenticate
- Register your webhook endpoint with your
signing_secret - LINE messages arrive as standard
message.receivedevents:
{
"event": "message.received",
"account_id": "acct_4Lm9xQ",
"provider": "line",
"from": "U7b2e4a09f1c3...",
"text": "สินค้าพร้อมส่งไหมคะ",
"timestamp": 1750636800,
"message_id": "line_msg_a3f8d2"
}The payload is identical in shape to messages from WhatsApp, Telegram, Zalo, TikTok, and X — all arriving at the same endpoint, all signed with the same HMAC-SHA256 signature. Your backend handles LINE the same way it handles every other platform.
The decision matrix
| Local entity | Partner agency | Unverified OA | Unofficial inbound | |
|---|---|---|---|---|
| Geographic restriction | Must be in JP/TW/TH | Via agency’s presence | None | None |
| Setup time | 3–5 months | 2–6 weeks | Same day | Same day |
| Ongoing cost | $1K–3K/yr maintenance | $200–1K+/mo | Free | No per-message fees |
| Follower cap | None (verified) | None (via agency OA) | 500 | N/A |
| Outbound broadcast | Yes | Yes | Limited | Not the primary use |
| Inbound reception | Yes | Yes | Yes (to 500) | Yes |
For teams whose primary need is receiving LINE messages — routing them into a support queue, CRM, or AI agent pipeline — the bottom-right column is the path that matches the problem without requiring infrastructure built for a different one.
What this means in practice
The geographic restriction on LINE’s Official Account isn’t a bug or an oversight — it reflects LINE’s market strategy. LINE is a Japanese company with deep roots in Japan, Taiwan, and Thailand, and its business infrastructure is built around those three markets. For a team operating within one of them, the OA path is straightforward (if slow).
But for the growing number of teams outside these countries who serve customers inside them — a Singapore hub managing Thai support, a Chinese brand selling to Japanese consumers, a Vietnamese agency handling cross-border clients — the official path is a dead end that doesn’t open no matter how long you wait.
If inbound LINE messages are what you need, connect a LINE account to UnifyPort and start receiving events today. The OA registration process, if you decide to pursue it later for outbound features, can run in parallel without blocking your inbound pipeline.