# The Legacy Custom Objects API stops working

Calls to /api/sunshine/objects/* on Zendesk API stopped working on July 1, 2026.

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.

## What to use instead

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.

- API: Zendesk API (*.zendesk.com)
- Kind: Removal
- Announced: July 7, 2025
- Takes effect: July 1, 2026
- Calls after that day: fail
- Calls it hits: `/api/sunshine/objects/*`
- Source: [Announcement](https://developer.zendesk.com/api-reference/changelog/changelog/)
- Verified: November 6, 2026, against Zendesk API's own pages
- Page: https://www.okapi.bot/providers/zendesk-api/breaking-changes/the-legacy-custom-objects-api-stops-working/

## 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.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent