Zendesk API
PUT /api/v2/users/me/merge endpoint removal
Stopped workingSubscribe to Zendesk APIShare
On May 19, 2023, the PUT /api/v2/users/me/merge endpoint was removed. Calls made to this endpoint fail after that day. The removal affects developers calling the self-merge route.
Calls it hits
PUT /api/v2/users/me/merge
What to use instead of these calls
Use the Merge End Users endpoint, PUT /api/v2/users/{user_id}/merge, instead.
In Zendesk API's words
The Merge Self with Another User endpoint is being removed and replaced with the Merge End Users endpoint.
Facts
- API
- Zendesk API
*.zendesk.com - Kind
- Endpoint removal
- Takes effect
- May 19, 2023
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Zendesk API's own pages
Questions
When does this change take effect?
Calls to PUT /api/v2/users/me/merge on Zendesk API stopped working on May 19, 2023.
What happens to calls after May 19, 2023?
They have failed since May 19, 2023.
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 Zendesk API 7
-
/api/v2/nps/*Removal Stopped working -
/api/v2/*Behaviour change Stopped working -
/api/sunshine/objects/*Removal Stopped working -
/api/sunshine/relationships/*Removal Stopped working -
/api/v2/*Behaviour change Stops workingin 175 days -
No date
GET /api/v2/apps/locations/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v2/oauth/tokensEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.