List sync

Returns every sync link the caller's org has, each with its two endpoints, its direction and trigger policy, the time it last reconciled, and for a repo link its native copy on the forge — the address to clone it from, its default branch and whether it is in step.

GET /v1/sync

Sync → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/sync`
Method	`GET`
Operation	`get_sync`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Request

GET /v1/sync takes no parameters and no body — the credential is the whole request.

Response

Status	Body	Meaning
`200`	sync.syncList	ok
`default`	problem-details	refused

200 body — 25 fields.

Field	In	Type	Always	Description
`data`	body	sync.syncView[]	—	Data is the org's syncs, each with its endpoints, policy and last-synced time.
`data[].actor`	body	string	—	Actor is the identity a reconcile writes AS.
`data[].createdAt`	body	string	—	CreatedAt is when the link was first declared, RFC3339 in UTC.
`data[].direction`	body	string	—	Direction is which way work flows: "both", "pull" (target ← source), "push" (source → target), or "off" — which keeps the link declared and moves nothing.
`data[].id`	body	string	—	ID is the link's handle, derived from its source and target — which is what makes re-declaring the same pair an update rather than a duplicate.
`data[].kind`	body	string	—	Kind is what is being synced.
`data[].native`	body	sync.nativeView	—
`data[].native.advancedAt`	body	string	—	AdvancedAt is when an import or a push last moved one of its refs, RFC3339 in UTC.
`data[].native.branch`	body	string	—	Branch is the forge's default branch, which an import sets to the upstream's once that branch has landed.
`data[].native.clone`	body	string	—	Clone is the https address to clone it from.
`data[].native.sizeBytes`	body	integer (int64)	—	SizeBytes is the repository's size on the forge, in bytes.
`data[].native.ssh`	body	string	—	SSH is the ssh address to clone it from, when the forge serves one.
`data[].native.status`	body	string	—	Status is one of "synced" (the forge holds it and no ref is in conflict), "conflict" (an upstream ref diverged and the forge kept its own history), "pending" (the forge does not hold it yet) or "paused" (the link's direction is off).
`data[].native.url`	body	string	—	URL is the repository's page on the forge.
`data[].scope`	body	string	—	Scope is "repo" for a link to one repository, or "account" for a link to a whole GitHub account, which declares a repo link for every repository the account holds — the ones created later included.
`data[].source`	body	sync.endpointView	—
`data[].source.connector`	body	string	—	Connector names a connected account from the org's connector registry, when the endpoint reaches its provider through one.
`data[].source.locator`	body	string	—	Locator addresses the thing INSIDE that provider, in the provider's own terms — an https clone URL for a hosted forge, a bare repository name for hanzo-git.
`data[].source.provider`	body	string	—	Provider is the concrete integration: "github", "gitlab" or "hanzo-git".
`data[].target`	body	sync.endpointView	—
`data[].target.connector`	body	string	—	Connector names a connected account from the org's connector registry, when the endpoint reaches its provider through one.
`data[].target.locator`	body	string	—	Locator addresses the thing INSIDE that provider, in the provider's own terms — an https clone URL for a hosted forge, a bare repository name for hanzo-git.
`data[].target.provider`	body	string	—	Provider is the concrete integration: "github", "gitlab" or "hanzo-git".
`data[].trigger`	body	string	—	Trigger is what starts a reconcile: "webhook" (the provider tells us), "poll" (we ask on a schedule), or "manual" (only an explicit call).
`data[].updatedAt`	body	string	—	UpdatedAt is bumped by every reconcile, so it reads as the LAST-SYNCED time rather than the last edit.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo sync list

.ts

.py

.go

.rs

.java

import { Configuration, SyncApi } from 'hanzoai';

const api = new SyncApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getSync();

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

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = SyncApi(client).get_sync()

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

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

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

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

let result = sync_api::get_sync(&cfg, Default::default()).await?;

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

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

var result = new SyncApi(client).getSync();

curl https://api.hanzo.ai/v1/sync \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches sync through the sync tool, which names its 6 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_syncs"
         }
       }
     }'

Sync API · All Hanzo APIs · Interactive reference

Was this page useful?

PreviousGet sync NextUpdate sync