List the caller's pending secret requests
Returns the requests the model has made for a value, newest first. Each one is a prompt the dashboard renders as a secure input: the user types the value there, never in chat. The model is told only whether a request is `pending`, `set`, or `declined`; it never learns the value.
Returns the requests the model has made for a value, newest first. Each one is a prompt the dashboard renders as a secure input: the user types the value there, never in chat. The model is told only whether a request is pending, set, or declined; it never learns the value.
Authorization
bearerAuth A bearer token. The Account routes accept a Privy access token; the MCP transport accepts an sk- API key issued by POST /account/api-keys.
In: header
Query Parameters
Filter by status. Omit for all of the caller's requests.
Value in
- "pending"
- "set"
- "declined"
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/secrets/requests/requests"{ "requests": [ { "id": "string", "name": "string", "description": "string", "scope": "user", "projectId": "string", "status": "pending", "createdAt": "string" } ]}Which projects a secret is usable from GET
Reports the projects a secret is usable from. A user-scoped secret is usable from every one of the caller's projects; a project-scoped secret is usable from exactly its own. Metadata only.
Decline a secret request POST
Records that the user declined to provide the value. The model is told `declined` and nothing else, and the request stops appearing in the dashboard's pending banner. Answering a request with a value is a `PUT /secrets/{name}`, which is where the value goes.