Running into a weird issue with the web messaging guest endpoint. Trying to push typing indicators and read receipts directly via HTTP instead of relying on the frontend SDK. The docs mention hitting POST /api/v2/conversations/webmessaging/{conversationId}/messages with a custom payload, but the response keeps coming back as a 200 with an empty body. Agent side stays completely silent.
Here’s what I’m throwing at it:
{
"type": "typing",
"conversationId": "8f3a2c1d-4e5b-6c7d-8e9f-0a1b2c3d4e5f",
"from": { "id": "guest-abc-123" }
}
Dropped a console.log in the Node middleware just to be sure. Payload structure looks fine. I’ve already verified the bearer token scopes and swapped out to application/json headers. It’s still not working. The native SDK doesn’t complain about the payload shape, but the programmatic trigger just drops the message into the void. Response headers do include a location field pointing to a new message ID, yet the agent UI never updates.
Anyone managed to wire this up with raw fetch calls? The event bus shows the conversation state updating, but the typing animation never fires.