Changelog

Changes to the Storage Buckets API are listed here, newest first.

A breaking change is one that can make code you have already written stop working. Removing or renaming an endpoint, a parameter, or a response field is breaking. So is changing the type of a field, or refusing a request that used to work. Adding an endpoint, an optional parameter, or a response field is not breaking, so your code should ignore fields it does not recognise. Breaking changes are marked Breaking in the entry.

October 2026

The Storage Buckets API is introduced.

• Buckets. Create a bucket, list your buckets, get a bucket, and delete a bucket.
• Files. Upload, download, get the details of, delete, and list files. Lists are read a page at a time, see Pagination.
• Folders. Create a folder so that it exists before it has any files.
• Visibility and links. Read and change whether a file is public or private, and get a link: permanent for a public file, temporary for a private one.
• Credentials. Read-only and read & write credentials, so an application gets only the access it needs.
• Paging. List files and List buckets both take limit and page, and answer with has_next and next_page. List files also takes folder, and folders is always a list. The names prefix, token, and next_token that List files used before still work. See Pagination.