API Reference · Secrets
Roll a secret back to an earlier version
Re-point the secret's CURRENT value at an archived version's bytes. The sanitized data key (`key`) never changes, so every workload `secretEnv` reference keeps working unchanged — but a pod that already mounted the value keeps the old bytes until it restarts, exactly like any secret update. Nothing is destroyed: every version stays in the ladder, so a rollback can itself be rolled back. Versions whose archived bytes were pruned by retention (`rollbackable: false` in the list) return 422.
POST/v1/tenants/{name}/secrets/rollback
Authorization
x-api-keystringrequired
Your per-workspace API key, e.g. llc_AbC123…. Also accepted as Authorization: Bearer <key>. Mint keys on your workspace's API keys page — each key belongs to one workspace.
Path parameters
namestringrequired
Workspace (tenant) name.
Body
pathstringrequired
The secret path
toVersionintegerrequired
The version number to make current.
Response
200 — The rollback landed.
pathstring
currentVersioninteger
statusstring
e.g. rolled-back
notestring
Operational caveat — running pods keep the previously mounted value until they restart.
curl -X POST https://api.live-llm.com/v1/tenants/acme/secrets/rollback \
-H "x-api-key: $LIVELLM_KEY" \
-H "Content-Type: application/json" \
-d '{
"path": "/prod/tg-bot-token",
"toVersion": 2
}'Try itPOSThttps://api.live-llm.com/v1/tenants/{name}/secrets/rollback
Fill required path param: name.
Example response200
{
"path": "/prod/tg-bot-token",
"currentVersion": 4,
"status": "rolled_back",
"note": "v4 is a copy of v2"
}