LINE Engagement (BYOK)

LINE Engagement (BYOK) — connector documentation

• MCP endpoint: https://byok-line-engagement.connectorbay.com/mcp
• REST API: POST https://byok-line-engagement.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-line-engagement.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own LINE Engagement channel access token (long-lived or stateless) of a Messaging API channel, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-line-engagement.connectorbay.com/health · Tool schemas: https://byok-line-engagement.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-line-engagement · agent@connectorbay.com

What LINE Engagement (BYOK) is for

LINE Engagement (BYOK) lets an AI assistant read your own LINE Engagement data through the LINE Engagement API with a key you supply (channel access token (long-lived or stateless) of a Messaging API channel). Read-only: 11 tools (get_message_event_stats, get_aggregation_event_stats, get_richmenu_insight_summary, get_richmenu_insight_daily, get_rich_menu, list_rich_menu_aliases, get_rich_menu_alias, get_default_rich_menu, list_coupons, list_membership_plans, list_liff_apps). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.line.me. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINE Engagement. LINE Engagement and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "How many people clicked the links in my LINE broadcast?"
• "What was the click rate of my LINE campaign labelled promotion_a?"
• "Which area of my LINE rich menu gets tapped the most?"
• "How did my LINE rich menu perform day by day last week?"
• "What does my LINE rich menu look like?"
• "Which rich menu aliases are set up on my LINE account?"

What it does

• get_message_event_stats: Get interaction statistics of one sent message request: delivered, unique impressions, unique clicks, media plays, per-message impressions and per-link clicks.
• get_aggregation_event_stats: Get interaction statistics for messages labelled with a custom aggregation unit over a date range: unique impressions, clicks, media plays and per-link clicks.
• get_richmenu_insight_summary: Get totals for one rich menu over a date range: impressions and unique users, plus clicks and unique users per tappable area.
• get_richmenu_insight_daily: Get day-by-day impressions and clicks (with unique users) for one rich menu over a date range.
• get_rich_menu: Get one rich menu: name, chat bar text, size, whether it is selected by default and its tappable areas.
• list_rich_menu_aliases: List rich menu aliases (alias ID to rich menu ID) used for tab-style rich menu switching.
• get_rich_menu_alias: Get which rich menu one alias points to.
• get_default_rich_menu: Get the ID of the rich menu shown to all users by default.
• list_coupons: List coupons created on the Official Account (ID and title), with a continuation token for more.
• list_membership_plans: List the membership plans of the Official Account with price, currency, member count, member limit and published flag.
• list_liff_apps: List the LIFF apps registered on the channel with view type, URL, features, scope and bot prompt setting.

BYOK key

You bring your own LINE Engagement channel access token (long-lived or stateless) of a Messaging API channel (https://developers.line.biz/console/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.line.me over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developers.line.biz/en/reference/messaging-api/#get-insight-message-event (the API this connector calls, with a BYOK key)

Live from the LINE Engagement API (api.line.me) with a BYOK key; documentation: https://developers.line.biz/en/reference/messaging-api/#get-insight-message-event. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINE Engagement. LINE Engagement and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your LINE Engagement account.

Built for: Worldwide. Languages: English.

LINE Engagement (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What LINE Engagement (BYOK) is. LINE Engagement (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own LINE Engagement data: Read LINE Official Account message interaction statistics, rich menu performance, rich menu aliases, coupons, membership plans and LIFF apps with your own channel access token (read-only). You bring your own LINE Engagement channel access token (long-lived or stateless) of a Messaging API channel; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one LINE Engagement call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.line.me, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If LINE Engagement rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What LINE Engagement receives. The request we make on your behalf, including the key and the arguments, under LINE Engagement's own terms and privacy policy. LINE Engagement acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer LINE Engagement gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your LINE Engagement data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. LINE Engagement (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at LINE Engagement at any time to end all access.

Children. LINE Engagement (BYOK) is a general-audience service operated by the adult using the assistant, under LINE Engagement's own age rules.

Changes. We will post changes here with a new effective date.

LINE Engagement (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the LINE Engagement (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. LINE Engagement (BYOK) provides: Read LINE Official Account message interaction statistics, rich menu performance, rich menu aliases, coupons, membership plans and LIFF apps with your own channel access token (read-only). It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own LINE Engagement credentials and only access data you are allowed to access. LINE Engagement's terms apply to your use of LINE Engagement; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by LINE Engagement. LINE Engagement and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data LINE Engagement returns, lightly trimmed; it may be incomplete, delayed or changed by LINE Engagement. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your LINE Engagement account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent LINE Engagement's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; LINE Engagement may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your LINE Engagement key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action LINE Engagement takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-line-engagement

LINE Engagement (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-line-engagement.connectorbay.com/mcp
• REST API: https://byok-line-engagement.connectorbay.com/openapi.json
• Live status: https://byok-line-engagement.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. LINE Engagement (BYOK) never asks for them.