Returns one application's argocd ApplicationSyncWindowState — the answer to "is…
Returns one application's argocd ApplicationSyncWindowState — the answer to "is anything blocking a sync of this application right now?".
GET /v1/deploy/applications/{name}/syncwindows
| Address | https://api.hanzo.ai/v1/deploy/applications/{name}/syncwindows |
| Method | GET |
| Operation | get_deploy_applications_by_name_syncwindows |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Returns one application's argocd ApplicationSyncWindowState — the answer to "is anything blocking a sync of this application right now?".
This platform runs NO sync windows, so the answer is always the permissive empty one: canSync true, with no active and no assigned windows. The application is still resolved first, so a name that is not the caller's is not found rather than handed the static body — the endpoint discloses nothing about another tenant's fleet.
Request
1 field.
| Field | In | Type | Required | Description |
|---|---|---|---|---|
name | path | string | yes | Name is the application to read, from the path. |
Response
| Status | Body | Meaning |
|---|---|---|
200 | argoSyncWindows | ok |
200 body — 3 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
activeWindows | body | object[] | — | ActiveWindows are the sync windows in force right now. |
assignedWindows | body | object[] | — | AssignedWindows are the windows configured for this application at all, whether or not currently in force. |
canSync | body | boolean | — | CanSync is whether a sync would be permitted at this moment. Always true — with no windows there is nothing to deny it. |
Failure carries the platform error shape — see Errors.
Examples
hanzo deploy applications syncwindows <name>import { Configuration, DeployApi } from 'hanzoai';
const api = new DeployApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getDeployApplicationsByNameSyncwindows({ name: 'name' });from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import DeployApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = DeployApi(client).get_deploy_applications_by_name_syncwindows(name='name')cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.DeployAPI.GetDeployApplicationsByNameSyncwindows(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, deploy_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = deploy_api::get_deploy_applications_by_name_syncwindows(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.DeployApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new DeployApi(client).getDeployApplicationsByNameSyncwindows();curl https://api.hanzo.ai/v1/deploy/applications/<name>/syncwindows \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches deploy through the deploy tool, which names its 21 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": "get_deploy_account_can_i"
}
}
}'How is this guide?