We’re pushing typing indicators to the web messaging guest endpoint but keep hitting a 400 Bad Request. The payload looks standard.
{“eventType”: “typing”, “conversationId”: “abc-123”}
Switched to read receipts with the exact same result. Verified the org scope and checked the admin UI routing settings. Nothing flags an issue. Tried adding an epoch timestamp manually. It still rejects the payload. Which header is actually required here? Logs just show validation failed. Don’t know what’s missing.