Skip to main content

LINE

The current LINE profile accepts text Messaging API events through a signed webhook and sends text with Push API using the configured version 2.1 Channel access token. It does not use the short-lived webhook reply_token as its send credential; the recipient must be eligible for push messaging. Native media admission is not provided by this profile.

What You Need​

  • a LINE Messaging API Channel;
  • a version 2.1 Channel access token;
  • the Channel secret;
  • optional Bot User ID; and
  • a public HTTPS route to the Anyy Gateway.

Refer to the current LINE Messaging API reference while configuring the Channel.

Connect in Dashboard​

  1. Open Dashboard → Channel → Add.
  2. Choose LINE; the default entry uses Messaging API webhook.
  3. Enter the Channel access token and Channel secret.
  4. Add the Bot User ID only when you need explicit identity matching.
  5. Save the credentials, then use the CLI wizard for policy changes.
  6. Register and enable the webhook URL in the LINE Developers Console.

Enable the shared listener and HTTPS proxy using Messaging Platforms. The callback path is:

/channels/line/ACCOUNT_ID/webhook

The default account ID is line.

Access Policies​

Direct messages default to open and support open, allowlist, or disabled. Group messages default to mention and support mention, open, allowlist, or disabled.

Sender pairing is not available for LINE. Change policy by choosing LINE in the interactive anyy setup channel wizard. The Dashboard form lacks policy inputs, and current setup actions do not edit LINE allowlist entries. An empty/non-matching list denies access; consult the shared setup limits.

Verify the Connection​

anyy channel doctor line
anyy channel reload

Use the LINE console's webhook verification, then test a direct message and a group mention.

Verify signatures through the public proxy

The Channel secret validates the exact webhook body. Configure the reverse proxy so it forwards the body unchanged to Anyy.

Troubleshooting​

ProblemCheck
Console webhook test failsPublic HTTPS reachability and exact account path
Signature is rejectedChannel secret and unchanged request body
Receive works but send failsVersion 2.1 access token and Channel availability
Direct message ignoredDM policy and allowlist
Group message ignoredGroup policy, allowlist, and explicit mention