LINE Notify Not Working? Fixes & Common Causes

If LINE Notify has stopped sending messages, the most common causes are a revoked access token, an expired LINE account session, or a temporary service outage. This guide walks through the exact steps to diagnose and fix each issue, plus what to do if the problem persists.

What LINE Notify Is and How It Works

LINE Notify is an official service from LINE Corporation that lets third-party services (like IFTTT, Zapier, or custom scripts) send messages directly to your LINE chat. Instead of logging into LINE as a bot, you generate a personal access token on the LINE Notify website, then use that token in an HTTP POST request to the LINE Notify API endpoint. When the request is successful, the message appears in a chat with the “LINE Notify” official account.

The key detail most people miss: each access token is tied to a specific LINE account and a specific service. If you log out of LINE on your phone, change your password, or revoke the token on the LINE Notify site, every service using that token stops working immediately.

First Things to Check (Before You Blame the Service)

Before diving into advanced fixes, run through these quick checks. They resolve roughly half of all “LINE Notify not working” reports.

• Is the service you connected still active? IFTTT applets, Zapier zaps, and custom cron jobs can be paused, deleted, or rate-limited. Log into the third-party service and confirm the trigger actually fired.
• Did you test with a manual API call? Use a tool like cURL or Postman to send a test message directly to the LINE Notify API. If that works, the problem is in the middle layer, not LINE.
• Is your LINE app updated? LINE Notify relies on the standard LINE messaging infrastructure. An outdated app can sometimes fail to display notifications even though the message was delivered.
• Check your notification settings on the phone. The message may be arriving, but your phone’s notification settings for LINE are muted or set to “no popup.” Open the LINE app and look for the LINE Notify chat to see if the message is actually there.

Most Common Cause: Revoked or Expired Access Token

Access tokens for LINE Notify do not expire on their own, but they are instantly invalidated if you click “Revoke” on the LINE Notify website, or if you disconnect the service from the third-party app. Many people revoke a token while testing, then forget they did it.

Another scenario: you generated a token while logged into LINE with one account, then later switched accounts on your phone. The token is bound to the account that created it. If you’re now logged into a different LINE account, the token will fail with an invalid access token error.

Fix: Go to notify-bot.line.me, log in with the same LINE account that created the token, and click “Manage” next to the service name. You’ll see the token status and a “Revoke” button. If the token is missing from the list, it was already revoked. Generate a new token and update your script or third-party service.

How to Test Your Token in 30 Seconds

If you’re not sure whether the token is valid, send a test message directly to the API using a simple command. On Windows, Linux, or macOS with cURL installed, run:

curl -X POST -H "Authorization: Bearer YOUR_TOKEN_HERE" -F "message=test" https://notify-api.line.me/api/notify

Replace YOUR_TOKEN_HERE with your actual token. You should get a JSON response like {"status":200,"message":"ok"} and see “test” appear in your LINE chat. If you get status: 401, the token is invalid or revoked. If you get status: 400, the message parameter is missing or malformed. If you get a network error, the problem is on your side (firewall, proxy, or DNS).

LINE Notify Service Outages and Status Pages

LINE Notify itself is a free service and does not have a public status page that lists real-time uptime. However, large-scale outages are rare and usually tied to LINE’s broader messaging platform. If your token works in a manual test but messages still don’t arrive, wait 15–30 minutes and try again. Check social media or general tech forums for others reporting the same issue at the same time. If the problem persists for hours, it’s more likely a local configuration issue than a LINE-wide outage.

Common Mistakes in Custom Scripts and IFTTT

When people write their own scripts, the most frequent errors are:

• Using the wrong endpoint. The correct URL is https://notify-api.line.me/api/notify. Some older tutorials use api.line.me/v2/bot/message, which is a different API (Messaging API) and requires a channel access token, not a LINE Notify token.
• Sending as JSON instead of form data. LINE Notify expects application/x-www-form-urlencoded or multipart form data. If you send a raw JSON body, the API returns a 400 error.
• Missing the message parameter. The message field is required. You can include other optional fields like stickerPackageId, stickerId, or imageThumbnail, but if message is absent, the request fails.
• Rate limiting. LINE Notify allows a certain number of requests per hour per token. If you exceed it, you’ll get a 429 error. The exact limit is not officially published, but it’s high enough for personal use. If you’re sending hundreds of messages, space them out.

What to Do If Nothing Works

If you’ve tested the token manually, confirmed the third-party service is active, and still see nothing, try these steps in order:

1. Generate a brand new token on the LINE Notify site and update your service. This eliminates any hidden revocation or account mismatch.
2. Log out and back into LINE on your phone. This refreshes the session that receives the notification.
3. Uninstall and reinstall LINE (back up your chats first). This clears any corrupted local data that might block incoming messages from specific accounts.
4. Check if the LINE Notify chat is blocked or hidden. Open the LINE Notify chat, tap the menu, and verify you haven’t muted or blocked it.
5. Try a different network. Some corporate or school networks block API endpoints. Test using your phone’s mobile data instead of Wi-Fi.

If none of these work, the issue may be on LINE’s side. Wait a few hours and retest. LINE Notify is a free service with no official support channel, so community forums are the best place to check if others are having the same problem.

Alternatives to LINE Notify

If LINE Notify continues to fail for you, consider these alternatives, each with different strengths:

• LINE Messaging API — This is the official bot API for LINE. It requires creating a provider and channel on the LINE Developers console, but it’s more reliable for production use and supports two-way communication.
• Telegram Bot API — Free, well-documented, and doesn’t require a phone number to receive messages. You create a bot with BotFather and send messages via a simple HTTP request.
• Discord Webhooks — If you’re already on Discord, a webhook URL lets you post messages to a channel with a simple POST request.
• Pushover — A paid (one-time) notification service that works on both iOS and Android and has a very simple API.

Each alternative has its own token or key system, but the debugging approach is the same: test the API directly first, then check the middle layer.

Frequently Asked Questions

Why did my LINE Notify token stop working after I changed my LINE password?

Changing your LINE password does not automatically revoke tokens, but it can invalidate all active sessions on some devices. If you were logged into the LINE Notify website on a device that got logged out, the token may still be valid, but you’ll need to log back in to manage it. The safest fix is to generate a new token after any account security change.

Can I use one LINE Notify token for multiple services?

Yes, you can use the same token in multiple scripts or IFTTT applets. However, if you revoke that token, all services stop at once. For easier management, generate a separate token per service so you can revoke one without affecting the others.

Does LINE Notify work with a LINE account that has no phone number?

LINE Notify requires a valid LINE account. If your account was created with Facebook or Apple ID and has no phone number, it still works as long as you can log in to the LINE Notify website. Some users report issues with accounts that were created solely for testing and have no verified email; make sure your email is verified.

Why do I get a 400 error when sending a message with an image?

A 400 error usually means the request is malformed. For image messages, you must provide both imageThumbnail and imageFullsize URLs, and both must be publicly accessible over HTTPS. If either URL is broken or returns a non-image file, the API rejects the entire request.

Is LINE Notify free forever?

LINE Notify has been free since its launch, and LINE has not announced any plans to charge for it. However, it is a legacy service that LINE has not actively promoted in recent years. If LINE ever discontinues it, users would likely receive advance notice through the official LINE Notify account, but there is no guarantee.

Can I receive LINE Notify messages on multiple devices?

Yes. LINE Notify sends the message to your LINE account, so it appears on any device where you’re logged into that same LINE account, including phone, tablet, and desktop. If you don’t see it on one device, check that the device is actually logged in and has a working internet connection.

Related

• Sarah Silverman and Artists Sue OpenAI and Meta: Why
• Best Chatbot Examples: 5 Standout Tools and Use Cases
• RAG Explained Simply: Stop Your AI Chatbot Making Things Up