Chat API

One conversation of mine, by id. myChatThreads was the only place a non-admin could read a thread's lock state, topic and counterparties, so a client opening a single conversation had to page the list and search it — both service apps scanned the first 100 rows. Past that the header fell back to a role name and the lock stopped being read, leaving the composer up on a closed thread until the send was refused. None when the caller is not a participant, which is the same answer as "no such thread" on purpose: a thread's existence is not something to confirm to someone who is not in it.

My conversations, newest activity first. Three queries regardless of page size: my participant rows, the threads they point at, and the other participants of those threads.

Fetch all chat messages for a specific order. # Authorization Requires TenantAdmin or PlatformAdmin role. # Arguments * order_id - The order ID to fetch messages for # Returns List of chat messages associated with the order's chat thread. Returns empty list if no chat thread exists for the order.