At the moment, the GET Conversations endpoint supports returning translated text for outbound communications only via the “include_translations=true” query.
It would be great if this could be expanded to include inbound communications as well.
At the moment, the GET Conversations endpoint supports returning translated text for outbound communications only via the “include_translations=true” query.
It would be great if this could be expanded to include inbound communications as well.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.