Post v1volumes :start push
Start pushing a new version to a volume: returns a push handle and a short-lived URL to upload the manifest (the file listing) to. Content bytes never ride this API — they go directly to the volume store through the URLs the push RPCs hand out.
The push flow: StartVolumePush → upload the manifest → RequestVolumeBlobUploads (in batches) → upload the missing blobs → PublishVolumeVersion. An abandoned push needs no cleanup; its staged manifest expires on its own.
Authorizations
Hiloop API key sent as an HTTP Bearer token.
Path Parameters
The volume to push a new version to.
Body
The volume to push a new version to.
Response
OK
The push handle. Pass it to PublishVolumeVersion once the manifest and all content blobs are uploaded.
Short-lived pre-authorized URL to PUT the manifest (the JSON file listing: per file its path, mode, size, content digest, and chunk list) to. The URL is bound to this push's staging location; the request needs no additional credentials.
How long the upload URL stays valid, in seconds.
The largest manifest the server accepts for this push, in bytes.