FruxonDocs
UsersAPI Access

Reactivate a revoked service account.

Makes a revoked account active again under the same id, scope grant and Application binding, and mints it one new API key, whose plaintext secret is returned once. The keys it held when it was revoked stay revoked: whoever held them must be given the new one. Held to the same checks as a rotation, and refused for a platform system account, an account that is already active, and a deleted one (404). A signed-in administrator only: an API token is refused with `403 token_cannot_mint`.

POST
/v1/tenants/{tenant}/serviceAccounts/{serviceAccount}:reactivate
AuthorizationBearer <token>

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

In: header

Path Parameters

serviceAccount*string

The unique identifier of the service account.

tenant*string

The tenant identifier

Query Parameters

keyExpirationDays?integer

Lifetime of the new key in days, 1 to 365. Omit it for 365.

Formatint32

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/serviceAccounts/string:reactivate"
{
  "id": "00000000-0000-0000-0000-000000000000",
  "name": "string",
  "token": "string",
  "keyPrefix": "string",
  "scopes": [
    "string"
  ],
  "protectedApplicationIds": [
    "00000000-0000-0000-0000-000000000000"
  ],
  "droppedScopes": [
    "string"
  ],
  "createdAt": 0,
  "expiresAt": 0,
  "createdBy": "string"
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}