[Info] End of service for LINE Notify #3894

New issue

Closed

opened 2026-02-28 03:44:23 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-28 03:44:23 -05:00

Owner

Originally created by @rezzorix on GitHub (Jan 13, 2025).

Just for anyone using LINE notify... they are ending their service 31.03.2025: https://notify-bot.line.me/closing-announce

End of service for LINE Notify

Thank you for your continued support of LINE Notify.

We've been offering the LINE Notify service to developers since September 2016, but we are regrettably discontinuing this service as of March 31, 2025 in order to focus on providing you a superior service with a similar product that has inherited its management resources. We'd like to express our sincere gratitude to everyone who, over the years, has used this notification linking service delivered through LINE.

As a product for sending users notifications via LINE, we offer the Messaging API which has an increased variety of features.
Effects of service discontinuation

From April 1, 2025, all LINE Notify features, including those listed below, will become unavailable.
All LINE Notify APIs
    notify-bot.line.me/**
    notify-api.line.me/**
[My Page](https://notify-bot.line.me/my/) on LINE Notify
    Service registration
    Confirmation of connected services
    Generation of access tokens
In addition, the "LINE Notify" LINE official account (@linenotify) and the webpages listed below are planned to be deleted following May 12, 2025.
[LINE Notify website](https://notify-bot.line.me/)
    [LINE Notify API Document](https://notify-bot.line.me/doc/en/)
[LINE Notify documentation for "LINE Developers Thailand"](https://linedevth.line.me/th/line-notify)
[LINE Notify Help center](https://help2.line.me/line_notify/web/?lang=en)
[LINE Notify Terms of Use](https://terms2.line.me/line_notify_terms_of_use?lang=en)
Alternative service we offer

As an alternative means of sending notifications, consider using the Messaging API through which you can send messages from your LINE official account. By using the Messaging API you can send a fixed number of messages each month for free. For details on fees, see "Messaging API fees".

See the various pages of the "Messaging API documentation" for details on available features.

Originally created by @rezzorix on GitHub (Jan 13, 2025). Just for anyone using LINE notify... they are ending their service 31.03.2025: https://notify-bot.line.me/closing-announce > End of service for LINE Notify > > Thank you for your continued support of LINE Notify. > > We've been offering the LINE Notify service to developers since September 2016, but we are regrettably discontinuing this service as of March 31, 2025 in order to focus on providing you a superior service with a similar product that has inherited its management resources. We'd like to express our sincere gratitude to everyone who, over the years, has used this notification linking service delivered through LINE. > > As a product for sending users notifications via LINE, we offer the Messaging API which has an increased variety of features. > Effects of service discontinuation > > From April 1, 2025, all LINE Notify features, including those listed below, will become unavailable. > > All LINE Notify APIs > notify-bot.line.me/** > notify-api.line.me/** > [My Page](https://notify-bot.line.me/my/) on LINE Notify > Service registration > Confirmation of connected services > Generation of access tokens > > In addition, the "LINE Notify" LINE official account (@linenotify) and the webpages listed below are planned to be deleted following May 12, 2025. > > [LINE Notify website](https://notify-bot.line.me/) > [LINE Notify API Document](https://notify-bot.line.me/doc/en/) > [LINE Notify documentation for "LINE Developers Thailand"](https://linedevth.line.me/th/line-notify) > [LINE Notify Help center](https://help2.line.me/line_notify/web/?lang=en) > [LINE Notify Terms of Use](https://terms2.line.me/line_notify_terms_of_use?lang=en) > > Alternative service we offer > > As an alternative means of sending notifications, consider using the [Messaging API](https://developers.line.biz/en/services/messaging-api/) through which you can send messages from your LINE official account. By using the Messaging API you can send a fixed number of messages each month for free. For details on fees, see "[Messaging API fees](https://developers.line.biz/en/docs/messaging-api/overview/#line-official-account-plan)". > > See the various pages of the "[Messaging API documentation](https://developers.line.biz/en/docs/messaging-api/)" for details on available features.

deekerman

2026-02-28 03:44:23 -05:00

closed this issue
added the
feature-request

A:notifications

good first issue

house keeping
labels

deekerman commented

2026-02-28 03:44:29 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 13, 2025):

@rezzorix: Hello! 👋

This issue is being automatically closed because it does not follow the issue template. Please DO NOT open blank issues and use our issue-templates instead.
Blank Issues do not contain the context nessesary for a good discussions.

@github-actions[bot] commented on GitHub (Jan 13, 2025): @rezzorix: Hello! :wave: This issue is being automatically closed because it does not follow the issue template. Please **DO NOT open blank issues and use our [issue-templates](https://github.com/louislam/uptime-kuma/issues/new/choose) instead**. Blank Issues do not contain the context nessesary for a good discussions.

deekerman commented

2026-02-28 03:44:29 -05:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 18, 2025):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Mar 18, 2025): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

deekerman commented

2026-02-28 03:44:29 -05:00

Author

Owner

@dlackty commented on GitHub (Jan 22, 2026):

As #6088 was merged, this issue could be closed too.

@dlackty commented on GitHub (Jan 22, 2026): As #6088 was merged, this issue could be closed too.

deekerman commented

2026-02-28 03:44:29 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 22, 2026):