Skip to content
Ishvana Ishvana Docs

Read recent hub communication activities

GET
/api/agent-communication/debug/communication-activities

Translate the hub’s message history into :class:CommunicationActivity records.

Per-message latency reflects real delivery timing: response_time_ms = (delivered_at - timestamp) in ms when the recipient has drained the message, else 0.0. status mirrors delivery — "completed" when delivered_at is set, "pending" when the message is still in the queue.

Query Parameters:

  • limit: Maximum activities to return (default 50).
  • agent_id: Optional — only include activities where this agent is the sender or recipient.

Returns:

  • :class:CommunicationActivitiesResponse with the filtered, limited list.

Raises:

  • HTTPException 503: Communication hub unavailable.
  • HTTPException 500: Unexpected hub error while reading the history.

Parameters

Section titled “ Parameters ”

Query Parameters

Section titled “Query Parameters ”
limit
Limit
integer
default: 50
agent_id
Any of:
string

Responses

Section titled “ Responses ”

200

Section titled “200 ”

Successful Response

CommunicationActivitiesResponse

Communication activities response model.

Provides log of communication activities between agents including message exchanges, consultations, and workflow coordination events. Used for activity monitoring and audit logging endpoints.

Usage: GET /api/agent-communication/activities returns this response model.

object
status
required
Status

Operation status

string
activities
required
Activities

Communication activity log

Array<object>
CommunicationActivity

Single entry in the communication hub activity log.

Fields:

  • id: hub-assigned activity identifier.
  • timestamp: ISO 8601 timestamp the activity was recorded.
  • sender_agent / recipient_agent: participating agent ids.
  • message_type: message classification ("direct", "broadcast", "consultation", etc.).
  • protocol: transport protocol tag.
  • status: activity outcome ("completed", "failed", "pending").
  • response_time_ms: round-trip latency in milliseconds.
  • success: whether the activity completed successfully.
  • metadata: optional extra context from the hub.
object
id
required
Id

Activity identifier

string
timestamp
required
Timestamp

ISO 8601 activity timestamp

string
senderAgent
required
Senderagent

Sending agent id

string
recipientAgent
required
Recipientagent

Receiving agent id

string
messageType
required
Messagetype

Message classification tag

string
protocol
required
Protocol

Transport protocol tag

string
status
required
Status

Activity outcome

string
responseTimeMs
required
Responsetimems

Round-trip latency in milliseconds

number
success
required
Success

Whether the activity succeeded

boolean
metadata
Any of:

Arbitrary JSON-shaped data. Flattened from a recursive type alias for wiki rendering — the live API accepts any JSON-compatible value (string, number, bool, null, array, or nested object).

object
key
additional properties
any
total
required
Total

Total activities

integer

422

Section titled “422 ”

Validation Error

HTTPValidationError
object
detail
Detail
Array<object>
ValidationError
object
loc
required
Location
Array
msg
required
Message
string
type
required
Error Type
string
input
Input
ctx
Context
object