Create builds

Requests a Pages rebuild and returns the queued build's status.

POST /v1/provider/github/repos/{repo}/pages/builds

Provider → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/provider/github/repos/{repo}/pages/builds`
Method	`POST`
Operation	`post_provider_github_repos_by_repo_pages_builds`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Requests a Pages rebuild and returns the queued build's status. The build is queued AT GITHUB, not completed here, so the answer is 202 Accepted and its status is the one GitHub reported at queue time. 404 when the repository has no Pages site, or when the org's installation was not granted it.

Request

1 field.

Field	In	Type	Required	Description
`repo`	path	string	yes	Repo is the repository's short name within the org's installation, with no owner prefix (the owner is server-derived from the grant).

Response

Status	Body	Meaning
`202`	provider.githubPagesBuildOut	accepted
`default`	problem-details	refused

202 body — 3 fields.

Field	In	Type	Always	Description
`repo`	body	string	—	Repo is the repository the build was queued for.
`status`	body	string	—	Status is GitHub's build state at the moment it was queued ("queued").
`url`	body	string	—	URL is GitHub's API URL for the build, for polling it there.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo provider github repos pages builds <repo>

.ts

.py

.go

.rs

.java

import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postProviderGithubReposByRepoPagesBuilds({ repo: 'repo' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import ProviderApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = ProviderApi(client).post_provider_github_repos_by_repo_pages_builds(repo='repo')

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

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

use hanzo_client::apis::{configuration::Configuration, provider_api};

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

let result = provider_api::post_provider_github_repos_by_repo_pages_builds(&cfg, Default::default()).await?;

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

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

var result = new ProviderApi(client).postProviderGithubReposByRepoPagesBuilds();

curl -X POST https://api.hanzo.ai/v1/provider/github/repos/<repo>/pages/builds \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches provider through the provider tool, which names its 38 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_connections"
         }
       }
     }'

Provider API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousCreate backfill — POST /v1/provider/github/issues/backfill NextCreate pages