​

LINE

​

Send a message

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...",
    "type": "text",
    "body": "Welcome! Reply with a number to continue."
  }'

​

Request body

​

Response

{
  "data": {
    "id": "msg_line_abc123",
    "status": "queued",
    "channel": "line"
  },
  "meta": {
    "request_id": "req_xyz789",
    "timestamp": "2026-06-08T00:00:00Z"
  }
}

​

Capabilities

• Message types — text, image, video, audio, location, sticker, plus template (buttons / confirm / carousel) and flex (fully custom Flex Message layouts).
• User, group, and room targeting — push to a user (U…), group (C…), or room (R…) id surfaced by an inbound event.
• Inbound webhooks — user messages, follows, joins, and postbacks are POSTed to your registered webhook endpoint with the standard Orbit inbound envelope (channel: "line").
• Media re-hosting — inbound image / video / audio / file content is downloaded from api-data.line.me and re-hosted on Orbit storage, so attachment URLs stay reachable after LINE’s short-lived content URL expires.
• Signature verification — every inbound request is verified against the connected channel’s channel_secret (HMAC-SHA256, x-line-signature header) before it reaches your webhook.

​

Rate limits

​

Onboarding flow

1. In the LINE Developers Console, create (or open) a Messaging API channel for your LINE Official Account.
2. From the channel’s Messaging API tab, copy the Channel access token (long-lived) and from the Basic settings tab copy the Channel secret.
3. In the Orbit dashboard, navigate to Channels → LINE → Connect and paste both values. Orbit stores them encrypted at rest (enc:v1: envelope) under your organization’s settings.channels.line and never echoes them back through any API response.
4. Set the channel’s Webhook URL in the LINE Developers Console to https://api.orbit.devotel.io/api/v1/webhooks/inbound/line and enable Use webhook. Orbit identifies the receiving tenant from the LINE channel id (destination) on each event, so all tenants share this single URL.

​

Credential handling — your responsibility

• Never commit a channel access token or channel secret to git, public or private.
• Rotate immediately from the LINE Developers Console if you suspect exposure, then re-paste the new values in Orbit — conversation history is keyed by channel id, not by the token, so it is preserved across rotation.
• Scope each environment to its own LINE channel (dev / staging / production) so a leaked dev credential cannot reach customer conversations.

​

Inbound webhook routing

1. Reads the destination (LINE channel id) from the untrusted payload and resolves the owning tenant.
2. Verifies the x-line-signature HMAC-SHA256 header against that tenant’s stored channel_secret.
3. Normalizes each LINE event into the standard inbound envelope and forwards it to the webhook endpoint configured under Settings → Webhooks, signed with the Standard-Webhooks scheme used across Orbit.

​

Common errors

​

Pricing