Decline a secret request
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.
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.
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
Path Parameters
The request to decline.
1 <= lengthRequest Body
application/json
An optional note about why the request was declined.
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/secrets/requests/requests/string/decline" \ -H "Content-Type: application/json" \ -d '{}'{ "id": "string", "name": "string", "description": "string", "scope": "user", "projectId": "string", "status": "pending", "createdAt": "string"}List the caller's pending secret requests GET
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.
Ask the user for a secret POST
Creates a request for the user to enter a value in the dashboard. The value is never part of this request and never comes back through it: the user types it into a secure input, which stores it with `PUT /secrets/{name}` and marks the request `set`.