OpenapiIntegrations
Requests a Pages rebuild and returns the queued build's status.
Requests a Pages rebuild and returns the queued build's status.
POST /v1/integrations/github/repos/{repo}/pages/builds
| Address | https://api.hanzo.ai/v1/integrations/github/repos/{repo}/pages/builds |
| Method | POST |
| Operation | post_integrations_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 | githubPagesBuildOut | accepted |
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
hanzo integrations github repos pages builds <repo>import { Configuration, IntegrationsApi } from 'hanzoai';
const api = new IntegrationsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIntegrationsGithubReposByRepoPagesBuilds({ repo: 'repo' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import IntegrationsApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = IntegrationsApi(client).post_integrations_github_repos_by_repo_pages_builds(repo='repo')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IntegrationsAPI.PostIntegrationsGithubReposByRepoPagesBuilds(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, integrations_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = integrations_api::post_integrations_github_repos_by_repo_pages_builds(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.IntegrationsApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new IntegrationsApi(client).postIntegrationsGithubReposByRepoPagesBuilds();curl -X POST https://api.hanzo.ai/v1/integrations/github/repos/<repo>/pages/builds \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches integrations through the integrations tool, which names its 45 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_connectors"
}
}
}'How is this guide?