This is a zero-trust metadata write. The request must include a fresh item detailCheckpoint plus replacement signed summaries for both the source and target vaults.
The moved item's name, field labels, and websites remain metadata, so they are not end-to-end encrypted. Only field values are end-to-end encrypted.
When the source and target vaults use different DEKs, send reEncryptedFieldValues so the moved field values can be rewritten under the target vault's encryption context.
Headers
Header
Type
Required
Description
X-API-Key
string
Yes
Your machine API key
Content-Type
string
Yes
Must be application/json
Path Parameters
Parameter
Type
Required
Description
id
string
Yes
The unique identifier of the vault item to move
Request Body
Field
Type
Required
Description
detailCheckpoint
object
Yes
Signed replacement detail checkpoint for the moved item
sourceVaultSummaryCheckpoint
object
Yes
Signed replacement summary checkpoint for the source vault after the item leaves
targetVaultSummaryCheckpoint
object
Yes
Signed replacement summary checkpoint for the target vault after the item arrives
vaultId
string
Yes
The target vault ID
reEncryptedFieldValues
array
No
Optional field values re-encrypted for the target vault DEK
Re-Encrypted Field Value Object
Field
Type
Required
Description
fieldInstanceId
string
Yes
Field-instance ID being rewritten for the move
value
string
Yes
Client-encrypted value for the target vault DEK
Response
Success (200 OK)
No response body is returned on success.
Notes
This endpoint requires machine.vault.write plus ADMIN access to the target vault item.
Refresh both source and target vault summaries immediately before building the replacement checkpoints.