---
title: "Update Secret Value"
slug: "secretmanager-updatesecretvalue"
updated: 2026-10-08T04:19:40Z
published: 2026-10-08T04:19:40Z
canonical: "api.ncloud-docs.com/secretmanager-updatesecretvalue"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://api.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Update Secret Value

Available in VPC

Edit the secret value of the all secret stages. The value of a secret in the `REVOKE` (deletion requested) can't be changed.

## Request

This section describes the request format. The method and URI are as follows:

| Method | URI |
| --- | --- |
| PUT | /api/v1/secrets/{secretId}/values |

### Request headers

For information about the request headers common to all Secret Manager APIs, see [Secret Manager request headers](/docs/en/secretmanager-api-overview#%EC%9A%94%EC%B2%AD%ED%97%A4%EB%8D%94).

### Request path parameters

You can use the following path parameters with your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `secretId` | String | Required | Secret ID - See [Get Secret List](/docs/en/secretmanager-getsecretlist). |

### Request body

You can include the following data in the body of your request:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `previous` | String | - | Secret values previously used in the ACTIVE stage (PREVIOUS stage) - 1 to 100 key-value pairs. - Maximum 10,000 bytes. |
| `active` | String | - | Active secret values currently in use (ACTIVE stage) - 1 to 100 key-value pairs. - Maximum 10,000 bytes. |
| `pending` | String | - | Secret value for which a replacement has just begun and is awaiting completion (PENDING stage) - 1 to 100 key-value pairs. - Maximum 10,000 bytes. |

              Caution

              

Only the value entered in the request body is edited, and if the secret value of a secret stage is empty, the stage value is deleted. For more information on how to edit the secret value of a specific stage, see [Update Secret Stage Value](/docs/en/secretmanager-update-secret-stage-value).

### Request example

The request example is as follows:

```
curl --location --request PUT 'https://secretmanager.apigw.ntruss.com/api/v1/secrets/{secretId}/values' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}' \
--header 'Content-Type: application/json' \
--data '{
    "previous": "{\"abc\":\"cba\"}",
    "active": "{\"abc\":\"cba\"}",
    "pending": "{\"abc\":\"cba\"}"
}'
```

## Response

This section describes the response format.

### Response body

The response body includes the following data:

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `code` | String | - | Response code |
| `data` | Object | - | Response result |
| `data.encryptedSecretChain` | Object | - | Encrypted secret chain |
| `data.encryptedSecretChain.previous` | String | - | Previously used encrypted secret value (PREVIOUS stage) based on ACTIVE stage |
| `data.encryptedSecretChain.active` | String | - | Encrypted active secret value (ACTIVE stage) currently in normal use |
| `data.encryptedSecretChain.pending` | String | - | Encrypted secret value (PENDING stage) whose rotation has started anew and is waiting for the rotation to complete |

### Response status codes

For information about the response status codes common to all Secret Manager APIs, see [Secret Manager response status codes](/docs/en/secretmanager-api-overview#%EC%9D%91%EB%8B%B5%EC%83%81%ED%83%9C%EC%BD%94%EB%93%9C).

### Response example

The response example is as follows:

```
{
    "code": "SUCCESS",
    "data": {
        "encryptedSecretChain": {
            "previous": "ncpkms:v1:/*****ROoPnOWY7YmmKQFwuBuAaqnU1EdnJl2VORPtW2YBj/Kr1*****",
            "active": "ncpkms:v1:*****iseiMDx/Xs8VPsLviPnVLKKO9qkMHo8l5o7L0q9E/shi1*****=",
            "pending": "ncpkms:v1:*****GGkJ234mjiKOhmyYnUR20MTGl+MB/0u5yXjG1Ti6EZ9Gq*****="
        }
    }
}
```