curl --request PUT \
--url https://api.pipecat.daily.co/v1/secrets/{setName} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"secrets": [
{
"secretKey": "API_KEY",
"secretValue": "your-api-key"
},
{
"secretKey": "DATABASE_URL",
"secretValue": "postgresql://user:pass@host:5432/db"
}
],
"region": "us-west"
}
'{
"status": "OK",
"region": "us-west"
}Create or Update Secrets
PUT /secrets/ creates or updates a Pipecat Cloud secret set and its key-value pairs.
curl --request PUT \
--url https://api.pipecat.daily.co/v1/secrets/{setName} \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"secrets": [
{
"secretKey": "API_KEY",
"secretValue": "your-api-key"
},
{
"secretKey": "DATABASE_URL",
"secretValue": "postgresql://user:pass@host:5432/db"
}
],
"region": "us-west"
}
'{
"status": "OK",
"region": "us-west"
}Authorizations
Authentication requires a Pipecat Cloud Private API token.
Generate a Private API key from your Dashboard (Settings > API Keys > Private > Create key) and include it as a Bearer token in the Authorization header.
Path Parameters
Name of the secret set to create or update
3 - 63^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$Body
- Option 1
- Option 2
Array of secret key-value pairs
1Show child attributes
Show child attributes
The region where the secret set will be created. If not specified, defaults to the organization's default region. Secrets must be in the same region as the agents that use them. Cannot be changed after creation.
"us-west"
Response
Secret set accepted. Values have been stored and the set is being provisioned into the target region in the background. Poll GET /secrets/{setName} until status is ready before binding it to a deploy.