LINE Notify Alternatives 2026: Migration Guide

#What Happened to LINE Notify?

LINE Notify was a free notification service that let anyone push a message to their own LINE chat — or a group — with nothing more than a personal access token and a single HTTP POST to notify-api.line.me. Since its launch in 2016 it quietly became the default plumbing for server monitoring alerts, CI/CD pipelines, Google Apps Script automations, IoT sensors, and countless internal tools across Thailand, Taiwan, and Japan.

That era is over. LY Corporation announced the discontinuation in October 2024, and LINE Notify officially ended service on March 31, 2025. Personal access tokens were invalidated, and the Notify API endpoints no longer accept requests. Any script still calling the old endpoint has been failing silently (or loudly) ever since.

LINE's officially recommended replacement is the LINE Messaging API — push messages sent from a LINE Official Account. That works, but it changes three things at once:

1. Authentication: a channel access token issued to a Messaging API channel replaces the personal Notify token.
2. Targeting: you now push to an explicit user ID or group ID instead of "whoever owns this token".
3. Economics: Notify was free and effectively unlimited for normal use; Messaging API push messages count against a monthly quota with a free tier.

If you are still deciding how to rebuild your notifications, this guide walks through every realistic option — including the ones that do not involve writing code.

#Your Migration Options at a Glance

#Option 1: LINE Messaging API push messages (the official path)

Create a LINE Official Account, enable the Messaging API, and call the /v2/bot/message/push endpoint. This is the closest functional replacement: programmatic, LINE-native, and it supports text, images, stickers, and rich Flex Messages that Notify never could. The trade-off is a slightly heavier setup and a message quota (details in the cost section).

#Option 2: LINE Official Account broadcast (no code)

If your "notifications" were really announcements to a group of people — promotions, schedule changes, status updates — the LINE Official Account Manager lets a human send broadcasts to all followers without touching an API. Pair it with our LINE Official Account setup guide if you are starting from zero.

#Option 3: An automation platform with webhook triggers

Tools like LineBot.pro's LINE automation sit on top of the Messaging API and give you back the thing Notify did best: a simple endpoint you can hit from any script, cron job, or third-party service, without managing tokens, user IDs, and quota logic yourself. This is the pragmatic choice for teams that want LINE delivery but not LINE plumbing.

#Option 4: Leave LINE for machine-to-human alerts

Be honest about your use case. If the recipients were only ever you and your ops team, a LINE Official Account may be overkill. Telegram bots, Discord webhooks, Slack incoming webhooks, ntfy, or plain email are free, take minutes to set up, and have no per-message quotas. Many Notify refugees moved server alerts to these channels and kept LINE strictly for customer-facing messaging.

#Migrating to the Messaging API

Here is the end-to-end path for Option 1:

1. Create a LINE Official Account (free) at LINE for Business, or follow our step-by-step setup guide.
2. Enable the Messaging API for that account in the LINE Developers Console. This creates a Messaging API channel.
3. Issue a channel access token (long-lived) from the channel's "Messaging API" tab. This replaces your old Notify token.
4. Get your target user ID. Your own user ID is displayed in the channel's Basic settings ("Your user ID"). Anyone else must add your OA as a friend before you can push to them.
5. For group notifications: enable "Allow bot to join group chats" in the OA settings, invite the bot to the group, and capture the groupId from the join webhook event. Unlike Notify, the group is identified by ID, not by token.
6. Swap the HTTP call in your scripts (next section).

If you would rather not build and host the webhook side yourself, our LINE development services cover exactly this kind of migration.

#Code-Level Migration (Before / After)

Before — LINE Notify (no longer works):

curl -X POST https://notify-api.line.me/api/notify \
  -H 'Authorization: Bearer NOTIFY_TOKEN' \
  --data-urlencode 'message=Backup finished OK'

After — Messaging API push:

curl -X POST https://api.line.me/v2/bot/message/push \
  -H 'Authorization: Bearer CHANNEL_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "to": "U1234567890abcdef1234567890abcdef",
    "messages": [{ "type": "text", "text": "Backup finished OK" }]
  }'

What actually changed:

For Node.js, the official @line/bot-sdk wraps all of this — see our Express middleware tutorial with working code. In Google Apps Script, replace the UrlFetchApp.fetch call to the Notify endpoint with a JSON POST to the push endpoint and move the token into script properties.

One genuine upgrade: push messages support Flex Messages, so a plain-text server alert can become a formatted card with severity colors and action buttons.

#Cost Implications: Notify Was Free — What Now?

LINE Notify cost nothing and was rate-limited generously (on the order of 1,000 calls per hour per token). The Messaging API works differently:

• Reply messages are free and unlimited — but replies require a reply token from an incoming user message, which notification scripts do not have.
• Push, multicast, and broadcast messages count against a monthly quota tied to your Official Account's plan, counted per recipient.
• Free tiers exist: in Japan and Taiwan the entry plans currently include 200 free messages per month; Thailand's free plan also includes a monthly free message quota. Check the LINE for Business pricing page for your country's current numbers, and see our Messaging API 2026 updates article for how quotas have evolved.

Do the math before migrating a chatty alerting system. A monitor that pings every 5 minutes generates roughly 8,600 messages a month — far beyond any free tier. Sensible mitigations:

1. Aggregate: batch low-priority events into a daily digest.
2. Filter: push only actionable, critical alerts to LINE.
3. Split channels: high-frequency machine noise goes to Discord/Telegram/ntfy for free; customer-facing and business-critical notifications stay on LINE.

#Comparison of Alternatives

The pattern that works for most businesses: keep customer-facing notifications on LINE (where your customers actually are in Thailand, Taiwan, and Japan) via the Messaging API or an automation platform, and move internal machine alerts to a free developer-oriented channel.

#Frequently Asked Questions

Q: Can I still use my LINE Notify token? No. The service ended on March 31, 2025. Tokens were invalidated and the notify-api.line.me endpoints no longer accept requests. There is no grace period or legacy mode.

Q: Is the LINE Messaging API free? Partly. Creating an Official Account and a Messaging API channel is free, and reply messages are unlimited. Push messages (what notification scripts need) count against a monthly quota — free tiers cover low volumes (e.g. 200 messages/month in Japan and Taiwan), with paid plans above that.

Q: How do I send to a group chat like Notify did? Enable group chat joining for your bot, invite the Official Account into the group, and capture the groupId from the webhook join event. Then push to that groupId instead of a user ID.

Q: I don't write code — what's my easiest option? Either send broadcasts manually from the LINE Official Account Manager, or use a no-code platform like LineBot.pro that exposes ready-made triggers and handles the Messaging API for you.

Q: What about my Google Apps Script / IFTTT automations? The HTTP call needs to change (JSON body, new endpoint, channel token, explicit recipient), but the overall pattern survives. For GAS, it is typically a 10-line change; for IFTTT-style tools, look for a Messaging API integration or route through a webhook automation platform.

Next steps:

• Follow the LINE Official Account setup guide to create your Messaging API channel
• Copy working webhook code from the @line/bot-sdk Express tutorial
• Check current quotas in the Messaging API 2026 updates
• Or let LineBot.pro's automation service handle the migration end-to-end