How it's actually built, in plain terms
You don't need to code to understand this — but knowing the pieces helps you scope a project. Here's what a custom LINE build is made of.
The building blocks
Messaging API
The engine behind a bot — it receives what users send and sends replies, pushes, and broadcasts.
Webhook
A public address on our server that LINE notifies whenever a user acts. It's what makes a bot react in real time.
Rich menu & Flex
The rich UI — a tappable menu docked in the chat, and designed message cards beyond the console templates.
LIFF
A web app that runs inside LINE — forms, booking, member cards — that already knows who the LINE user is.
LINE Login
Sign-in with LINE for a website or app outside the chat (OAuth 2.0 + a verified identity token).
One concept worth knowing: Provider & Channel
Everything sits under a Provider (your company), which holds Channels — one per feature (Messaging API, LINE Login, LIFF). One OA = one Messaging API channel. Gotcha: a user has a different ID per provider, so channels that must share a user identity belong under one provider.
A typical build path
- 1Create the Messaging API channel (the bot) + a webhook
- 2Add a rich menu and Flex messages for the UI
- 3Add a LIFF app for forms / booking / loyalty
- 4Integrate your systems (POS / CRM / payment)
None of this needs a Verified or Premium account to build or demo — the account tier is about public presence, not developer access.