I’m working with Document List API version 3 and using two-legged OAuth authentication through Google Apps Marketplace permissions. When I fetch folder contents using the API endpoint with folder document ID and xoauth_requestor_id parameter, I successfully get 10 folders in the response.
However, when I try to retrieve each individual folder using their specific document IDs with the same user credentials, 9 folders load perfectly but one consistently throws a ResourceNotFoundException. I’ve verified that this problematic folder still exists and the user definitely has proper access rights to it.
I’ve tried multiple attempts at different times but keep getting the same error. Has anyone encountered similar behavior where certain folders become inaccessible through the API even though they exist and permissions are correct? Could this be an API bug or is there a workaround besides migrating to Google Drive API?
This usually happens when folder metadata gets corrupted during sync or when there’s conflicting ACL entries the API can’t handle. I’ve seen this with three folders last year - Document List API kept failing but the web interface worked fine. Most of the time it’s folders that got moved between different org units or had sharing settings changed through batch operations. Try hitting the folder’s ACL directly with the ACL feed endpoint to check for broken permission entries. If that also fails, you know the folder’s permission metadata is definitely corrupted. You can work around it by using the parent directory and filtering results on your end, but that’ll hurt performance. Document List API v3 has known issues with permission edge cases that never got fixed before they deprecated it.
yea, sounds like a corruption issue or smth wrong with the metadata. I had a simliar issue b4, where the API wouldn’t access it even tho the folder was there. Maybe check if there are any special chars in the name or if it was made in a diff way? recreating could help but ik it’s not what ya want.
Had this exact issue six months ago with Document List API v3. Folder showed up in listings but threw ResourceNotFoundException when I tried accessing it directly. Turned out to be folder inheritance permissions that got screwed up during some org changes in our Google Apps domain. The folder had broken permission states - API couldn’t handle it even though the web interface worked fine. Fixed it by having our domain admin temporarily take ownership of the folder, then transfer it back to the original user. That reset whatever permission metadata was breaking the API. Also check if the folder has external users or weird sharing settings that might be messing with the API’s permission validation.