Help Center> Data Encryption Workshop> API Reference> APIs> Secret Management APIs> Lifecycle Management> Querying the Secret List
View PDF

Querying the Secret List

Function

This API is used to query all the secrets created by the current user in the current project.

Constraints

The information returned via this API is the metadata of the secret and does not contain the secret value.

Debugging

You can debug this API in API Explorer.

URI

GET /v1/{project_id}/secrets

Table 1 URI parameter

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID
Table 2 Query parameters

Parameter

Mandatory

Type

Description

limit

No

String

Number of results returned on each page

Default value: 50

marker

No

String

Resource ID of pagination query. If the parameter is left blank, only resources on the first page are queried.

Request Parameter

Table 3 Request header parameter

Parameter

Mandatory

Type

Description

X-Auth-Token

Yes

String

User token.

It can be obtained by calling the IAM API (value of X-Subject-Token in the response header).

Response Parameters

Status code: 200

Table 4 Response body parameters

Parameter

Type

Description

secrets

Array of Secret objects

Secret list

page_info

PageInfo object

Pagination information
Table 5 Secret

Parameter

Type

Description

id

String

Secret ID

name

String

Secret name

state

String

Secret status. Its value can be:

ENABLED

DISABLED

PENDING_DELETE

FROZEN

kms_key_id

String

ID of the KMS CMK used to encrypt secret values

description

String

Description of a secret

create_time

Long

Secret creation time. The timestamp indicates the total seconds past the start of the epoch date (January 1, 1970).

update_time

Long

Time when a secret was last updated. The timestamp indicates the total seconds past the start of the epoch date (January 1, 1970).

scheduled_delete_time

Long

Time when a secret will be deleted as scheduled. The timestamp indicates the total seconds past the start of the epoch date (January 1, 1970).

If a secret is not in Pending deletion state, the value of this parameter is null.
Table 6 PageInfo

Parameter

Type

Description

next_marker

String

Address of the next page (starting resource ID of the next page) in a query. If this parameter is not specified, the next page is empty.

previous_marker

String

Address of the previous page (ending resource ID of the previous page) in a query.

current_count

Integer

Number of records returned on the current page

Status code: 400

Table 7 Response body parameters

Parameter

Type

Description

error_code

String

Error code

error_msg

String

Error description

Example Request

None

Example Response

Status code: 200

The request has succeeded.

{
  "secrets" : [ {
    "id" : "bb6a3d22-dc93-47ac-b5bd-88df7ad35f1e",
    "name" : "test",
    "state" : "ENABLED",
    "kms_key_id" : "b168fe00ff56492495a7d22974df2d0b",
    "description" : "description",
    "create_time" : 1581507580000,
    "update_time" : 1581507580000,
    "scheduled_delete_time" : 1581507580000
  } ],
  "page_info" : {
    "next_marker" : "bb6a3d22-dc93-47ac-b5bd-88df7ad35f1e",
    "previous_marker" : "bb6a3d22-dc93-47ac-b5bd-88df7ad35f1e",
    "current_count" : 1
  }
}

Status Code

Status Code

Description

200

The request has succeeded.

400

Error response

Error Code

For details, see Error Code.

Parent topic: Lifecycle Management