AgentSkyLINE guide
Register your Official Account
Enable the Messaging API for your LINE Official Account. In the LINE Developers Console, open the associated channel, copy its channel access token from Messaging API settings and its channel secret from Basic settings.
In Developer apps, select LINE and enter both credentials. API callers register platform line with credentials channel_access_token and channel_secret. Registration makes a read-only bot-info request to verify the token and obtain the Official Account's identity. It does not change the current webhook or prove that the supplied channel secret can receive events.
Configure the webhook
Copy setup.webhook_url to Messaging API → Webhook settings and enable Use webhook. Disable automatic replies that would duplicate the agent's response. AgentSky checks the raw webhook signature with the channel secret and requires the event destination to match the registered bot.
If this Official Account already serves another integration, import and verify its existing conversations before switching its webhook. Registration alone does not migrate users or replace the previous callback.
Connect and talk
Add the Official Account as a friend. Create a connection using platform line, the registered app ID and a session or webhook destination. Open the returned connect URL and send its LINK code in LINE. The open-chat shortcut is intended for the LINE mobile app; on desktop, copy the code into your chat manually. A verified incoming message changes the connection from PENDING to CONNECTED.
Use thread_id from signed message.received events unchanged for replies. Direct messages, groups and rooms keep separate app-scoped conversations. A shared conversation does not establish every participant's identity or authorization in your product; the webhook consumer must check the actual sender.
Message behavior and recovery
Text replies preserve links and split long content to fit LINE's message limits. Incoming images, audio, video and files are downloaded through the authenticated LINE content API. Native file sending and edits of sent messages are not supported; integrations should present accessible file links and send corrections as new messages. Push delivery is subject to the Official Account's messaging quota.
A rejected token fails registration. A mismatched secret or destination rejects the webhook without connecting a conversation. If the open-chat shortcut fails, use the displayed code in LINE. An expired code requires a new connection. After an uncertain send, check the conversation before retrying to avoid duplicate messages.