Put Secret

PUT /secrets/{name}

Role floor

Requires admin or above. The floor is a minimum, not a grant: scope filtering still applies on top of it, and a resource in another tenant answers 404 rather than 403.

Parameters

Name	In	Type		Notes
name	path	string	required	—

Request body — SecretWrite

Field	Type		Notes
value	string	required	min length 1 max length 65536
label	string | null	optional	max length 200
scope	workspace | organization | platform	optional	Default "workspace".

Responses

Status	Description	Body
200	Successful Response	SecretMeta
422	Validation Error	HTTPValidationError

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

The body shows the fields the schema always carries. Which combination is legal is a service rule the schema cannot express, so read the description above before copying this.

curl -X PUT https://your-deployment.example.com/secrets/{name} \
  -H "Authorization: Bearer $COBRE_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
       "value": "string"
     }'

Response — SecretMeta

Field	Type		Notes
name	string	required	—
label	string | null	optional	—
scope	workspace | organization | platform	required	—
organization_id	string (uuid) | null	optional	—
workspace_id	string (uuid) | null	optional	—
key_version	integer	required	—
is_active	boolean	required	—
created_at	string (date-time)	required	—
updated_at	string (date-time)	required	—