ClaudiusH wrote:     The easiest technical implementation would probably be using an SSO login option and the SSO token returning the "free/paid" information that is obtained from your CRM. This is what some of our customers use to separate a paid area in their communities that is customers only from the one available to the general public. Another possibility would be to have the (external, non Lithium) system that stores the user subscription details make calls into our Lithium REST API to grant and revoke roles as appropriate. The technical integration would be done in that third party system only, and leveraging our existing APIs. But yes, without SSO you will need to manage the mapping between your user accounts (in your systems) and the ones stored in Lithium. So I still vote for @ClaudiusH 's idea - also considering that SSO brings other benefits into the mix for communities in general. ... View more

Hi @kosmonaft   You will need to get in touch with the moderation team to obtain access or, if you are a Lithium customer, you can contact your Customer Success representative and they will be able to arrange it with you. If you are a partner working with one of our customers, you can ask them directly and they will be able to get it sorted out too!    Kind Regards, ... View more

This will actually return JSON : http://community.lithium.com/restapi/vc/users/login/Kronshage/kudos/received/count?restapi.response_format=json However their page does not specify if a specific JSON format is required, or if you can configure which element to look at. If a specific format is required, an endpoint will likely help. ... View more

Hey @Kronshage looks like the device only requires an input JSON endpoint that provides the counter value. I think if you create a Custom Studio Endpoint that returns the number of kudos for a given user (maybe accepting a user ID as a parameter) - it should do the trick. Thanks, ... View more

Hi @doug_ebay I'm pretty sure script tags are disabled for security reasons. I think a custom component in Studio (or a Custom Content Element that can be manipulated in Admin with your embed code) would be a way forward here. Thanks, ... View more