Zendesk API
GET /api/v2/apps/locations/{id} endpoint removal
Deprecated, no dateSubscribe to Zendesk APIShare
Zendesk API deprecated the GET /api/v2/apps/locations/{id} endpoint without specifying a shutdown date, noting that it is deprecated for all accounts starting April 30, 2026. This change impacts any calls made to that route, which will eventually fail.
Calls it hits
GET /api/v2/apps/locations/{id}
What to use instead of these calls
Read locations with List Locations (GET /api/v2/apps/locations) instead.
In Zendesk API's words
Starting April 30, 2026, the /api/v2/apps/locations/{app_location_id} endpoint is deprecated for all accounts.
Facts
- API
- Zendesk API
*.zendesk.com - Kind
- Endpoint removal
- Announced
- January 30, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Zendesk API's own pages
Questions
When does this change take effect?
Zendesk API deprecated GET /api/v2/apps/locations/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Zendesk API has not given a shutdown date yet.
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 -
PUT /api/v2/users/me/mergeEndpoint 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
POST /api/v2/oauth/tokensEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.