Organization Secrets
Create Secret
Changed onCreate a new secret in organization vault.
Security:
- Secret value is encrypted at rest using Fernet encryption
- Encrypted using ENCRYPTION_KEY from environment
- Decrypted value is NEVER returned in API responses
- Only secret names are exposed in list operations
Use Cases:
- Store API keys for external services (Stripe, GitHub, etc.)
- Store authentication tokens for api_call retriever stage
- Store credentials for third-party integrations
Important:
- Secret names must be unique within organization
- Use update endpoint to modify existing secrets
- Delete and recreate if you forget the value
post/v1/organizations/secrets
Request
- Base URL: https://api.mixpeek.com
- URL: https://api.mixpeek.com/v1/organizations/secrets
- Auth: HTTP bearer
Request body
Example request
{
"description": "Store Stripe API key for payment processing",
"secret_name": "stripe_api_key",
"secret_value": "YOUR_STRIPE_API_KEY"
}Response
Successful Response
Example response
{
"created": true,
"description": "Secret created successfully",
"secret_name": "stripe_api_key"
}Changes
- warning
removed the optional property
from the response with the status - info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- warning
- breaking
removed the success response with the status
- info
added the success response with the status
- breaking