​

LINE Onboarding: Messaging API Channel to Working Two-Way Chat

​

1. Prerequisites — the Messaging API channel

1. A LINE Official Account. If you do not have one, create it in the LINE Official Account Manager.
2. A Messaging API channel on that account, created in the LINE Developers Console.

• Channel access token (long-lived) — from the channel’s Messaging API tab. This is the bearer token LINE accepts on outbound push calls.
• Channel secret — from the channel’s Basic settings tab. Orbit uses it to verify the x-line-signature header on inbound webhooks before any event reaches your handler.

​

2. Connect the channel to Orbit

1. Navigate to Channels → LINE → Connect.
2. Paste the channel access token and channel secret. Orbit validates the token at connect time — an expired or invalid token returns LINE_INVALID_TOKEN (401) instead of connecting.
3. Orbit stores both values encrypted at rest under your organization’s settings.channels.line and never echoes them back through any API response.
4. In the LINE Developers Console, set the channel’s Webhook URL to https://api.orbit.devotel.io/api/v1/webhooks/inbound/line and enable Use webhook. Every Orbit tenant shares this single URL — the LINE channel id (destination) on each inbound event is what resolves the receiving tenant (see §4).

​

3. Send — POST /api/v1/messages/line

curl -X POST https://api.orbit.devotel.io/api/v1/messages/line \
  -H "X-API-Key: dv_live_sk_..." \
  -H "Content-Type: application/json" \
  -d '{
    "to": "U4af4980629...",
    "body": "Welcome! Reply with a number to continue.",
    "type": "text"
  }'

import { Devotel } from '@devotel-orbit/node';

const orbit = new Devotel({ apiKey: process.env.ORBIT_API_KEY });

// Fully-typed per-channel method — prefer it over the generic send.
// LINE accepts up to 5 stacked messages per push.
const message = await orbit.messages.sendLine({
  to: 'U4af4980629...',
  messages: [
    { type: 'text', text: 'Welcome! Reply with a number to continue.' },
  ],
});

console.log(message.data.id);      // msg_line_abc123
console.log(message.data.status);  // 'queued'

from orbit_sdk import OrbitClient

client = OrbitClient.from_env()  # reads ORBIT_API_KEY

# The Python SDK has no typed send_line method — reach the channel
# endpoint through the client.request escape hatch (raw JSON returned).
message = client.request(
    "POST",
    "/messages/line",
    json_body={
        "to": "U4af4980629...",
        "body": "Welcome! Reply with a number to continue.",
        "type": "text",
    },
)

print(message["data"]["id"])       # msg_line_abc123
print(message["data"]["status"])   # 'queued'

​

4. Inbound — tenant resolution from destination

1. Read the untrusted payload’s destination and resolve the tenant that connected that channel id.
2. Verify the x-line-signature HMAC-SHA256 header against that tenant’s stored channel secret. Requests that fail verification are rejected before any webhook fires.
3. Normalize each message-type event into the canonical inbound envelope and forward it to the endpoint configured under Settings → Webhooks, signed with the Standard-Webhooks scheme.

{
  "id": "evt_9d4e2b8c1f",
  "type": "message.received",
  "created_at": "2026-09-02T08:31:12Z",
  "data": {
    "message_id": "msg_1n58gk",
    "channel": "line",
    "from": "U4af4980629...",
    "to": "1654385910",
    "body": "Store hours?",
    "provider_status": "inbound"
  }
}

​

5. Verify the loop end to end

1. From a LINE device, message your Official Account — confirm a message.received event lands on your webhook within seconds.
2. Reply through POST /messages/line using the sender’s U… id from that event — confirm the message arrives in the chat.
3. Confirm the message.delivered event arrives and that the message record in the dashboard moved through queued → delivered.

​

6. Rotation and retirement

​

7. Error reference

​

Compliance scope

​

Where to go next

• LINE channel page — message types, capability detail, pricing notes.
• Asia channels onboarding — LINE beside KakaoTalk, Viber, and WeChat.
• API recipes cookbook — the send → poll → webhook loop task by task, with curl and per-language SDK snippets.
• Inbound webhook debugging — tools for the receiver side on any channel.