REST API

The Storage API manages a project’s buckets and files. Send every request to https://storage-api.digitospace.com. The paths below are relative to it.

Authentication

Send an API key with Storage permissions as a bearer token on every request:

Authorization: Bearer dsk_…

A missing, unknown, or expired key gets 401 with the code unauthenticated. See API keys.

Requests and responses

• Request bodies are JSON, sent with Content-Type: application/json, and at most 1 MB. File contents never go in a request to the API. See Uploads.
• Times are RFC 3339 in UTC, such as 2026-09-26T10:15:00Z.
• Sizes are whole bytes.
• {bucket} in a path is the bucket’s name or its ID.
• {key} is the file’s key. Encode each part of it for a URL, and keep the slashes, such as 2026/Dar%20es%20Salaam/report.pdf.

Every successful response wraps its result in data, with details about the request in meta:

{
  "data": { "id": "01m3c081d2wj4g63qcr53pa1yh", "name": "invoices" },
  "meta": { "requestId": "01m3c081dbf3j55x7hsa7wc1yj" }
}

Every failure is a problem document with a stable code. See Errors.

Paging

Buckets come in pages of 50, or up to 200 with limit. Files come in pages of 100, or up to 1,000 with limit.

For the next page, pass meta.page.nextCursor from the last response as cursor. It is null on the last page.

GET /v1/projects/{project}/buckets/{bucket}/objects?limit=500&cursor=…

Endpoints