tenant.store.set_custom_fields

Set the declared custom fields on a store — MERGES by key: a key you do not name is left alone, and a null value removes one (an empty map is refused). Unlike cart.set_custom_fields, which replaces its bags, because this one is shared by the merchant, apps and the kernel (the store’s reserved vocabulary lives in it).

• Scope: tenant.store.write
• System: no
• Reachable from: POST /v1/commands/tenant.store.set_custom_fields — the tenant data face, with a tenant credential carrying tenant.store.write · MCP tool tenant.store.set_custom_fields · SDK client.call('tenant.store.set_custom_fields', …)
• Events: tenant.store.updated

Input (JSON Schema)

{
  "properties": {
    "custom_fields": {
      "additionalProperties": {},
      "propertyNames": {
        "type": "string"
      },
      "type": "object"
    },
    "store_id": {
      "minLength": 1,
      "type": "string"
    }
  },
  "required": [
    "store_id",
    "custom_fields"
  ],
  "type": "object"
}

Result (200)

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

Errors

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