Archives a vault. An archived vault is no longer used by cloud agents but remains readable through the API.
Request headers
|
Header |
Required |
Description |
|
|
Yes |
Bearer token used to authenticate the request. Format: |
Path parameters
|
Parameter |
Type |
Required |
Description |
|
|
string |
Yes |
The unique identifier of the vault to archive. |
Example request
curl -X POST "https://api.qoder.com.cn/api/v1/cloud/vaults/vault_019e3bb940277f0db05ab74291acf6ef/archive" \
-H "Authorization: Bearer $QODER_PAT"
Example response
HTTP 200 OK
{
"id": "vault_019e3bb940277f0db05ab74291acf6ef",
"type": "vault",
"display_name": "my-mcp-vault",
"status": "archived",
"metadata": {},
"archived_at": "2026-05-18T15:34:35.630693Z",
"created_at": "2026-05-18T15:34:16.874877Z",
"updated_at": "2026-05-18T15:34:35.630693Z"
}
Response field changes
After a successful archive:
-
statuschanges from"active"to"archived". -
An
archived_attimestamp is added. -
updated_atis set to the archive time.
Errors
|
HTTP |
Type |
Trigger |
|
401 |
|
The authentication token is missing or invalid. |
|
404 |
|
The specified vault does not exist or has been deleted. |
For the full error envelope, see Errors.