POSTing to /api/v2/conversations/{conversationId}/messages keeps throwing a 400 Bad Request when the dashboard automation tries to inject a canned reply mid-chat, and the requests.post() call fails immediately after the OAuth refresh cycle completes. We’ve been pushing {"to": {"id": "cust_uuid", "type": "user"}, "from": {"id": "agent_uuid", "type": "user"}, "text": "Hold please", "cannedResponseId": "cr_998877"} but the gateway validation layer just drops it with {"code": "invalid_request", "message": "Unsupported field in message object"}. Python logs confirm the conversation:write scope is active and the interval grouping logic handles paging fine, yet it’s weird how the payload structure keeps getting rejected and don’t see any workaround in the SDK docs either.
strip the cannedResponseId field. the API doesn’t accept it in the message body like that. you need to use the dedicated canned response endpoint or just send the plain text. trying to mix them causes validation errors every single time.