FruxonDocs
ApiFruxon channel

Answers a parked consult as the advisor — closes the loop in the sandbox.

WS-5 (docs/design/debug-console-consult-loopback.md): when a sandbox run is parked on a `consult_participant` call (surfaced as a `pending_consult` frame carrying the `operationId`), the operator submits the advisor's reply here. The consulting agent's suspended run resolves with it and resumes — its reply then arrives on the stream as a normal `reply`. Sandbox sessions only; nothing is delivered to a real channel.

POST
/v1/tenants/{tenant}/fruxon/sessions/{session}/consults/{consult}:answer

Authorization

Bearer
AuthorizationBearer <token>

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

In: header

Path Parameters

session*string

The session id returned by open.

consult*string

The parked consult operation id from the pending_consult frame.

Formatuuid
tenant*string

The tenant identifier

Request Body

The advisor's reply text and an optional outcome.

text?string|null

The advisor's reply (or the decline reason). Surfaced to the consulting agent as the consult result.

outcome?string|null

Optional outcome: omitted resolves as GoalMet; "declined" resolves as ParticipantDeclined.

[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/fruxon/sessions/string/consults/497f6eca-6276-4993-bfeb-53cbbbba6f08:answer" \  -H "Content-Type: application/json" \  -d '{}'
Empty
{
  "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
}