Important: Only call parameters that you need. RichRelevance operates off a set of APIs that support many applications and clients concurrently. RichRelevance may update and enhance these APIs at any time.
Note: The URL requires the API key and parameter(s) to function properly. See below for more information on example URL requests.
User Profile Service requests must be signed using the standard OAuth 1.0 signature algorithm.
There are a number of libraries for most languages to implement OAuth. In the example below, we use the signpost library but you’re free to use your own library.
Client API Keys and Secrets
To create a client key and a client secret, contact your RichRelevance team, who will make sure you have access to the Relevance Cloud dashboard. Your clientApiKey will be accessible through the dashboard, but the clientSecret is a specific value for the clientApiKey and will need to be communicated via email or phone.
Client secrets need to be kept secure. They should never be shared, and only ever passed via HTTPS.
Some libraries require accessToken and accessTokenSecret values. If your library requires these, you can leave the values blank.
Note: All paramets are case sensitive.
|Name||Required or Optional||Description|
A unique key that identifies the site. Each RichRelevance client has a unique API key to separate data and traffic from other clients. This is provided by RichRelevance.
User ID. A unique string to identify each shopper (user). All shopper behavior is stored using this key. It is case-sensitive, and should be the same user ID sent to RichRelevance in other applications.
A comma separated list of the subset of profile fields to return. The known fields are described in more detail below, but are listed here for reference. The default value for this field is
In addition the value
Returns all fields for user 1870225 for instrumentation events for site with apiKey de89fba2959239b2.
Returns views and clicks for user 1870225 for instrumentation events for site with apiKey de89fba2959239b2.
Returns views and clicks for user the user that was last seen together with rrUserGuid 414c617d-ba8b-4735-90c9-9c526ac2fee5 for instrumentation events for site with apiKey de89fba2959239b2.
|userId||The merchant’s user ID for the profile.|
|mostRecentRRUserGuid||The most recent rrUserGuid seen with this profile. The intent is that this can be used for cookie synchronization across devices.|
|timeOfFirstEvent||The time of the first event recorded for this profile. This is not necessarily recoverable from the list of events in the profile because some of the older ones may have been discarded.|
|viewedItems||A list of the most recent itemView events of the user. These typically correspond to the user viewing an item page on the merchants website. For each event we return the sessionId, itemId (external ID), and timestamp of the event.|
|clickedItems||A list of the IDs of items the users most recently clicked on recommendations for. The sessionId and timestamp have the same meaning as for viewedItems.|
|searchedTerms||A list of the string the users most recently searched for. The sessionId and timestamp have the same meaning as for viewedItems.|
|viewedCategories||A list of the most recent categoryView events of the user. These typically correspond to views of the merchants category page. The sessionId and timestamp have the same meaning as for viewedItems.|
|viewedBrands||A list of the most recent brandView events of the user. These typically correspond to views of the merchant’s brand page. The sessionId and timestamp have the same meaning as for viewedItems.|
|addedToCartItems||A list of the most recent cartAdd events of the user. For each event we record the itemId, quantity and priceInCents. The sessionId and timestamp have the same meaning as for viewedItems.|
|orders||A list of the most recent purchase events of the user. For each event we record the itemId, quantity and priceInCents. The sessionId and timestamp have the same meaning as for viewedItems.|
|userSegments||A list of the most recent user segments seen in the instrumentation for this user. For this field we just return the seen segments with the most recent segments first.|
|userAttributes||A list of the most recent user attribute value pairs seen in the instrumentation.|
|verbNoun||A list of the most recent verb/noun events seen in the instrumentation.|
|countedEvents||A list of the most recent counted events seen in the instrumentation, the number of times it has been seen and the time of the most recent event.|