Files API
Store private bytes without confusing storage with inference.
Availability#
This page preserves the corresponding public documentation URL. The endpoint is not enabled for public use yet. A request example describes the intended interface, not a claim of deployed support. Consult the capability matrix and your access configuration before integration.
Upload, inspect, delete#
Create one owned file, retain its returned id, retrieve metadata or authenticated content, then delete it when no longer needed. Configure an explicit retention period within the supported policy. No public object URL or client-selected storage key is accepted.
Recovery and quotas#
Storage needs owner/global byte quotas, bounded concurrent uploads and durable cleanup. A reservation precedes object writes. Expired, interrupted and orphaned uploads must be reclaimed without waiting for a new user request.