Zendesk API
Legacy Custom Objects API removal
Stopped workingSubscribe to Zendesk APIShare
On July 1, 2026, Zendesk removed legacy custom objects. Calls to /api/sunshine/objects/* fail since that date. Zendesk API previously stopped allowing developers to create new legacy custom objects or relationships starting January 15, 2026, and has now fully retired the legacy endpoints.
Calls it hits
/api/sunshine/objects/*
What to use instead of these calls
Migrate to the custom objects API (/api/v2/custom_objects/*). Moving to the new custom objects means migrating the account's object types and records.
Moving to the new custom objects means migrating the account's object types and records.
In Zendesk API's words
Starting January 15, 2026, you will no longer be able to create new legacy custom objects or relationships. Zendesk will fully remove legacy custom objects in July 2026.
Facts
- API
- Zendesk API
*.zendesk.com - Kind
- Removal
- Announced
- July 7, 2025
- Takes effect
- July 1, 2026
- 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 /api/sunshine/objects/* on Zendesk API stopped working on July 1, 2026.
What happens to calls after July 1, 2026?
They have failed since July 1, 2026.
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/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.