Hanzo
OpenapiTeam

SyncBots re-projects the caller org's agents as workspace members into EVERY…

SyncBots re-projects the caller org's agents as workspace members into EVERY workspace of the org, and removes the ones whose agent is gone.

POST /v1/team/bots/sync

Addresshttps://api.hanzo.ai/v1/team/bots/sync
MethodPOST
Operationpost_team_bots_sync
AuthAuthorization: Bearer $HANZO_API_KEY

SyncBots re-projects the caller org's agents as workspace members into EVERY workspace of the org, and removes the ones whose agent is gone. It is idempotent, and admin only: mutating a workspace's roster requires the gateway-minted admin flag, which a client can never forge. It answers how many roster entries the reconcile touched.

Request

The document declares no body for POST /v1/team/bots/sync. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask the MCP door's describe for post_team_bots_sync, which answers from the running route.

Response

StatusBodyMeaning
200botSyncok

200 body — 2 fields.

FieldInTypeAlwaysDescription
projectedbodyintegerProjected is how many roster entries the reconcile touched.
syncedbodybooleanSynced is true when the reconcile ran.

Failure carries the platform error shape — see Errors.

Examples

hanzo team bots sync

Team API · All Hanzo APIs · Interactive reference

How is this guide?

On this page