Skip to main content
PATCH
/
api
/
v1
/
secrets
/
{secret_id}
Update a Secret
curl --request PATCH \
  --url https://api.intelligence.io.solutions/api/v1/secrets/{secret_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "secret_name": "<string>",
  "secret_value": "<string>",
  "tool_name": "<string>",
  "tool_arg": "<string>",
  "is_default_for_tool": true
}
'
{
  "detail": [
    {
      "loc": [
        "<string>"
      ],
      "msg": "<string>",
      "type": "<string>"
    }
  ]
}
This endpoint allows you to modify one or more properties of a previously registered secret, such as its value, linked tool, or default configuration. Only the fields provided in the request body will be updated, and omitted fields will remain unchanged.
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 system imposes an overall implementation-specific limit on the total size of stored secrets. If a request attempts to store a secret, or a combination of secrets, that exceeds this limit, the API will return an HTTP 413 (Payload Too Large) error.

​
Request body parameters:

secret_name – A user-defined identifier for the secret. This value is used to reference and manage the secret in subsequent operations. secret_value – The confidential value associated with the secret. This value is securely stored and made available to the designated tool when access is authorized. tool_name – The name of the single tool that is granted access to this secret. This field accepts only one tool identifier, not an array or list. tool_arg – The specific argument of the tool that this secret applies to. is_default_for_tool – A boolean flag specifying whether this secret should be automatically applied when the associated tool does not receive a value for the argument. This field is optional when using secrets in workflow YAML configurations, but required when defining secrets for built-in agents.

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

Body

application/json
​
secret_name
string | null
Required string length: 1 - 1024
​
secret_value
string | null
Required string length: 4 - 1024
​
tool_name
string | null
Required string length: 1 - 1024
​
tool_arg
string | null
Required string length: 1 - 1024
​
is_default_for_tool
boolean | null

Response

Successful Response