Skip to main content
Answered

Issue with translated_content after upgrading from API version 2.3 to 2.11


Hi everyone,

I've recently upgraded from Intercom API version 2.3 to 2.11 and I'm encountering some issues. I understand that sections are now deprecated and are accessed via collections. I'm able to update the section names using the new path help_center/collections/{id}.

However, when I try to use translated_content, I receive the following error:

{
    "type": "error.list",
    "request_id": "0001t87jrm46e5t3rtp0",
    "errors": [
        {
            "code": "not_found",
            "message": "Resource Not Found"
        }
    ]
}

 

Has anyone else experienced this issue or can provide guidance on how to correctly use translated_content in version 2.11? Any examples, workarounds, or documentation links would be highly appreciated.

Thanks in advance for your help!

 

Best answer by Vitalii Smol

I found the issue. translated_content wasn't working because additional languages were disabled in my workspace 😔. After enabling them, it works fine now.

Thanks for your help!

View original
Did this topic help you find an answer to your question?

2 replies

  • Author
  • New Participant
  • 1 reply
  • Answer
  • June 10, 2024

I found the issue. translated_content wasn't working because additional languages were disabled in my workspace 😔. After enabling them, it works fine now.

Thanks for your help!


bernice
Intercom Team
Forum|alt.badge.img+5
  • Intercom Team
  • 230 replies
  • June 12, 2024

Hey @Vitalii Smol 👋 Nice spot! Let me know if you have any further questions on this 🚀


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings