Hanzo
OpenapiCloudflare

Trigger a new Pages deployment for a project

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

Addresshttps://api.hanzo.ai/v1/cloudflare/pages/projects/{project}/deployments
MethodPOST
Operationpost_cloudflare_pages_projects_by_project_deployments
AuthAuthorization: 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.

FieldInTypeRequiredDescription
projectpathstringyes
branchbodystring

Response

StatusBodyMeaning
2XXSuccess

2XX body — 1 field.

FieldInTypeAlwaysDescription
(body)bodyanyyes

Failure carries the platform error shape — see Errors.

Examples

hanzo cloudflare pages projects deployments <project>

Cloudflare API · All Hanzo APIs · Interactive reference

How is this guide?

On this page