Presigned R2 GET for a file

Deprecated

POST

/v1/datasets/download/presign

curl --request POST \
  --url https://example.com/v1/datasets/download/presign \
  --header 'Content-Type: application/json' \
  --header 'X-API-Key: <X-API-Key>' \
  --data '{ "name": "example", "file_id": "example", "ttl_seconds": 300 }'

Deprecated: only SDKs before 0.6.9 call this, and it is removed at the date in its Sunset header. Use POST /v1/datasets/download/presign-exact-batch, which plans a whole page of files of one immutable snapshot, as the current SDK does.

Presigned GET plan for one file. The file_id MUST belong to the caller’s own org — qds-api’s tenant-scope gate 404s a foreign file_id, so a customer can’t presign another account’s chunks by guessing one (no tree pre-fetch).

Authorizations

• ApiKey
• Bearer

Request Body ^required

Media type application/json

DownloadPresignBody

object

name

required

string

file_id

required

string

ttl_seconds

integer

default: 300

Responses

200

Successful Response

Media type application/json

Example ^generated

example

401

Invalid or missing API key

Media type application/json

ErrorResponse

Standard error response.

object

detail

required

Error message describing what went wrong

string

Example ^generated

{
  "detail": "example"
}

422

Validation Error

Media type application/json

HTTPValidationError

object

detail

Array<object>

ValidationError

object

loc

required

Location

Array<string | integer>

msg

required

Message

string

type

required

Error Type

string

input

ctx

Context

object

Example ^generated

{
  "detail": [
    {
      "loc": [
        "example"
      ],
      "msg": "example",
      "type": "example",
      "input": "example",
      "ctx": {}
    }
  ]
}