Update secret

PUT/v1/servers/{serverId}/secrets/{secretId}

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
NameLocationTypeRequiredDescription
serverIdpathstringYesResource ID
secretIdpathstringYesSecret document ID or name
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
namestringNoHuman-readable name.
valuestringNoOptional replacement value. Omit to keep the existing encrypted value.
descriptionstringNoHuman-readable description.
metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Secret updatedapplication/json
FieldTypeRequiredDescription
serverIdstringNoResource ID.
secretobjectNo
secret.idstringNoUnique identifier.
secret.namestringNoHuman-readable name.
secret.descriptionstringNoHuman-readable description.
secret.maskedValuestringNo
secret.metadataobjectNoFree-form metadata object.
secret.createdAtstringNoISO 8601 timestamp.
secret.updatedAtstringNoISO 8601 timestamp.
secret.lastAccessedAtstringNo
secretsobject[]No
secrets[].idstringNoUnique identifier.
secrets[].namestringNoHuman-readable name.
secrets[].descriptionstringNoHuman-readable description.
secrets[].maskedValuestringNo
secrets[].metadataobjectNoFree-form metadata object.
secrets[].createdAtstringNoISO 8601 timestamp.
secrets[].updatedAtstringNoISO 8601 timestamp.
secrets[].lastAccessedAtstringNo
Update secret
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow