![]()
*.zendesk.com · MarketingSubscribeShare
Zendesk API breaking changes
The breaking changes Zendesk API announced that Okapi tracks: 8 in all.
Do you run the Zendesk API? Make sure your users call it right →
At a glance
- API host
*.zendesk.com- Kind
- Marketing
- Versions with breaking changes
- v2 (6)
- Next breaking change
- API token authentication stops working on calls authenticated with an API token,
- Breaking changes tracked
- 1 breaking change coming up, 2 with no date yet and 5 already in effect
- Last updated
Coming up 1
-
/api/v2/*Behaviour change Stops workingin 175 days
Deprecated, no date yet 2
-
No date
GET /api/v2/apps/locations/{id}Endpoint removal Deprecated, no date -
No date
POST /api/v2/oauth/tokensEndpoint removal Deprecated, no date
Already in effect 5
-
/api/sunshine/objects/*Removal Stopped working -
/api/sunshine/relationships/*Removal Stopped working -
/api/v2/*Behaviour change Stopped working -
PUT /api/v2/users/me/mergeEndpoint removal Stopped working -
/api/v2/nps/*Removal Stopped working
Where Okapi reads it
- Changelog developer.zendesk.com/api-reference/changelog/changelog/
- OpenAPI spec developer.zendesk.com/zendesk/oas.yaml
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub