GET /2.0/file_version_retentions → endpoint removal
Box API
Deprecated, no date
The GET /2.0/file_version_retentions endpoint has been deprecated without a shutdown date, noting that the "File retention API is now deprecated". Requests to this endpoint will eventually fail. The change impacts all callers currently querying file version retention policies via this route.
Calls it hits
GET /2.0/file_version_retentions
What to use instead of these calls
List files under retention using GET /2.0/retention_policy_assignments/{id}/files_under_retention instead. Alternatively, query file versions with GET /2.0/retention_policy_assignments/{id}/file_versions_under_retention.
In Box API's words
File retention API is now deprecated
Facts
- API
- Box API
api.box.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Box API's own pages
Questions
When does this change take effect?
Box API deprecated GET /2.0/file_version_retentions without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Box 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 Box API 6
-
No date
azure__openai__gpt_4_1_miniModel retirement Deprecated, no date -
No date
azure__openai__gpt_4o_miniModel retirement Deprecated, no date -
No date
GET /2.0/file_version_retentions/{}Endpoint removal Deprecated, no date -
No date
google__gemini_2_0_flash_lite_previewModel retirement Deprecated, no date -
No date
ibm__llama_4_scoutModel retirement Deprecated, no date -
No date
xai__grok_3_mini_betaModel retirement 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.