List secrets
const url = 'https://example.com/api/v1/secrets';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/secretsLists the secrets the caller may see, with masked fields, filtered to the read scope; admin-sensitive secrets appear only to the admin tier. Gated by secret:read, which the viewer floor does not carry (secret is a sensitive resource).
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
object
A URL to the JSON Schema for this object.
When true, only the admin tier may see or reveal this secret, regardless of placement
object
Whether the field is encrypted at rest and masked here
The owning entity’s id, the canonical handle; absent for a global owner
The secret_type name
The secret_type’s uuid, the stable form of secret_type
Example
{ "$schema": "/api/v1/schemas/ListSecretsOutputBody.json", "secrets": [ { "$schema": "/api/v1/schemas/SecretBody.json" } ]}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "/api/v1/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}