Getting the most seach keywords
I've been trying to access via Rest API to the top ten most search keyword, I try this: http://somcommunity.com/restapi/vc/metrics/name/top_search_terms and receive no response :( Do you know...
Forum Discussion
Ok, though I would advise against the path you're taking right now (for a sanity-check, please post what your top 10 Search terms are right now?).
To finalize your testing criteria, answer the following questions to generate a test list. You must make sure that you have the lists in order to prove a positive first. Get the list from Metrics directly, not the API:
If you're testing against stage, what are the top 10 terms for the certain period that you are selecting?
If you're testing against production, what are the top 10 terms for the certain time period you are selecting?
If you cant generate a list from the metrics console first, there is no way you're going to be able to generate a list from the API. So my advice is to at least establish that there is data there in the Web UI first.
I cant provide you a list of of the request working, because what you're asking for can only be provided if you we are both Admins on the same site. Meaning, I could not give you an example URL of a successful call here on the Lithosphere because you are not an Admin here. Likewise, I am not an Admin on your staging or Production site, so it is difficult to give you an example from your site.
If you are getting an "Access Denied" message, it is one of three things:
1. You are not an Admin
2. You are testing against stage and there is a restriction at the Apache level because of HTaccess
3. You do not have read REST API permissions set for an Admin (very unlikely, but still possible)
Thanks a lot for your answer.
I have checked that there is data in the Web UI first.
The search that I do from the Web UI is this (Reports -> User Search Reports):
(this search if for an entire week)
I can see at least 15 results. Then I copy the URL to use it through the REST API like this:
And the response is this:
<response status="success">
<metrics type="metrics" href="/metrics">
<metric name="board_views" type="long">543122</metric>
<metric name="message_views" type="long">27896002</metric>
<metric name="subscriptions_sent" type="long">3751</metric>
<metric name="threads_escalated" type="long">113</metric>
</metrics>
</response>
:(.
Could this be related with the REST API version that we are using?
Can I download the CSV using some sort of request?
Thanks again for your time.
Claudio.
Ok, I've been trying to get this info myself, with the following URLs and I'm getting "0" too.
(remember, I have admin permissions on the Lithosphere, so these types of URLs would have to be changed to your staging server to at least get success...but I'm looking into getting a result):
http://lithosphere.lithium.com/lithium/restapi/vc/metrics/name/userSearch_top_search_terms?date_start=2008-03-11&date_end=2009-06-12&restapi.format_detail=full_list_element&restapi.response_style=view&page=1&page_size=99
http://lithosphere.lithium.com/lithium/restapi/vc/metrics/name/userSearch_top_search_terms?date_start=2008-03-11&date_end=2009-06-12
http://lithosphere.lithium.com/lithium/restapi/vc/metrics/name/userSearch_top_search_terms
http://lithosphere.lithium.com/lithium/restapi/vc/metrics/name/userSearch_top_search_terms&date=1280127600000I'm reaching out to Lithium Developers to see if they can lend a hand. Unfortunately, I'm not a Developer so I can only bring the ball so far down the field. :(
Excellent, anything that I can do or test to solve this problem, please don't hesitate to ask.
Claudio.
Just adding my voice to this thread as someone who's also looking to pull search terms out of the API.
I've tested these endpoints and seen the same results (I have admin permissions on our community), so I'll be watching this thread for updates.
I know it's not the best use of the API, but I'm not going to be exposing the search terms to the community. We're going to be using the search terms in a daily community dashboard for management in order to identify new errors and problems that are popping up within our user base.
