Skip to main content
GET
JavaScript
The workspace secrets in a workspace. An inventory, not a vault, values are redacted on every row.
Every spec.value comes back "". This lists what secrets exist and their names, so you can check that a ${NAME} your adapter references is stored. limit, cursor, and prefix (name starts-with) are the controls, no free-text query here. Pair the list with a tool set’s adapter headers to audit that every ${NAME} it uses has a matching secret before a sync fails on a missing one.

Create a workspace secret

Add one to the list.

Get a workspace secret

One secret’s metadata and lastUsedAt.

Store and use secrets

The three scopes and how ${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 whose secrets will be listed.

Example:

"workspace_01HXKD2E5NQM3T9AYWCF133E3Q"

Query Parameters

limit
integer<int32>

Maximum number of results to return

cursor
string

Pagination cursor from previous response

prefix
string

Filter expression (query param: prefix)

query
string

Free-form search query

labels
string

Filters by metadata labels. Comma-separated key=value pairs, e.g. "env=prod,team=ai". A resource matches only if every pair matches exactly (AND semantics).

sortOrder
string

Sort order for results (asc or desc by creation time)

includeInfo
boolean

When set to true you may use more of your alloted API rate-limit

Response

OK

items
object[]
pagination
object

Page carries cursor-based pagination state. There is no total: the cursor walks the result set without ever counting it, and a count would cost a second query on every list.