...
Some otapi methods require customer's session parameter. It's necessary to get a session before working with logic for users. Initially, you need to get an anonymous session using http://docs.dev.otapi.net/en/Documentations/Method?name=GetAnonymousSession method so that the shopping cart, preferences (for example) and so on could be saved on it. All data will be automatically transferred if the previous anonymous session was transferred during authorization. Obtained session must be saved in the application memory and used later for all requests.
...
and parameter applicationType=MobileApplication/Android or applicationType=MobileApplication/iOS depends on system. Received data for each collection has a serial number for sorting <Order> 0 </Order>, you need to display collections on the application screen according to this sorting. It is recommended to show collections only from cache. Collections in cache must be updated in background: every 60 minutes, request BatchSearchRatingLists method and save result in the cache. When receiving a response, you need to check HasTranslateErrors node (http://docs.dev.otapi.net/en/Documentations/Type?name=BatchRatingListsSearchResultAnswer), if the node is "true", then you do not need to cache the response. You must check HasError node (http://docs.dev.otapi.net/en/Documentations/Type?name=RatingListSearchResult) for each RatingList element in the response, if the node is true, then this collection item does not need to be cached.
...
The current types of actions and their parameters purpose are listed below:
| Action type | Parameter |
|---|---|
Url | Absolute address of the link to open when you click banner |
Category | ID of the category that should be opened when clicking the banner |
Short categories menu
TODO:
...
The following properties should be used on recommended vendors page, in product card in vendor's block, for viewing all goods of vendor and for displaying information about the vendor:
Property | Description | Where to show | Comments |
|---|---|---|---|
| DisplayName | vendor name | everywhere | Thanks to this, website admin will be able to change names later, but nothing will change in Mobile Application logic. |
| DisplayPictureUrl | vendor image | everywhere | Only if available, otherwise there is an image stub in recommended vendors, do not display in other places. Thanks to this, website admin will be able to change images but nothing will change in Mobile Application logic. |
| Credit/Level | vendor rating from 1 to 20 | in product card | Only if available and more than 0, otherwise it does not need to be displayed. |
| Credit/TotalFeedbacks | number of feedbacks | in product card on vendor's page | Only if available and more than 0, otherwise it does not need to be displayed. |
| Credit/PositiveFeedbacks | number of positive feedbacks | in product card on vendor's page | Only if available and more than 0, otherwise it does not need to be displayed. Display as% of total reviews if available. |
| Scores/DeliveryScore | delivery scrore from 1.0 to 5.0 | in product card on vendor's page | Only if available and more than 0, otherwise it does not need to be displayed. |
| Scores/ItemScore | item score from 1.0 to 5.0 | in product card on vendor's page | Only if available and more than 0, otherwise it does not need to be displayed. |
| Scores/ServiceScore | service score from 1.0 to 5.0 | in product card on vendor's page | Only if available and more than 0, otherwise it does not need to be displayed. |
Search
Basic documentation on search.
...