LINE Messaging API
GET /v2/bot/audienceGroup/authorityLevel endpoint removal
Stopped workingSubscribe to LINE Messaging APIShare
On March 26, 2025, LINE discontinued features to set and check public and private audience settings. Requests to GET /v2/bot/audienceGroup/authorityLevel now fail.
Calls it hits
GET /v2/bot/audienceGroup/authorityLevel
What to use instead of these calls
Remove the call. Audiences created with the Messaging API and the LINE Official Account Manager are usable in both without an authority level.
In LINE Messaging API's words
the features to set and check the public/private setting of audiences created with the Messaging API has been discontinued as of March 26, 2025.
Facts
- API
- LINE Messaging API
api.line.me - Kind
- Endpoint removal
- Announced
- February 6, 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 GET /v2/bot/audienceGroup/authorityLevel 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
-
PUT /v2/bot/audienceGroup/{id}/activateEndpoint 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.