pid
provided in this request (the returned value of the
selected Claimed Product
in the Product Search
step), ValueChecker will suggest similar products based on relevant
specifications, - the product that is selected during this step is
referred to as the Replacement Product. It’s worth noting that a
suggested Replacement Product could have the same pid
as the
Claimed Product
if the Claimed Product
is still for sale and in many cases the Replacement Product will share a
very similar or identical product_name with the
Claimed Product.
The response is a list of price groups, where each group is an array of
the prices found for one product, sorted first by Recommended Shop and
then Price.
grouped_prices
contains a list(s) of replacement product(s) full of
arrays of key value information pertaining to the shops where the
replacement product is available.total_price
value from the first product of the first group in the list
for the lowest available price from a recommended shop.
Example:grouped_prices.[0].[0].total_price
grouped_prices
list)
claimed_product
may contain an object called price
. This
contains an additional nested key again called price
(see Response
sample below). This is not to be confused with replacement prices in the
following object grouped_prices
. The Last Known Price is the most
recent valid price that ValueChecker has stored for the Claimed Product.
It can be used as historical data but should not be shown as the current
ValueChecker suggested replacement price.claimed_product
object if no
current valid prices for the Claimed Product
are found in the current market. It is also included in the
grouped_prices
object as a filtered_price
replacement if no other
current prices are available for any possible replacement.
We additionally return prices that have been filtered out
by us but can still be selected as a viable replacement product if the
user opts to do so.
filtered_price
.filtered_price = true
should
be hidden in your result set. These prices are included in the response
for special business cases and for your historical analysis as the
values may change often (for example: the “in_stock
” status can change
often - thereby switching the filtered status).
The 4 cases where filtered_price = true
(ValueChecker considers as a
filtered price but still returns the data in the response) are as
follows:
Property | Value | Description |
---|---|---|
in_stock | false | The shop indicates the product as not in stock. |
international | true | The shop marked the offer as not locally available |
is_refurbished | true | The product is marked as refurbished |
shop .shop_status | -1 | (in the shop array) <0 the shop itself has been filtered out 0 the shop is whitelisted 1 the shop is recommended (ranked higher) |
product_pic_url
in claimed_product
has been deprecated and will be removed in a future update.
Please use pic_url
instead.