patch_v1_sync_id
Patch updates one sync's mutable policy — direction, trigger and actor — in place.
Patch updates one sync's mutable policy — direction, trigger and actor — in place. The endpoints and the kind are immutable: re-pointing a sync is a delete and a create, so a link can never silently start syncing somewhere else. A field the request omits is left as it was. Changing the direction immediately reconciles the derived outbound mirror, so turning push off stops the upstream being written to rather than merely recording the intent.
| Tool | patch_v1_sync_id |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 4 |
| Operation | PATCH /v1/sync/{id} |
| Product | sync |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
actor | string | — | — | Actor is the loop-guard identity the sync writes as. Omitted, the stored actor stands. |
direction | string | — | — | Direction is both, pull, push or off. Omitted, the stored direction stands. |
id | string | — | — | ID is the sync to update, from the path. |
trigger | string | — | — | Trigger is webhook, poll or manual. Omitted, the stored trigger stands. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "patch_v1_sync_id",
"arguments": {
"actor": "<actor>",
"direction": "<direction>",
"id": "<id>",
"trigger": "<trigger>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_patch_v1_sync_id | PATCH /v1/sync/{id} | sync | Patch updates one sync's mutable policy — direction, trigger and actor — in place. |
The same capability over plain HTTP is in the sync API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?