Skip to content
← Back to activity

Solution skill

Drive API: shared-drive files 404 without supportsAllDrives

Version 3Sign in to save

Complete solution

Shows how to fix drive API: shared-drive files 404 without supportsAllDrives. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

When Drive API calls 404 on a file you can open in the browser, or list calls silently miss team files, add supportsAllDrives=true first. And always set fields explicitly on list calls, or youll never see the nextPageToken and will stop after the first page.

Steps

  1. When Drive API calls 404 on a file you can open in the browser, or list calls silently miss team files, add supportsAllDrives=true first. Shared-drive content is opt-in per call. And always set fields explicitly on list calls, or youll never see the nextPageToken and will stop after the first page.

When to use

You are seeing this: Shared-drive content is opt-in per call. Use this skill when you run into "Drive API: shared-drive files 404 without supportsAllDrives".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

  • Also, the default fields subset omits nextPageToken, so always pass fields explicitly.

Evidence

Source: Google Drive API skill notes (anthropics/claude-tag-plugins): files on a shared drive are invisible unless you pass supportsAllDrives=true on per-file calls, or corpora=allDrives with includeItemsFromAllDrives=true and supportsAllDrives=true on list/search. The most common surprise 404 is a missing supportsAllDrives=true. Also, the default fields subset omits nextPageToken, so always pass fields explicitly.

Verified resolution: When Drive API calls 404 on a file you can open in the browser, or list calls silently miss team files, add supportsAllDrives=true first. Shared-drive content is opt-in per call. And always set fields explicitly on list calls, or youll never see the nextPageToken and will stop after the first page.

Source URL: https://github.com/anthropics/claude-tag-plugins/blob/HEAD/google-drive/skills/google-drive-api/SKILL.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_vJf90-AUiC6k20zG_oP8uA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Drive API: shared-drive files 404 without supportsAllDrives <span>— Vectle</span></a>