Available in VPC
Get secret details.
Request
This section describes the request format. The method and URI are as follows:
Method | URI |
---|---|
GET | /api/v1/secrets/{secretId} |
Request headers
For information about the headers common to all Secret Manager APIs, see Secret Manager request headers.
Request path parameters
You can use the following path parameters with your request:
Field | Type | Required | Description |
---|---|---|---|
secretId |
String | Required | Secret ID
|
Request example
The request example is as follows:
curl --location --request GET 'https://secretmanager.apigw.ntruss.com/api/v1/secrets/{secretId}' \
--header 'x-ncp-apigw-timestamp: {Timestamp}' \
--header 'x-ncp-iam-access-key: {Access Key}' \
--header 'x-ncp-apigw-signature-v2: {API Gateway Signature}'
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.secretId |
String | - | Secret ID |
data.secretName |
String | - | Secret name |
data.secretStatus |
String | - | Secret status
|
data.secretType |
String | - | Secret type
|
data.memo |
String | - | Secret description |
data.region |
String | - | Area code |
data.expectedDestroyDate |
Integer | - | Estimated secret destruction date and time (millisecond)
|
data.updateDate |
Integer | - | Secret update date and time (millisecond)
|
data.registerDate |
Integer | - | Secret creation date and time (millisecond)
|
data.autoRotationYN |
String | - | Whether to rotate automatically
|
data.autoRotationPeriod |
Integer | - | Secret automatic rotation cycle (day)
|
data.nextRotationDate |
Integer | - | Next rotation date and time (millisecond)
|
data.rotationPhase |
String | - | Current rotation phase
|
data.trigger |
Object | - | Information of the trigger |
data.trigger.id |
String | - | Trigger ID |
data.trigger.name |
String | - | Trigger name |
data.trigger.url |
String | - | Trigger URL |
data.protectionKey |
Object | - | Protection key information |
data.protectionKey.type |
String | - | Protection key type
|
data.protectionKey.kmsKeyTag |
String | - | KMS key tag |
data.protectionKey.kmsKeyName |
String | - | KMS key name |
Response status codes
For information about the HTTP status codes common to all Secret Manager APIs, see Secret Manager response status codes.
Response example
The response example is as follows:
{
"code": "SUCCESS",
"data": {
"secretId": "*****687685109842348f7358629bca2a6b2491e8c2352718e7d312b183*****",
"secretName": "test-***",
"secretStatus": "ENABLE",
"secretType": "BASIC",
"memo": "Secret Manager Description",
"region": "KR",
"updateDate": 1753159021411,
"registerDate": 1753065580243,
"autoRotationYN": "Y",
"autoRotationPeriod": 90,
"nextRotationDate": 1760842800000,
"rotationPhase": "NONE",
"trigger": {
"id": "*****",
"name": "test",
"url": "https://console.ncloud.com/vpcCloudFunctions/trigger/detail/test"
},
"protectionKey": {
"type": "USER_MANAGED_KEY",
"kmsKeyTag": "*****a8e99ef1ba49b9c190a0cb4f6fb20cff86dd3a3017fd6ee05aea8b*****",
"kmsKeyName": "test-***"
}
}
}