FruxonDocs
ApiSecrets

Rolls the published revision back to a prior historical revision.

The target revision's encrypted value becomes live immediately. Unlike LLM configs there is no draft to restore — secrets publish atomically on each rotation.

POST
/v1/tenants/{tenant}/secrets/{secret}:rollback

Authorization

Bearer
AuthorizationBearer <token>

JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.

In: header

Path Parameters

secret*string

The secret identifier (Guid).

Formatuuid
tenant*string

The tenant identifier

Request Body

The rollback payload identifying the target revision.

revisionId*string
Formatuuid
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/secrets/497f6eca-6276-4993-bfeb-53cbbbba6f08:rollback" \  -H "Content-Type: application/json" \  -d '{    "revisionId": "bae12d01-48af-47b3-9304-b09ef0081cd6"  }'
{
  "id": "00000000-0000-0000-0000-000000000000",
  "secretId": "00000000-0000-0000-0000-000000000000",
  "version": 0,
  "sensitivity": "STANDARD",
  "note": "string",
  "createdBy": "string",
  "createdAt": 0
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}