Drive
The file store behind every project, your account, and Studio's own build assets, and how to reach each one over the API.
Drive is not one file store, it is three, each with the same shape of operations but its own scope. Every method name says which one it acts on with its own suffix.
A _workspace or _studio call takes the project's app_id; a _user call does not, it always
means the caller's own account drive.
Methods
Core operations, one family at a time
Every scope carries the same operations, only the suffix changes:
List and inspect
get_drive_files_<scope> lists a folder's contents; get_drive_file_info_<scope> reads one
item's details.
Upload and organize
upload_drive_file_<scope> uploads a file; create_drive_folder_<scope> makes a folder;
rename_drive_file_<scope> / rename_drive_folder_<scope> renames either;
move_drive_files_<scope> and copy_drive_files_<scope> move or copy a batch of items
(user and workspace scopes) between folders.
Trash, restore, purge
On the user and workspace scopes, trash_drive_files_<scope> soft-deletes,
get_trashed_files_<scope> lists what is in the trash, restore_trashed_files_<scope> brings an
item back, and purge_trashed_files_<scope> removes it for good. The studio scope has no trash
step, delete_drive_files_studio and delete_file_bulk_studio delete outright, the same way
delete_drive_files_<scope> and delete_file_bulk_<scope> do on every scope for a permanent
removal.
Share, star, tag
update_drive_file_sharing_mode_<scope> changes who can open a file;
star_drive_file_<scope> toggles a bookmark; update_drive_file_tags_<scope> sets a file's tags;
get_shared_with_me_files_user lists what other people have shared with you.
Storage
get_drive_size_<scope> returns total bytes used; get_drive_breakdown_<scope> (user and
workspace scopes) breaks usage down by file type plus duplicate file groups.
upload_drive_file_workspace and its siblings take the file itself as an upload, not a JSON
field, the request is a multipart form rather than a plain JSON body the way most methods are.