====== Mobiplus Recommender API ======

We have 2 ways available to interface with the Mobiplus Recommendation Engine
\\
\\
====== API Mode ====== 
Download data from recommendation API:

  * **recommendation.js** file should be added to the website.
  * With the above API we can get Recommendations by giving parameters the id of the customer or the id of one or more products.
  * Also for the Recommendation Engine to work properly we need to send some basic data in every transaction.
  * Below are examples of the above functions.

===== Receive data from recommendation API. ===== 
Parameters of the following functions are the client's userid and the token which we provide.
In case we don't know the customer because they haven't signed in then we call the following function with NULL userid.
\\
\\
\\
**Receive data in JSON format**
<code>get_user_items_json(userid,token);</code>
\\
**Receive data in HTM format**
<code>get_user_items_html(userid,token);</code>
\\
\\
\\
===== Receive Recommendation based on products. =====
Parameters of the following functions are the code of the product(s).
In case we have more than 1 product, then the List should be a string with the ids of the products separated by a comma ",", e.g.\\
<code>list=108,109,150,286;</code>\\
<WRAP center round important 60%>
The token parameter is a string **which we give you**.
</WRAP>
\\
**Receive data in JSON format**
<code>get_history_items_json(list,token);</code>
\\
**Receive data in HTM format**
<code>get_history_items_html(list,token);</code>
\\
\\
\\
===== Send data to recommendation engine =====
Sending data during the transaction of a customer who has signed in or unknown.\\
In this case we call the function:\\
<code>item_click(userid,itemid,clicktype,sessionid,token);</code>
\\
||Parameter||Information||
||userid||Your customer's password (blank if they have not signed in).||
||itemid||Product code.||
||clicktype||A string with one of two values (basket, favorite).||
||basket||The price is given when the product is added to the shopping cart,||
||favorite||Given in case it has been added to the wish list.||
||Sessionid||It is the code of the session currently created for your customer|||
\\

----

\\
====== Operation Rest Web Service====== 
By calling the REST Web Service with the corresponding parameters we have the following possibilities:\\
The values of the parameters: clientid, projectid, date, will be given by us.\\
\\
===== Tokencreation =====
<WRAP center round important 60%>
Required for calling the other WebServices
</WRAP>

<code>/clienttoken?client_id= clientid&amp;project_id= projectid&amp;exp_date=date</code>
\\
\\
===== Recommendation Web Service: ===== 
<code>/reco?itemsid= itemsid&amp;userid= userid&amp;sessionid=sessionid&amp;token= token</code>
\\
||Parameter||Information||
||itemsid||In case of more than one product id there should be a "," comma separating the ids. E.g. itemsid = 108 or itemsid= 108,109,250,456|||
||userid||The parameter is the id of the registered user.||
||sessionid||The sessionid parameter is the sessionid that your client is currently using.||
||token||The parameter can be retrieved using the previous WS "clienttoken".||
<WRAP center round info 60%>
The itemsid and userid parameters can also be NULL.
</WRAP>
<WRAP center round important 60%>
The sessionid and clienttoken parameters are mandatory.
</WRAP>
\\
\\
__**Every time the customer clicks on a product then you should call the WS below giving the corresponding reason for clicking on a product.**__
<code>/clickinsert?userid= userid&amp;itemid=itemid&amp;clicktype=clicktype&amp;sessionid=sessionid&amp;token=token</code>
\\
||Parameter||Information||
||userid||The parameter is the id of the registered user.||
||itemid||The parameter is the id of the product.||
||clicktype||The parameter is the reason for clicking and can be one of the following values: **clicktype** = **click** or **favorite** or **wishlist** or **basket**||
<WRAP center round important 60%>
The sessionid parameter is the sessionid your client is currently using.
</WRAP>
<WRAP center round tip 60%>
The token parameter can be retrieved using the previous WS "clienttoken".
</WRAP>
<WRAP center round info 60%>
Only the userid parameter can be empty.
</WRAP>
<WRAP center round important 60%>
All other parameters are mandatory.
</WRAP>
\\
\\
===== New Product Sales ===== 
<code>/saleinsert?itemid=itemid&amp;userid=userid&amp;sessionid=sessionid&amp;purchaseprice=purchaseprice&amp;name=name&amp;timestamp=timestamp&amp;token=token</code>
\\
||Parameter||Information||
||itemid||The parameter is the id of the product.||
||userid||The parameter is the id of the registered user.||
||sessionid||The parameter is the sessionid, which your customer is currently using.||
||purchaseprice||The parameter is the price of the product.||
||name||The parameter is the name of the product.||
||timestamp||The parameter is the timestamp of the purchase. E.g. "2021-3-22 19:30:10".|||
||token||The parameter can be retrieved using the previous WS "clienttoken".||

<WRAP center round important 60%>
All other parameters are mandatory.
</WRAP>

----