Add a reference to watch
You pass the product page address; the marketplace is derived from it, so you never name one and cannot name the wrong one.
The call takes the same path as the dashboard: your plan's reference count and its geographic perimeter apply identically.
curl -X POST -H "Authorization: Bearer swp_your_key" \
-H "Content-Type: application/json" \
-d '{"url":"https://www.amazon.fr/dp/B0XXXXXXX"}' \
https://api.sweeprice.com/v1/productsSet a floor and a ceiling
These are the only price values the API may write. The engine never recommends below a floor, so a wrong value stays bounded and visible.
Send one, the other, or both. A null value removes the bound.
curl -X PATCH -H "Authorization: Bearer swp_your_key" \
-H "Content-Type: application/json" \
-d '{"floorPrice":19.90,"ceilingPrice":39.90}' \
https://api.sweeprice.com/v1/products/PRODUCT_ID/boundsWhat the API does not change
Your repricing rules cannot be written through the API, and that is not an oversight. A rule written badly by a script, or invented by an agent, skews every recommendation until somebody notices. A floor price shows itself immediately.
Rules stay in the dashboard until you have a change log there to read.
Your allowance
Your plan includes a number of calls per month: ten thousand on Pro, one hundred thousand on Scale. The counter and the ceiling are shown in Settings, API access. Calls Claude makes through the connector draw on this same allowance: one tool call counts as one call.
Past it, calls receive a 429 until the next month. A 429 can also mean you are calling too fast for a moment: space your calls out, the key is not at fault.