Upload or replace a module Worker script
Publishes a module Worker to the org's OWN Cloudflare account under the name in the path, replacing whatever was there, and relays Cloudflare's result.
PUT /v1/cloudflare/workers/scripts/{script}
| Address | https://api.hanzo.ai/v1/cloudflare/workers/scripts/{script} |
| Method | PUT |
| Operation | put_cloudflare_workers_scripts_by_script |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Publishes a module Worker to the org's OWN Cloudflare account under the name in the path, replacing whatever was there, and relays Cloudflare's result. script carries the module SOURCE; the optional compatibility date, compatibility flags and bindings are packed into the multipart upload Cloudflare expects.
The path names the script and the body field named script is its source — two different things that share a name, which is exactly why this cannot be a typed op: a binder that gives the URL the last word would overwrite the source with the script's name. Requires ORG ADMIN (403 otherwise); an unparseable body or empty source is 400; 503 if the org has never connected a Cloudflare token.
Request
6 fields, body application/json.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
script | path | string | yes | |
bindings | body | any | — | |
compatibilityDate | body | string | — | |
compatibilityFlags | body | string[] | — | |
mainModule | body | string | — | |
script | body | string | — |
Response
| Status | Body | Meaning |
|---|---|---|
2XX | Success |
2XX body — 1 field.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
(body) | body | any | yes |
Failure carries the platform error shape — see Errors.
Examples
hanzo cloudflare workers scripts set <script>import { Configuration, CloudflareApi } from 'hanzoai';
const api = new CloudflareApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putCloudflareWorkersScriptsByScript({ script: 'script', bindings: "<bindings>", compatibilityDate: "<compatibilityDate>" });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import CloudflareApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = CloudflareApi(client).put_cloudflare_workers_scripts_by_script(script='script', bindings="<bindings>", compatibility_date="<compatibilityDate>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.CloudflareAPI.PutCloudflareWorkersScriptsByScript(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, cloudflare_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = cloudflare_api::put_cloudflare_workers_scripts_by_script(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CloudflareApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new CloudflareApi(client).putCloudflareWorkersScriptsByScript();curl -X PUT https://api.hanzo.ai/v1/cloudflare/workers/scripts/<script> \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"bindings": "<bindings>",
"compatibilityDate": "<compatibilityDate>"
}'The door reaches cloudflare through the cloudflare tool, which names its 33 operations with its own verbs — this one among them, under a name only the door 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_cloudflare_d1_databases"
}
}
}'How is this guide?