Read your catalogue and a product's market

Two calls cover the essentials: the state of your monitoring, and the market of one product.

Start for free

The state of your monitoring

This call answers the question an integration asks on a schedule: is my monitoring actually running? For each watched product it reports the matched marketplaces, the last successful read, and what failed.

It is the right call to run once a day to catch a product that stopped being found on a marketplace.

curl -H "Authorization: Bearer swp_your_key" \
     https://api.sweeprice.com/v1/products

A product's market

The competing offers collected, the best price, who holds the featured offer, and how it moved over the requested window.

The window is set with days. It stays bounded by your plan's history depth: asking for three hundred days on a plan that keeps thirty returns thirty, without an error.

curl -H "Authorization: Bearer swp_your_key" \
     "https://api.sweeprice.com/v1/products/PRODUCT_ID/market?days=30"

The comparable price

A seller can move margin between the listed price and the shipping cost. Comparing on the item price alone would reward that, so offers carry both separately and it is their sum that counts.

Frequently asked questions

Where does the product id come from?

From the first call, which lists your catalogue with its ids.

Why is an offer missing?

An offer priced in a currency other than the market's is dropped: the market's currency is the basis of every comparison. Used offers are dropped by default too.

How often are prices collected?

It depends on your plan, and on the marketplace. The terms of sale state those frequencies as maximums.

Shall we?

Take back control of your prices

Set up your first alert tonight. Tomorrow morning you will know exactly where you stand against your competitors.

Start for free

14-day free trial · No credit card · Cancel in one click