PUT /v1/objects/{}/{}/preferences/{}/categories/{} → endpoint removal
Knock API
Deprecated, no date
The provider has deprecated the PUT /v1/objects/{}/{}/preferences/{}/categories/{} endpoint without a shutdown date. Calls to this endpoint will fail. The endpoint previously handled requests to update a specific category preference for an object preference set.
Calls it hits
PUT /v1/objects/{}/{}/preferences/{}/categories/{}
What to use instead of these calls
Set the object preference set using PUT /v1/objects/{collection}/{object_id}/preferences/{id} with categories passed in the request body.
In Knock API's words
Updates a specific category preference for an object's preference set. Deprecated.
Facts
- API
- Knock API
api.knock.app - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Knock API's own pages
Questions
When does this change take effect?
Knock API deprecated PUT /v1/objects/{}/{}/preferences/{}/categories/{} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Knock 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 Knock API 1
-
No date
PUT /v1/users/{}/preferences/{}/*Endpoint 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.