Replace pages

Sets or clears the custom domain (cname) and updates HTTPS enforcement, build type, or source.

PUT /v1/provider/github/repos/{repo}/pages

Addresshttps://api.hanzo.ai/v1/provider/github/repos/{repo}/pages
MethodPUT
Operationput_provider_github_repos_by_repo_pages
AuthAuthorization: Bearer $HANZO_API_KEY

Sets or clears the custom domain (cname) and updates HTTPS enforcement, build type, or source. ONLY the provided fields are sent to GitHub, so an update never resets a setting the caller did not mention.

Request

7 fields, body application/json (required).

FieldInTypeRequiredDescription
repopathstringyesRepo is the repository, from the :repo path segment.
branchbodystring—Branch switches the legacy source branch.
buildTypebodystring—BuildType switches the builder: "legacy" or "workflow".
cnamebodystring—CNAME is the custom domain.
httpsEnforcedbodyboolean—HTTPSEnforced toggles GitHub's enforce-HTTPS bit.
pathbodystring—Path is the source directory to pair with Branch: "/" (the default) or "/docs".
repobodystring—Repo is the repository, from the :repo path segment.

Response

StatusBodyMeaning
200provider.githubPagesUpdatedOutok
defaultproblem-detailsrefused

200 body — 2 fields.

FieldInTypeAlwaysDescription
repobodystring—Repo is the repository that was updated.
updatedbodyboolean—Updated is always true — a failure is an HTTP error, never this shape.

Failure carries the platform error shape — see Errors.

Examples

hanzo provider github repos pages replace <repo>
import { Configuration, ProviderApi } from 'hanzoai';

const api = new ProviderApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.putProviderGithubReposByRepoPages({ repo: 'repo', branch: "<branch>", buildType: "<buildType>" });
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).put_provider_github_repos_by_repo_pages(repo='repo', branch="<branch>", build_type="<buildType>")
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.ProviderAPI.PutProviderGithubReposByRepoPages(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::put_provider_github_repos_by_repo_pages(&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).putProviderGithubReposByRepoPages();
curl -X PUT https://api.hanzo.ai/v1/provider/github/repos/<repo>/pages \
  -H "Authorization: Bearer $HANZO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
       "branch": "<branch>",
       "buildType": "<buildType>"
     }'

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?