Use Multiple Tools With One LINE Official Account: Token and Webhook Checklist
Yes, one LINE Official Account can use multiple tools through its linked Messaging API channel. The tools do not get isolated channels, though: they share channel access-token limits, a single webhook URL, API rate limits, and feature-specific quotas. Before adding a tool, decide who owns inbound events, which token type each tool uses, and how shared limits will be monitored.
Key takeaways
- A LINE Official Account can link to only one Messaging API channel, even when several tools call the API.
- Only one webhook URL can be configured, so two tools cannot independently receive the same LINE webhook directly.
- Reissuing the single long-lived channel access token disables the previous one; other token types have different limits.
- Rate limits and quotas are shared at channel level, so one tool can affect another.
- If several systems need inbound events, use one verified receiver and fan out events internally.
Can multiple tools use one LINE Official Account?
LINE’s July 23, 2026 developer guidance confirms that multiple tools can call the Messaging API through the channel linked to one LINE Official Account. A common setup might combine a campaign sender, a rich-menu manager, and a customer-support system.
The important boundary is ownership. Enabling the Messaging API creates one channel for the Official Account, and all connected tools operate inside that shared boundary. Adding a tool is therefore not the same as creating an isolated integration.
| Shared resource | Official constraint | Operational consequence |
|---|---|---|
| Messaging API channel | One channel linked to the Official Account | Tools share settings and limits |
| Webhook URL | One URL per channel | Choose one inbound owner or an internal fan-out layer |
| API rate limits | Applied per endpoint and per channel | Aggregate traffic across all tools |
| Feature quotas | Message, rich-menu, audience, and statistics limits can be channel-wide | Reserve capacity and assign ownership |
This is different from LINE Rich Menu Insights, which are an analytics surface, and from a LINE MCP tool layer, which gives an agent actions but does not become a durable inbox.
Choose channel access tokens without disabling another tool
LINE currently documents four channel access-token types. Record the type, owner, expiry, and revocation procedure for every tool before connecting it.
| Token type | Validity | Issuance limit per channel | What happens at the limit |
|---|---|---|---|
| Long-lived | No fixed expiry | 1 | Reissuing disables the active token |
| Short-lived | 30 days | 30 | The oldest token is revoked when another is issued |
| v2.1, user-specified expiry | Up to 30 days | 30 | A new issuance is rejected |
| Stateless | 15 minutes | No stated count limit | Cannot be revoked after issuance |
The safest choice depends on what the vendor supports. Do not rotate a shared long-lived token until every dependent tool is identified. For tokens with expiry, make renewal ownership explicit and test the new credential before the old one expires. Never paste one team’s production token into an unrelated tool merely because it is convenient.
Decide who owns the single webhook URL
LINE sends friend-add and message events to the webhook URL configured in the LINE Developers Console. A channel has one webhook URL, so a new tool that overwrites the URL can silently stop the existing receiver.
Use this decision table before installation:
| Tool requirement | Recommended design |
|---|---|
| Sends messages or manages rich menus only | Give it an appropriate token; leave the webhook owner unchanged |
| Needs all inbound events and replaces the current receiver | Migrate the URL with rollback and delivery tests |
| Two systems both need inbound events | Receive once, verify the LINE signature, store the event, then fan out internally |
| Vendor requires direct webhook ownership and cannot consume forwarded events | Use one inbound owner, or use a separate Official Account; do not assume both tools can coexist |
LINE recommends signature verification and asynchronous processing. Webhook redelivery can produce duplicates and changed arrival order, so deduplicate official LINE events with webhookEventId and order business state using the event timestamp where needed. There is no API to retrieve a text message again after the webhook has arrived, which makes durable storage at the receiving boundary important.
Six checks before adding the next tool
- Inventory features. List every endpoint, webhook event, rich menu, audience, and statistics function used by each tool.
- Assign token ownership. Record token type, expiry, renewal owner, secret store, and emergency revocation path.
- Name the webhook owner. Confirm the installer will not replace the current URL without an approved migration.
- Budget shared limits. Add request rates across tools and monitor
429 Too Many Requests, monthly message counts, rich menus, and audiences. - Test interaction effects. Verify that the existing receiver accepts any newly enabled event types and that one tool’s configuration changes do not break another.
- Run rollback acceptance. Send a controlled message, confirm exactly one durable record, verify downstream delivery, and rehearse restoring the previous webhook URL and token.
Where UnifyPort fits
UnifyPort is a separate path for teams that need inbound messages from an ordinary LINE account or a normalized queue across LINE, WhatsApp, Telegram, TikTok, Zalo, and X. It does not reuse a LINE Official Account’s Messaging API channel, channel access token, rich menus, audiences, or single official webhook setting.
After connecting LINE through the documented QR flow, UnifyPort delivers normalized message.received events to your registered endpoint. When signing_secret is enabled, deliveries include X-Device-Timestamp and X-Device-Signature; verify the HMAC-SHA256 signature against the raw body before storage or routing. The LINE authorization guide describes the login boundary, and the webhook delivery guide documents signing, retries, ordering, and idempotency.
That path can simplify a cross-channel inbox, but it should not be presented as another tool sharing the Official Account’s Messaging API channel. Keep the two architectures explicit.
Limitations and trade-offs
Use the official Messaging API when you need Official Account broadcasts, rich menus, audiences, account-linked events, or other native LINE features. A fan-out service adds an internal component to operate, secure, and monitor. Some vendors may prohibit forwarded events or require direct webhook control, so confirm their contract and technical requirements before integration.
UnifyPort’s unofficial interface does not provide LINE Official Account campaign, audience, or rich-menu management. It also cannot remove channel-level limits from official tools. Its role is ordinary-account and cross-channel message intake, not changing LINE’s Official Account model.
FAQ
Can two tools use the same LINE Messaging API channel?
Yes. They can call the same channel with supported channel access tokens, but they share channel settings, rate limits, and feature quotas.
Can LINE send one webhook event to two URLs?
No. One webhook URL is configured for the Messaging API channel. Receive once and fan out internally if two systems need the event.
Will issuing a new LINE channel access token break another tool?
It can. Reissuing the only long-lived token disables the current one, and issuing beyond the short-lived limit revokes the oldest token. Check the token type and dependencies first.
Do multiple tools get separate LINE rate limits?
No. Messaging API rate limits are applied per API function and per channel, regardless of different callers or IP addresses.
Is UnifyPort a second webhook for the same LINE Official Account?
No. It is a separate ordinary-account and normalized inbound path. It does not attach a second URL to the Official Account’s Messaging API channel.
Next step
Start with LINE’s official multiple-tools checklist and document the current token and webhook owner before connecting anything. If your actual requirement is ordinary-account or cross-channel inbound, review the UnifyPort LINE authorization guide as a separate architecture.
Sources
Official sources checked on August 4, 2026:
- LINE Developers: Points to check when using the Messaging API from multiple tools
- LINE Developers: Channel access token
- LINE Developers: Receive messages (webhook)
- LINE Developers: Messaging API reference — rate limits