Download stored bytes by hash
GET /storage/objects/{hash}
Returns the stored bytes for a SHA-256 hash. The response is always
application/octet-stream, whatever type the upload recorded.
Any signed-in account can download the bytes for any hash. This
route doesn’t look at assets, so an asset’s access rules don’t apply
here; to get an asset’s file with its rules checked, use GET /assets/{id}/file.
To get part of the file, send one range as bytes=start-end or
bytes=start-. You get 206 but no Content-Range header. A range
that runs past the end of the file can come back shorter than its
Content-Length, or fail with a 500, depending on the storage
backend. Any other Range value gets the whole file with 200, never
416.
404 means no bytes are stored under that hash, and a value that
isn’t 64 lowercase hex characters gets a plain-text 500. The
response has no ETag or caching headers.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The bytes’ SHA-256, as 64 lowercase hex characters (the hash an upload returns).
Header Parameters
Section titled “Header Parameters ”Optional. bytes=start-end or bytes=start- asks for part of the file; any other value gets the whole file.
Responses
Section titled “ Responses ”The whole file.
The requested range, without a Content-Range header.
Authentication required, missing, or invalid
object
Human-readable error summary
Example
the request could not be completedExample
{ "error": "authentication required: sign in and retry with a valid session or API token"}Resource not found
object
Human-readable error summary
Example
the request could not be completed