Seeds the native todo with the EXISTING issues across the org's granted repos…
Seeds the native todo with the EXISTING issues across the org's granted repos (default state=open); the webhook keeps them live thereafter.
POST /v1/integrations/github/issues/backfill
| Address | https://api.hanzo.ai/v1/integrations/github/issues/backfill |
| Method | POST |
| Operation | post_integrations_github_issues_backfill |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Seeds the native todo with the EXISTING issues across the org's granted repos (default state=open); the webhook keeps them live thereafter. Org-scoped by the validated principal — a caller only ever backfills its OWN org. Synchronous + bounded (a total time budget and an issue cap) so it returns the counts directly; idempotent by ExtRef, so a re-run continues where a truncated pass left off and never duplicates.
Request
1 field, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
state | body | string | — | State is the GitHub issue state to walk: "open" (the default), "closed" or "all". |
Response
| Status | Body | Meaning |
|---|---|---|
200 | githubBackfillResult | ok |
200 body — 6 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
created | body | integer | — | Created is how many native issues this pass created. |
failed | body | integer | — | Failed is how many repos or issues errored; the pass continues past each. |
issues | body | integer | — | Issues is how many upstream issues were seen. |
repos | body | integer | — | Repos is how many granted repos were walked (archived/disabled are skipped). |
truncated | body | boolean | — | Truncated is set when the time budget or the issue cap stopped the pass early. |
updated | body | integer | — | Updated is how many existing native issues this pass refreshed. |
Failure carries the platform error shape — see Errors.
Examples
hanzo integrations github issues backfillimport { Configuration, IntegrationsApi } from 'hanzoai';
const api = new IntegrationsApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postIntegrationsGithubIssuesBackfill({ state: "<state>" });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_issues_backfill(state="<state>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.IntegrationsAPI.PostIntegrationsGithubIssuesBackfill(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_issues_backfill(&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).postIntegrationsGithubIssuesBackfill();curl -X POST https://api.hanzo.ai/v1/integrations/github/issues/backfill \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"state": "<state>"
}'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?