customer_cluster.pin

Pin a customer into a cluster (idempotent). A pinned customer stays in the cluster even if the rule stops matching them — that is what pinning MEANS here, and it is why pins live in their own table.

• Scope: customer.admin.write
• System: no
• Reachable from: POST /v1/commands/customer_cluster.pin (tenant credential) · MCP tool customer_cluster.pin · SDK client.call('customer_cluster.pin', …)
• Events: customer_cluster.updated

Input (JSON Schema)

{
  "properties": {
    "cluster_id": {
      "minLength": 1,
      "type": "string"
    },
    "customer_id": {
      "minLength": 1,
      "type": "string"
    }
  },
  "required": [
    "cluster_id",
    "customer_id"
  ],
  "type": "object"
}

Result (200)

{
  "additionalProperties": false,
  "properties": {
    "cluster_id": {
      "type": "string"
    }
  },
  "required": [
    "cluster_id"
  ],
  "type": "object"
}

Errors

validation_failed (400) · unauthorized (401) · forbidden (403) · conflict (409) · internal (500)