FruxonDocs
ApiEscalations

Acknowledges a degraded escalation so it leaves the "Awaiting a human" queue.

Use this when the operator has followed up on a degraded escalation out-of-band. The unhandled ledger is append-only and carries no "resolved" state, so acknowledging writes a small companion row that drops the escalation from the queue. The call is idempotent — a repeat is a no-op — and returns 404 when the id is not an unhandled-escalation event.

POST
/v1/tenants/{tenant}/escalations/unhandledEscalations/{unhandledEscalation}:acknowledge

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

unhandledEscalation*string

The unhandled-ledger event id (the eventId on a Degraded row).

Formatuuid
tenant*string

The tenant identifier

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/escalations/unhandledEscalations/497f6eca-6276-4993-bfeb-53cbbbba6f08:acknowledge"
Empty
Empty
Empty
{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}