Skip to main content
GET
/
api
/
v1
/
secrets
/
{secret_id}
Get Secret Info
curl --request GET \
  --url https://api.intelligence.io.solutions/api/v1/secrets/{secret_id} \
  --header 'Authorization: Bearer <token>'
{
  "secret_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "user_id": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "secret_name": "<string>",
  "display": "<string>",
  "tool_name": "<string>",
  "tool_arg": "<string>",
  "is_default_for_tool": true,
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z"
}
This endpoint allows you to access detailed information about a registered secret, including its associated tool, argument, and configuration details. The actual secret value is never returned in the response for security reasons.
The API supports multiple authentication mechanisms, but only one needs to be provided per request. You may authenticate using any of the following headers, a browser-issued JWT token, an Authorization header, or an x-api-key header (io.net API key).
The display field returned in the response provides a partially masked representation of the secret value. It shows only the first and last few characters, ensuring that at least part of the value remains hidden. Complete visibility is only possible for very short secrets (typically 4 characters or fewer).

Authorizations

​
Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

​
token
string

JWT token

​
Authorization
string

io.net provided API Key

​
x-api-key
string

API key set by an SDK client

Path Parameters

​
secret_id
string<uuid>
required

Response

Successful Response

​
secret_id
string<uuid>
required
​
user_id
string<uuid>
required
​
secret_name
string
required
​
display
string | null
required
​
tool_name
string | null
required
​
tool_arg
string | null
required
​
is_default_for_tool
boolean
required
​
created_at
string<date-time>
required
​
updated_at
string<date-time>
required