An Azure service that provides a hybrid, multi-cloud management platform for APIs.
If the response appears as raw streamed chunks instead of a single formatted response, the request is likely hitting a streamed pattern rather than a complete synchronous response.
For the Work IQ Chat API, the synchronous endpoint is:
POST https://workiq.svc.cloud.microsoft/rest/conversations/{conversationId}/chat
The streamed endpoint is different:
POST https://workiq.svc.cloud.microsoft/rest/conversations/{conversationId}/chatOverStream
The documented chat endpoint remains the synchronous endpoint, and chatOverStream is the streamed endpoint. The examples also show the same request body shape for chat, such as:
{
"message": {
"text": "What meeting do I have at 9 AM tomorrow morning?"
},
"locationHint": {
"timeZone": "America/New_York"
}
}
Checks to make:
- Verify the request is going to
/chat, not/chatOverStream. - Verify the client code is not treating the response as an event stream.
- If the output resembles incremental chunks, disable streaming behavior in the caller and use the synchronous request pattern.
There is no context indicating a documented API change where /chat now returns only raw streamed output by default.