List the caller's secrets
Returns the caller's secrets by name and metadata. Values are never included at any depth. Pass `?projectId=` to include that project's secrets as well; a project secret and a user secret of the same name both appear, and the project one is the one that wins inside that project.
Returns the caller's secrets by name and metadata. Values are never included at any depth. Pass ?projectId= to include that project's secrets as well; a project secret and a user secret of the same name both appear, and the project one is the one that wins inside that project.
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
Include this project's secrets in the response alongside the user-scoped ones.
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/secrets"{ "secrets": [ { "id": "string", "name": "string", "scope": "user", "projectId": "string", "description": "string", "usage": "sandbox", "status": "string", "createdAt": "string", "updatedAt": "string", "lastUsedAt": "string" } ]}Read one Launch Kit GET
Returns a kit with the live state of each of its ten steps. The `launch` step reports `awaiting_signature` while the user has not signed: putty never holds a key, so the signature is the user's to give.
Read one secret's metadata GET
Returns one secret's metadata. There is no endpoint anywhere in the API that returns a value; this is the closest thing to one, and it stops at `lastUsedAt`. Pass `?projectId=` to read the project-scoped secret of that name rather than the user-scoped one.