/drive/v3/files/{}/permissions* → endpoint removal
Google APIsDeprecated, no date
Google APIs has deprecated the enforceExpansiveAccess query parameter without a shutdown date. The deprecation applies to all methods in the permissions resource, including calls to /drive/v3/files/{}/permissions*. Requests relying on this parameter will eventually fail once it is removed.
Calls it hits
/drive/v3/files/{}/permissions*query parameter enforceExpansiveAccess
What to use instead of these calls
Use the folders with limited access setting to restrict item access.
In Google APIs's words
Generally Available: The enforceExpansiveAccess query parameter is now deprecated for all methods in the permissions resource (v2 and v3).
Facts
- API
- Google APIs
www.googleapis.com - Kind
- Endpoint removal
- Announced
- February 25, 2026
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Google APIs's own pages
Questions
When does this change take effect?
Google APIs deprecated /drive/v3/files/{}/permissions*, query parameter enforceExpansiveAccess without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Google APIs 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 Google APIs 6
-
/youtube/v3/captionsEndpoint removal Stopped working -
GET /youtube/v3/commentThreadsEndpoint removal Stopped working -
GET /analytics/v3/data/*Version retirement Stopped working -
/androidcheck/v1/*Endpoint removal Stopped working -
GET /customsearch/v1/siterestrictEndpoint removal Stopped working -
GET /customsearch/v1*Endpoint removal Stops workingin 67 days
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.