Leave a workspace

leave_workspace

Removes you from a workspace you were invited to, ending your access to every site in it.

POST /v1/leave_workspaceScopeworkspaces:writeDestructive

You lose access immediately and can only get back in by being invited again. It acts on the person the token belongs to, and the tool tells the client never to call it on somebody else's behalf.

An owner cannot leave their own workspace, and is refused with Workspace owner cannot leave workspace! Transfer ownership or delete workspace! Leaving also revokes the connectors you installed in that workspace and takes your account email off the forwarding addresses of its sites where you added it yourself. See Workspaces.

Request

Call it with a POST to https://api.modulify.ai/v1/leave_workspace, sending the inputs below as a JSON object. The token needs the workspaces:write scope.

This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.

curl -X POST https://api.modulify.ai/v1/leave_workspace \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"workspaceId":"WORKSPACE_ID"}'

Over MCP, the same method is the leave_workspace tool.

Inputs

Input	Type	Required	Description
`workspaceId`	string	Yes	The workspace to leave.

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.