FruxonDocs
ApiFruxon channel

Injects a turn into the session as the chosen participant.

The run is queued; the reply arrives on the stream / messages endpoints. The participant must already be bound to the session's agent — an unbound sender is dropped and filed as an access request.

POST
/v1/tenants/{tenant}/fruxon/sessions/{session}/turns
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.

tenant*string

The tenant identifier

The participant to speak as and the turn text.

participantId?string
Formatuuid
text?string|null
asyncExecutionMode?string

How a step runs async operations (subtask, consult, human-approval, external callback).

Value in"UNSPECIFIED" | "AGENT_DECIDES" | "FORCE_AWAIT" | "FORCE_BACKGROUND"
[key: string]?never

Response Body

curl -X POST "https://api.fruxon.com/v1/tenants/string/fruxon/sessions/string/turns" \  -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
}