Secret lookup API reference

This user guide explains how to use and call the Public / Private Endpoint of Secrets Manager.

Pre-setup for Endpoint call

Describes the prerequisite configuration items required when calling the Secrets Manager endpoint.

Register Security Group’s Outbound Rule

To call the endpoint, you need to register an outbound rule in the security group.

To register the Outbound Rule of the Security Group, follow the steps below.

1. Click the All Services > Security > Secrets Manager menu. Navigate to the Service Home page of Secrets Manager.
2. Click the Secrets Manager menu on the Service Home page. Navigate to the Secrets Manager List page.
3. On the Secrets Manager List page, click the resource to view detailed information. You will be taken to the Secrets Manager Details page.
4. Check the URL information on the Secrets Manager Details page.
   • URL You can copy the public / private URL information from the URL item.
5. Use the nslookup command to check the IP to register in the Security Group.

nslookup <endpoint URL to call>

6. Security Group > Security Group List: Select the Security Group of the VM for which you want to set access control. Security Group Details page will be opened.
7. In the Security Group Details > Rules tab, click the Add Rule button. When the Add Rule window appears, enter the information below to add a rule.

   Item	Detailed description
   Target Input Method	CIDR Select
   Target address	Enter the IP address retrieved by nslookup
   Type	Select Destination Port/Type after entering protocol information Among protocols TCP select, enter 443 in TCP destination port
   Direction	Outbound rule Select
   Description	Enter Secrets Manager Public / Private Endpoint call rule

   Table. Security Group rule addition input items
8. Security Group rules Check that the rule you entered in the list has been added.

Register access control for Secrets Manager

You can register public/private access controls for Secrets Manager.

To configure the access control items of Secrets Manager, follow the steps below.

1. Click the All Services > Security > Secrets Manager menu. Go to the Service Home page of Secrets Manager.
2. Service Home page, click the Secrets Manager menu. Navigate to the Secrets Manager list page.
3. Secrets Manager list On the page, click the resource to view detailed information. Secrets Manager detail You will be taken to the page.
4. On the Secrets Manager Details page, click the edit icon of Public Access Control to add an allowed IP for Public Endpoint access.

• Public Access Control Edit Popup In the window, enter the IP and click the Add button. When addition is complete, click the Confirm button.
  • For security, adding a single IP is recommended, and up to 10 can be registered.
  • 0.0.0.0/24 - 0.0.0.0/32 can be registered, but be careful as it may be insecure.

5. On the Secrets Manager Details page, click the edit icon of Private Access Control to add a VM that allows Private Endpoint access.
   • In the Private Access Control Edit Popup window, select the resources to allow access and click the Add button. When the addition is complete, click the Confirm button.
   • If you do not set usage, you can access all subnet resources in the same region.

Secrets Manager API Call

Explains how to call the Secrets Manager API.

Check Secrets Manager URL information

All Services > Security > Secrets Manager > Secrets Manager Details page, check the URL information.

• URL You can copy public / private URL information from the item.

Secrets Manager Lookup API

get /v1/secret

## Description

Secret value lookup

## Parameters






  



Type
Name
Description
Schema




query
secretId (required)
Secret ID
 (Example : b3ed8b7637574255b83c274a6ed79426)
string




  Table. API Call Parameters Item





## Responses






  



Http Code
Description
Schema




200
OK
None


400
Bad Request
None


401
Unauthorized
None


403
IP Not Allowed
None


404
Not Found
None




  Table. API call Responses items





## Example HTTP request

### Request path

/v1/secret?secretId={secretId}

### Request header

“Accesskey = 2sd2gg=2agbdSD26svcD”, SecretKey = fsfsdf235f9U35sdgf35Xsf/qgsdgsdg326=sfsdr23rsef=

## Example HTTP response

### Response 200

{ “status”: “success”, “data”: { “key”: “value” }, “timestamp”: “2026-01-20T09:21:18.92730172” “}