Delete objects
Removes one object and answers 204.
DELETE /v1/s3/buckets/{bucket}/objects/{wildcard1}
| Address | https://api.hanzo.ai/v1/s3/buckets/{bucket}/objects/{wildcard1} |
| Method | DELETE |
| Operation | delete_s3_buckets_by_bucket_objects_by_wildcard1 |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Removes one object and answers 204.
It removes ONE object and never a prefix: a key that looks like a folder deletes the placeholder at that key, not the objects beneath it. The key is path-cleaned first, so the delete cannot reach outside the bucket it names, and a bucket the caller's org does not own is the same 404 an unknown name gives.
Billed per call: the balance is checked BEFORE anything is touched, so an unfunded org is refused with nothing deleted, and the debit lands only once the object is gone.
Request
2 fields.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
bucket | path | string | yes | Bucket is the bucket's friendly name, from the path. |
wildcard1 | path | string | yes | Key is the object's key within the bucket — everything after that bucket's /objects/. |
Response
| Status | Body | Meaning |
|---|---|---|
204 | — | no content |
default | problem-details | refused |
Failure carries the platform error shape — see Errors.
Examples
hanzo s3 buckets objects rm <bucket> <wildcard1>import { Configuration, S3Api } from 'hanzoai';
const api = new S3Api(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.deleteS3BucketsByBucketObjectsByWildcard1({ bucket: 'bucket', wildcard1: 'wildcard1' });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).delete_s3_buckets_by_bucket_objects_by_wildcard1(bucket='bucket', wildcard1='wildcard1')cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)
resp, _, err := client.S3API.DeleteS3BucketsByBucketObjectsByWildcard1(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::delete_s3_buckets_by_bucket_objects_by_wildcard1(&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).deleteS3BucketsByBucketObjectsByWildcard1();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl -X DELETE https://api.hanzo.ai/v1/s3/buckets/<bucket>/objects/<wildcard1> \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches s3 through the s3 tool, which names its 13 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"
}
}
}'