Skip to main content
GET
/
v1
/
organizations
/
secrets
List Secrets
curl --request GET \
  --url https://api.mixpeek.com/v1/organizations/secrets
{
  "secrets": [
    "<string>"
  ],
  "count": 123
}

Documentation Index

Fetch the complete documentation index at: https://docs.mixpeek.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

Headers

​
Authorization
string

REQUIRED: Bearer token authentication using your API key. Format: 'Bearer sk_xxxxxxxxxxxxx'. You can create API keys in the Mixpeek dashboard under Organization Settings.

Examples:

"Bearer YOUR_API_KEY"

"Bearer YOUR_STRIPE_API_KEY"

Response

Successful Response

Response for listing secrets in the organization vault.

Returns ONLY secret names, never decrypted values. Use this endpoint to discover which secrets are configured in your organization.

Security:

  • Returns ONLY secret names, never values
  • Decrypted values never exposed via API
  • Use for auditing which secrets are configured

Use Cases:

  • Discover which secrets are configured
  • Audit secret inventory
  • Check if a secret exists before using it
  • Verify secret name spelling before referencing in api_call

Permissions: Requires READ permission to list secrets.

​
secrets
string[]
required

List of secret names in the organization vault. Only names are returned, never decrypted values. Use these names as references in api_call stage configuration. Names are unique within the organization. Empty list if no secrets are configured.

Examples:
["stripe_api_key", "github_token"]

["openai_api_key"]

[]
​
count
integer
required

Total number of secrets in the organization vault. This is the length of the secrets array. Useful for monitoring and auditing secret inventory.

Examples:

4

1

0