FruxonDocs
ApiEmbed configs

Mints a new identity signing secret, returning it once.

The secret the embedding site HMACs visitor identities with. Returned in plaintext here and nowhere else — every read path reports only whether one exists. Rotating invalidates every hash already issued against the previous secret, so the host must redeploy with the new one; that is also how a leaked secret is revoked, since the signature carries no expiry.

POST
/v1/tenants/{tenant}/agents/{agent}/embedConfigs/{embedConfig}:rotateIdentitySecret

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

agent*string

The agent identifier.

embedConfig*string

The embed config id.

tenant*string

The tenant identifier

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/agents/string/embedConfigs/string:rotateIdentitySecret"
{
  "identitySecret": "string"
}
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}