Skip to main content
GET
JavaScript
Read one workspace secret. You get its name, labels, and usage, never its value.
spec.value is write-only, so it reads back as "" on every fetch. This endpoint is for confirming a secret exists and seeing when it was last used, not for recovering the value. If you lost the value, rotate it. info.lastUsedAt populates once a tool call has resolved the secret; a secret never used has no timestamp yet.

Fetch by external ID, mind the normalization

Secrets take an external ID, but Cadenya normalizes it the way it normalizes the name: hyphens and spaces become underscores. Set externalId: "billing-key" and it stores as billing_key, so you resolve it as external_id:billing_key, not external_id:billing-key (which is a 404). Stick to underscores to avoid the surprise.

List workspace secrets

Every secret’s name, no values.

Update a workspace secret

Rotate the value you cannot read.

Store and use secrets

Where ${NAME} resolves.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

workspaceId
string
required

The workspace the secret belongs to.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

id
string
required

The secret to retrieve.

Example:

"wsecret_01HXKD2E5NQM3T9AYWCF586W5A"

Response

OK

metadata
object
required

Standard metadata for persistent, named resources (e.g., agents, tools, prompts)

spec
object
required
info
object

Workspace secret information