LINE Messaging API
PUT /v2/bot/audienceGroup/{id}/activate endpoint removal
Stopped workingSubscribe to LINE Messaging APIShare
On March 26, 2025, the activate audience endpoint PUT /v2/bot/audienceGroup/{id}/activate was removed. LINE added it to the list of endpoints that have been discontinued. Calls to this endpoint now fail.
Calls it hits
PUT /v2/bot/audienceGroup/{id}/activate
What to use instead of these calls
Remove the call from your integration, as LINE documents no replacement endpoint. Because the activate audience endpoint has no replacement, callers must decide how the audience is used going forward.
The Activate audience endpoint has no replacement: whoever relies on it decides how the audience is used now.
In LINE Messaging API's words
We've added the Activate audience endpoint to the list of endpoints that have been discontinued.
Facts
- API
- LINE Messaging API
api.line.me - Kind
- Endpoint removal
- Announced
- March 26, 2025
- Takes effect
- March 26, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against LINE Messaging API's own pages
Questions
When does this change take effect?
Calls to PUT /v2/bot/audienceGroup/{id}/activate on LINE Messaging API stopped working on March 26, 2025.
What happens to calls after March 26, 2025?
They have failed since March 26, 2025.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from LINE Messaging API 2
-
GET /v2/bot/audienceGroup/authorityLevelEndpoint removal Stopped working -
PUT /v2/bot/audienceGroup/authorityLevelEndpoint removal Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.