---
title: "Enable MPC custody on a vault"
method: POST
path: "/v1/vaults/{vault_id}/mpc"
tags: ["Vaults"]
---

# Enable MPC custody on a vault

`POST /v1/vaults/{vault_id}/mpc`

## Request

- Base URL: `https://api.1claw.co`
- URL: `https://api.1claw.co/v1/vaults/{vault_id}/mpc`
- Auth: HTTP bearer

Enable MPC custody on an existing vault. Requires Business or Enterprise plan.
Splits secret encryption keys across multiple providers using the specified
custody mode (e.g. 2-of-2, 2-of-3).

## Path parameters

- `vault_id` string, uuid, required

## Request body

- EnableMpcRequest
  - `mpc_custody` string, required: MPC custody mode (e.g. "2-of-2", "2-of-3")

## Response `200`

MPC custody enabled

- VaultResponse
  - `id` string, uuid, required
  - `name` string, required
  - `description` string
  - `created_by` string
  - `created_by_type` string
  - `created_at` string, date-time, required
  - `cmek_enabled` boolean: Whether client-managed encryption is enabled
  - `cmek_fingerprint` string: SHA-256 fingerprint of the CMEK key (64 hex chars)
  - `mpc_custody` string: MPC custody mode (e.g. "2-of-2", "2-of-3"), absent when MPC is not enabled
  - `mpc_threshold` integer: Number of shares required to reconstruct the key
  - `mpc_providers` string[]: List of MPC share providers (e.g. ["server", "client"])

## Other responses

- `400`: Invalid request
- `403`: Insufficient permissions
- `404`: Resource not found

---

[API](https://skmtc.dev/1claw/apis/1claw-api.md) · [All operations](https://skmtc.dev/1claw/apis/1claw-api/llms.txt) · [OpenAPI document](https://skmtc.dev/1claw/apis/1claw-api/revisions/5fa0918f3b41?raw)