Download an object as a role
Storage's download as the role, streamed (Range and If-None-Match pass through). Needs the role held at Viewer.
Authorization
bearer In: header
Path Parameters
Database id
uuidBranch id
uuidBucket name
Object name (may contain /)
Query Parameters
The role to act as: row level security on storage.buckets and storage.objects
decides what it sees and may do. Absent, owner or the owner's name: owner mode, for an
Admin of the database only, which sees and writes past every policy (write-once buckets
still hold) and writes objects with no owner (owner null).
The JWT claims to run with: a JSON object (at most 4 KiB), {} when absent. Acting as
authenticated with {"sub": "<user id>"} shows what that app user sees.
The Postgres database; the branch's main database when absent. It must be served by the data API.
Upload: replace an existing object.
Download as an attachment; the value is the file name (empty: the object's own).
Response Body
application/octet-stream
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/databases/497f6eca-6276-4993-bfeb-53cbbbba6f08/branches/497f6eca-6276-4993-bfeb-53cbbbba6f08/storage/object/string/string"nullDelete several objects as a role DELETE
Storage's delete-many (`{"names": [...]}`) as the role. Needs the role held at Developer.
Upload an object as a role POST
Storage's streamed upload as the role, with no body cap here (the bucket's limits apply). `x-upsert: true` or `?upsert=true` replaces an existing object. Needs the role held at Developer.