integration_documentation:request_navigation

integration_documentation:request_navigation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
integration_documentation:request_navigation [2020/02/25 11:27]
florian
integration_documentation:request_navigation [2020/06/16 14:55] (current)
amil
Line 1: Line 1:
 ==== Integration ==== ==== Integration ====
  
-<note tip>Our library helps requesting the FINDOLOGIC ​API and also getting the data from the response and mapping it to corresponding objects. Read more at https://​github.com/​findologic/​findologic-api </​note>​+<note tip>Our library helps requesting the Findologic ​API and also getting the data from the response and mapping it to corresponding objects. Read more at https://​github.com/​findologic/​findologic-api </​note>​
  
 ---- ----
  
-The call to Navigation ​is made as usual via the FINDOLOGIC ​interface in the variant of XML:+The call for the navigation ​is made as usual via the Findologic ​interface in the variant of XML:
  
 <​code>​ <​code>​
Line 19: Line 19:
 In the first step, the available filters are queried and the preselected category is submitted via the selected parameter. In the first step, the available filters are queried and the preselected category is submitted via the selected parameter.
  
-<note important>​At this point, the results are generated not by FINDOLOGIC ​but by the shop, since FINDOLOGIC ​does not yet offer any benefit; therefore, query with count=0+<note important>​At this point, the results are generated not by Findologic ​but by the shop, since Findologic ​does not yet offer any benefit; therefore, query with count=0
 </​note>​ </​note>​
  
Line 26: Line 26:
 </​code>​ </​code>​
  
-The structure of requests to FINDOLOGIC ​is documented in detail here. Please ensure that you also provide the FINDOLOGIC ​required parameters with each call.+The structure of requests to Findologic ​is documented in detail here. Please ensure that you also provide the Findologic ​required parameters with each call.
  
 <note important>​Especially ensure that the IP of the requesting end customer is also supplied so that bot queries are not billed. <note important>​Especially ensure that the IP of the requesting end customer is also supplied so that bot queries are not billed.
Line 35: Line 35:
 The filters are output in the shop at the corresponding location. The output is executed in the module in the shop. The filters are output in the shop at the corresponding location. The output is executed in the module in the shop.
  
-The customer can now select a FINDOLOGIC ​filter with which the FINDOLOGIC ​results can be obtained in the next step.+The customer can now select a Findologic ​filter with which the Findologic ​results can be obtained in the next step.
  
 **Query of results** **Query of results**
  
-The customer has selected a filter. This is now transmitted to FINDOLOGIC+The customer has selected a filter. This is now transmitted to Findologic
  
 Example of preselected category "​Fashion"​ and selection of attribute "​Color=blue":​ Example of preselected category "​Fashion"​ and selection of attribute "​Color=blue":​