LINE Messaging API — build, review, and debug LINE bots
Full LINE Messaging API reference: webhook setup and signature verification, reply/push/multicast/narrowcast/broadcast sending, Flex Message design, Rich Menus, audience targeting, insights, coupons, and channel access tokens
- What
- Full LINE Messaging API reference: webhook setup and signature verification, reply/push/multicast/narrowcast/broadcast sending, Flex Message design, Rich Menus, audience targeting, insights, coupons, and channel access tokens
- Cost
- Free
- Needs
- a LINE Developers channel with a channel access token and channel secret (free at developers.line.biz) — your credentials go in the secure vault, never pasted anywhere; a bot server with a public HTTPS webhook URL
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @abgne's messaging-api skill, listed here with credit to its creator: a comprehensive, battle-ready reference for building, reviewing, and debugging LINE Bots on the LINE Messaging API. It walks the agent through a build workflow (load the right reference file per feature, consult expert profiles for architecture choices, code to the specs) and a review/debug workflow (cross-check code against size limits, token expiry, counting rules, required fields). Covered in depth: webhook signature verification (HMAC-SHA256, never reformat the body before verifying), reply/push/multicast/narrowcast/broadcast sending with rate limits and retry policy, the three-layer Flex Message structure (containers/blocks/components) with a component catalog, Rich Menu CRUD and display priority, audience management, messaging insights, coupons, channel access token lifecycle, URL schemes, and group/room APIs. The skill's own iron rule: never answer LINE API questions from memory — always consult the references, because LINE updates its APIs frequently. Honest caveats: needs a LINE Developers channel and its access token/channel secret (free, but your credentials live in your own vault); LINE's API changes often — the reference files are the source of truth, not the agent's memory; push quotas apply per plan. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a LINE Developers channel with a channel access token and channel secret (free at developers.line.biz) — your credentials go in the secure vault, never pasted anywhere; a bot server with a public HTTPS webhook URL Install "LINE Messaging API — build, review, and debug LINE bots" for me. It gives my agent @abgne's LINE Messaging API reference: build and review workflows, webhook signature verification (HMAC-SHA256, never reformat the body before verifying), reply/push/multicast/narrowcast/broadcast sending with rate limits and retry policy, the three-layer Flex Message structure, Rich Menu management, audience targeting, insights, coupons, channel token lifecycle, and URL schemes. The skill's iron rule: never answer LINE API questions from memory — consult the reference files, since LINE updates its APIs frequently. Apache-2.0 licensed. Repository: https://github.com/abgne/line-dev/blob/main/skills/messaging-api/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code — credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "messaging-api". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. create a LINE Developers channel and save the access token + channel secret in the vault; expose my bot server at a public HTTPS webhook URL). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.