Rocket.Chat API
GET /api/v1/livechat/inquiries.queued endpoint removal
Stopped workingSubscribe to Rocket.Chat APIShare
On November 1, 2024, GET /api/v1/livechat/inquiries.queued stopped working and calls to it fail. The endpoint was removed on that date. Any integration relying on this specific call receives errors after this shutdown.
Calls it hits
GET /api/v1/livechat/inquiries.queued
What to use instead of these calls
Call GET /api/v1/livechat/inquiries.queuedForUser instead.
In Rocket.Chat API's words
The endpoint is replaced by /livechat/inquiries.queuedForUser
Facts
- API
- Rocket.Chat API
*.rocket.chat - Kind
- Endpoint removal
- Takes effect
- November 1, 2024
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Rocket.Chat API's own pages
Questions
When does this change take effect?
Calls to GET /api/v1/livechat/inquiries.queued on Rocket.Chat API stopped working on November 1, 2024.
What happens to calls after November 1, 2024?
They have failed since November 1, 2024.
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 Rocket.Chat API 6
-
GET /api/v1/channels.imagesEndpoint removal Stopped working -
GET /api/v1/licenses.getEndpoint removal Stopped working -
GET /api/v1/licenses.isEnterpriseEndpoint removal Stopped working -
GET /api/v1/pw.getPolicyResetEndpoint removal Stopped working -
POST /api/v1/livechat/room.transferEndpoint removal Stopped working -
POST /api/v1/rooms.upload/{id}Endpoint 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.