Create deployments

Starts a build and deployment of one Cloudflare Pages project on the org's OWN Cloudflare account, and relays Cloudflare's deployment record back.

POST /v1/cloudflare/pages/projects/{project}/deployments

Cloudflare → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/cloudflare/pages/projects/{project}/deployments`
Method	`POST`
Operation	`post_cloudflare_pages_projects_by_project_deployments`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Starts a build and deployment of one Cloudflare Pages project on the org's OWN Cloudflare account, and relays Cloudflare's deployment record back. branch picks what to build; OMITTING it builds the project's production branch.

A body it cannot parse is IGNORED rather than refused — the deployment falls back to the production branch — which is the one rule to get right here and the reason this is not a typed op: a typed request would answer 400 where this deploys. Requires ORG ADMIN (403 otherwise), and 503 if the org has never connected a Cloudflare token.

Request

2 fields, body application/json.

Field	In	Type	Required	Description
`project`	path	string	yes
`branch`	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

CLI

SDK

HTTP

MCP

hanzo cloudflare pages projects deployments <project>

.ts

.py

.go

.rs

.java

import { Configuration, CloudflareApi } from 'hanzoai';

const api = new CloudflareApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postCloudflarePagesProjectsByProjectDeployments({ project: 'project', branch: "<branch>" });

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).post_cloudflare_pages_projects_by_project_deployments(project='project', branch="<branch>")

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.CloudflareAPI.PostCloudflarePagesProjectsByProjectDeployments(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_client::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::post_cloudflare_pages_projects_by_project_deployments(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.CloudflareApi;

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

var result = new CloudflareApi(client).postCloudflarePagesProjectsByProjectDeployments();

curl -X POST https://api.hanzo.ai/v1/cloudflare/pages/projects/<project>/deployments \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "branch": "<branch>"
     }'

MCP reaches cloudflare through the cloudflare tool, which names its 29 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_cloudflare_d1_databases"
         }
       }
     }'

Cloudflare API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate namespaces NextCreate domains