Access to individual endpoints can be restricted per account. If a request to this endpoint returns
403 with error code endpoint_not_enabled and you expect to have access, contact your account representative.POST /v1/products/watches endpoint creates a new product watch. You define the products to monitor, the rules that trigger a notification, the webhook URL to notify, and optional filters and metadata. The watch starts checking immediately after creation (unless you set status: "paused").
Endpoint
Headers
Request body
A human-readable label for the watch. Used in webhook payloads and notification history responses.
The product identifiers to watch. For
"product" watches, supply up to 100 Affiliate.com product IDs. For "asin" watches, supply up to 10 Amazon ASINs. For "barcode" watches, supply exactly 1 barcode (UPC, EAN, GTIN, or ISBN).The conditions that trigger a notification. When multiple rules are defined, all rules must be met (AND logic) for the watch to trigger. Maximum 10 rules for
product and asin watches; exactly 1 rule for barcode watches.The initial status of the watch. Either
"active" (starts checking immediately) or "paused" (created but not checking).Narrow which product listings trigger the watch. Each filter has a
field, operator, and value. Supported fields: network.id, merchant.id, direct_url, currency. Multiple filters are combined with AND — all conditions must match. Not allowed for ASIN watches.Up to 16 custom key-value pairs to attach to the watch. Keys are max 64 characters; values are max 512 characters. Returned in all API responses and in every webhook notification.
UNIX timestamp when the watch should expire. Defaults to 90 days from creation. Maximum is 180 days from the current time. You receive a webhook notification when the watch expires.
Request examples
- Product ID watch
- ASIN watch
- Barcode watch
Watch two products and trigger when the price drops by 10% or the item goes on sale.
Webhook verification
When you create a watch with a"webhook" notification channel, the API immediately sends a test POST request to your endpoint to verify it is accessible. Your endpoint must return a 2xx HTTP status code. If verification fails, the watch creation is rejected. If your webhook requires authentication, set up a webhook authentication first and the test request will carry its access token.
The test payload has the same structure as a real notification:
Response
A successful request returns200 OK with a list of all your active watches, including the one just created.