|All request URLs in the document are relative to the application root. E.g. if the web application is deployed at http://10.0.0.10:8080/api and this document says to request /user, the full URL would be http://10.0.0.10:8080/api/user|
User's actions are usually tracked by external publication system. Currently we support one kind of action - which may be considered equivalent to "User has read" or "User is interested in". Depending on specifics of the content and audience, different systems may opt for different schema of registering user's actions - for example, user may be considered interested in an article if they commented on it or scrolled to second screen, or a combination of these.
Relation is established by a call like this one:where "recommend" is the name of the installed recommendation application.
If relation was established successfully, a similar result would be returned:
This is done by such call:
Result would be something like this:
User with ID of "user-1" has read article with ID of "doc-en-1" three times and article of ID of "doc-en-2" once.
As a result, we have numberOfReads=4 for the user and also popularity=3 and popularity=1 for the two articles. Popularity is global, it does not depend on the user we are asking about.
Use calls like these:
The "to" parameter is optional and defaults to present time.
Both "from" and "to" can take following values:
Single number is returned as a result. Note that if an user had read the same article twice, it would be considered two reads.
Let's say you want to build a chart for activity at your news site on daily basis for the last 10 days.
You could use this method to get reads for each day and plot them in a chart:
Another useful method is:
This method has the same "from" and "to" parameters as usagestats/userreads and returns top users with most reads. The "count" parameter shows size of the list to be returned.
The method has also these optional parameters: