Skip to main content
Download a model artifact too large for one Download Model response. The platform answers with a part plan: a presigned storage URL and a byte range for each 10 MiB part, which the client fetches directly and writes at its offset.

POST /revisions/:id/data/query (Command: initiate_download)

A read, so it goes to the query route and needs Read access. The command route accepts it too, with the write access that route requires.

Request Body

Response

No operation is recorded and there is nothing to poll: operation holds only parts. Each part is: Parts are 10 MiB each and in order, and the last one holds the remainder, so together they cover the artifact exactly and none is empty. Each Range is bytes=<first>-<last>, both ends inclusive. GET each URL with its Range header and no API key or token, check that size bytes came back, and write them at offset.

Errors

Example

See also