Loading...
Area: Episerver Product Recommendations
Applies to versions: 1.0 and higher (Personalization API)

Header information

Recommendations [hide]

Authentication information (such as site and siteToken, and channel) needs to be put in the request header (rather than the JSON payload defined in the subsequent sections).

ParametersDescription
site

Episerver client site code. This name will be the site code provided by Episerver which identifies the retailer's site, for example:

site: streamlycool
siteToken

Authentication token for the client. This is a token provided to the client by Episerver Technical Services, which needs to be included as part of the JSON data in every API call. For example:

siteToken: 1234abcd5678

A separate siteToken is issued for each channel. Take care to ensure that you are using the correct token for your channel.

channel

Access channel. It should be one of the following: store, mobileapp, tv, callcentre. For example:

channel : store

Get in touch with Episerver Technical Services in case more channels are needed. A separate siteToken is issued for each channel. Take care to ensure that you are using the correct token for your channel.

Content-Type

The MIME type for JSON text:

Content-Type: application/json
Do you find this information helpful? Please log in to provide feedback.

Last updated: Nov 06, 2017

Recommendations [hide]