Create parts

Answers presigned PUT URLs for some parts of a multipart upload, at most 64 a call, each valid for minutes: mint them as the upload reaches them.

POST /v1/s3/buckets/{bucket}/uploads/{upload}/parts

Addresshttps://api.hanzo.ai/v1/s3/buckets/{bucket}/uploads/{upload}/parts
MethodPOST
Operationpost_s3_buckets_by_bucket_uploads_by_upload_parts
AuthAuthorization: Bearer $HANZO_API_KEY

Answers presigned PUT URLs for some parts of a multipart upload, at most 64 a call, each valid for minutes: mint them as the upload reaches them. PUT a part's bytes to its URL as they are — no headers are signed — and the store answers the part's ETag, which completing does not need.

Request

6 fields, body application/json (required).

FieldInTypeRequiredDescription
bucketpathstringyesBucket is the bucket, from the path.
uploadpathstringyesUpload is the upload's id, from the path.
bucketbodystring—Bucket is the bucket, from the path.
keybodystring—Key is the object key the upload was started on.
partsbodyinteger (int64)[]—Parts are the part numbers to mint URLs for, from 1.
uploadbodystring—Upload is the upload's id, from the path.

Response

StatusBodyMeaning
200s3.partURLsok
defaultproblem-detailsrefused

200 body — 4 fields.

FieldInTypeAlwaysDescription
expiresInbodyinteger (int64)—Expiry is how many seconds the URLs stay valid.
urlsbodys3.partURL[]—URLs are one presigned PUT per part asked for.
urls[].partbodyinteger (int64)—Part is the part number.
urls[].urlbodystring—URL is the presigned address to PUT the part's bytes to, directly.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, S3Api } from 'hanzoai';

const api = new S3Api(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postS3BucketsByBucketUploadsByUploadParts({ bucket: 'bucket', upload: 'upload', bucket: "<bucket>", key: "<key>" });
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import S3Api

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = S3Api(client).post_s3_buckets_by_bucket_uploads_by_upload_parts(bucket='bucket', upload='upload', bucket="<bucket>", key="<key>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.S3API.PostS3BucketsByBucketUploadsByUploadParts(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, s3_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = s3_api::post_s3_buckets_by_bucket_uploads_by_upload_parts(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.S3Api;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new S3Api(client).postS3BucketsByBucketUploadsByUploadParts();
curl -X POST https://api.hanzo.ai/v1/s3/buckets/<bucket>/uploads/<upload>/parts \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "bucket": "<bucket>",
       "key": "<key>"
     }'

MCP reaches s3 through the s3 tool, which names its 6 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_s3_buckets"
         }
       }
     }'

S3 API · All Hanzo APIs · Interactive reference

Was this page useful?