REST API - Emojis

When creating content via REST, you can insert the unicode character sequences for specific emoticons and they will be interpreted before the content is committed into the Telligent Community token format of [emoticon:GUID]. You can also insert emoticons directly using the Telligent Community token format if you know the GUID identifier of the emoticon to be inserted.

When retrieving content, it appears the default content rendering mode removes the emoticons as you found. You can override the default rendering mode by adding the PostTarget querystring parameter to your REST request and specifying:

• "Web" -- this will render the content for direct website rendering. This is how content is rendered on the website via widgets. Emoticons will be processed into direct image references.
• "Raw" -- this is the unrendered/stored content and will return the Telligent Community token format for emoticons.

When creating content via REST, you can insert the unicode character sequences for specific emoticons and they will be interpreted before the content is committed into the Telligent Community token format of [emoticon:GUID]. You can also insert emoticons directly using the Telligent Community token format if you know the GUID identifier of the emoticon to be inserted.

When retrieving content, it appears the default content rendering mode removes the emoticons as you found. You can override the default rendering mode by adding the PostTarget querystring parameter to your REST request and specifying:

• "Web" -- this will render the content for direct website rendering. This is how content is rendered on the website via widgets. Emoticons will be processed into direct image references.
• "Raw" -- this is the unrendered/stored content and will return the Telligent Community token format for emoticons.

Ben Tiedt I looked at the documentation for fetching a forum thread, and for PostTarget the description is "Do not document this property".

ref: https://community.telligent.com/community/10/w/api-documentation/61549/show-forum-thread-rest-endpoint

Is there a reason for this?  More specifically, is there a reason why we shouldn't make use of it in tools that we expect to be around for years?

Thanks.

There are many use cases for specifying a rendering/post target in REST (which is why these parameters exist). We discussed the issue of "do not document this property" internally and agree that these parameters should be fully documented. They are safe to use and I've logged a bug to address the documentation: