Freezing Kudos on a Topic on Classic
Hi all, Is there a way via either rest v1 or v2 (preferably the latter) to freeze the kudos for a given topic? I see that I can make a topic read only, but don't seen an obvious way to disable kudoing. Not sure if this is possible, but given gaps in the docs, I'm hoping that it's doable but that the field to update is not available with a select * query in the API browser. Thanks!json query syntax matches AND OR
Hello, I cannot find the full json query syntax documentation here. Thats wha I'm asking in this post: How does a json based query look like for AND matches in body text. I want to query all posts containing term1 AND term2 in their body. My query currently is this. How do I add the term2? [ { "messages":{ "fields":[ "id", "subject", "search_snippet", "body", "cover_image.view_href", "teaser", "view_href", "author", "conversation.last_post_time", "replies.count(*)", "kudos.sum(weight)", "metrics.views", "labels" ], "constraints":[ { "category.id":"DE", "conversation.style":"tkb", "body":{ "matches":"term1" }, "depth":0 } ], "sorts": [ "post_time desc" ], "limit":10, "subQueries":{ "labels":{ "fields":[ "text", "id" ] } } } } ]
Email missing in the bulk api
Hi Team could you please help me on the below activity i am missing couple of columns in the bulk api how can we get it https://api.lithium.com/lsi-data/v2/ Registration Status Registration Start Date Registration Completion Date Last Sign-in time Email Solutions Authored Solutions Accepted
list of all users subscribed to all board
I am using the below api to find the users permitted to a particular board: https://[COMMUNITY DOMAIN]/restapi/vc/boards/id/<board ID>/subscribers/email/board But the problem with above api and my use case is that I want to view the list of all the boards and its permitted users in one request. Whereas, the above api is only allowing to look for only a single board at a time. Is there a way in which I can get the list of all the boards in a community and it's subscribed users in a single hit?Using LiQL or SQL on Aurora instead of GraphQL?
We had an LiQL query we were using for years to surface community posts on our help center, and following the move to Aurora we need to update this to GraphQL. However, the developers on that team would prefer SQL/LiQL as their system is not set up for GraphQL. Is it possible to still use LiQL or SQL queries while on Aurora?Not receiving user email addresses from search endpoint
I have a script that queries the search endpoint for information about Khoros users. The API call looks roughly like /api/2.0/search?q=SELECT id, email FROM users LIMIT 10 When developing this script against one Khoros installation, I found that the Khoros user associated with the API request needed to have several "User Management" permissions granted to it in order to receive email addresses via this API call. (In particular, granting "View user reports in Admin Metrics", "Manage roles, user bans, and abuse notifications in admin and user profiles", and "Manage roles in user profiles" seemed to be sufficient.) However, when running this script against a second Khoros installation, I am not receiving back any email addresses. Every single user returned has the empty string as their email address, and I've tried querying several hundred (all of whom should have emails). For instance, a response may look similar to the below (redacted) sample: { "status": "success", "message": "", "http_code": 200, "data": { "type": "users", "list_item_type": "user", "size": 10, "items": [ { "type": "user", "id": "1000000", "email": "" }, ...additional users removed for brevity... ], "next_cursor": "AbCdEf" }, "metadata": {} } I have double-checked the roles and permissions for the Khoros user I'm using for this API request. What's the best way to debug? What are some other reasons that I may not be receiving any email addresses?Unable to retrieve users using v2 API
Unable to retrieve users from /api/2.0/search?q=SELECT * FROM users endpoint though it's returning 200 response. What could be the reason? Here is the response: { "status": "success", "message": "", "http_code": 200, "data": { "type": "users", "list_item_type": "user", "size": 0, "items": [] }, "metadata": {} }
