Skip to main content
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.
The Product Watch API lets you monitor affiliate products for price changes, availability updates, and sale events. When a condition you define is met, the API sends a notification to your webhook. You define the products to watch, the rules that trigger a notification, and how long the watch remains active.

Watch types

Choose the watch type that matches how you identify your products.
Use target_type: "product" to watch products using internal Affiliate.com product IDs. This is the most flexible watch type and supports every rule, filter, and condition.Limits
  • Up to 100 product IDs per watch
  • Up to 10 rules per watch
Supported filters: network.id, merchant.id, direct_url, currencyUse this type when you have already searched for and identified products in the Affiliate.com database.

Watch behavior

Watches are checked every 6 hours. When a rule condition is satisfied during a check, the watch transitions to "completed" status and a notification is sent to your webhook. Completed watches do not resume automatically. To continue monitoring after a rule triggers, call the PUT endpoint and set status: "active" with updated rules or a new expire_timestamp. If a watched product becomes unavailable in the database, the watch is removed and you receive a final notification with field: "__product__" and new_value: "unavailable".

Ended watches

A watch that is "completed", "expired", or "error" has ended and no longer checks products. Ended watches are kept for 60 days from the date they ended. During that time you can reactivate one by calling the PUT endpoint with status: "active". After 60 days the watch is permanently removed. Requests to retrieve, update, or delete it return 404, and you need to create a new watch to resume monitoring. Notification history is also kept for 60 days, including for active watches.

Expiration policy

Every watch expires at a configurable timestamp. If you do not supply expire_timestamp, the watch expires 90 days from when you create it. When a watch reaches its expiration, you receive a webhook notification and the watch stops checking.

Metadata

You can attach up to 16 key-value pairs of custom metadata to each watch. Use metadata to tag watches with campaign names, product categories, priority levels, or any other context your application needs.
  • Key maximum length: 64 characters
  • Value maximum length: 512 characters
Metadata is returned in all API responses and in every webhook notification, so you can use it to route and process notifications programmatically. You can also filter watches by metadata using query parameters: ?metadata[campaign]=summer_sale.

Webhook authentication

If your webhook only accepts authenticated calls, add a webhook authentication in the dashboard under Account Settings → Webhook Authentication (available to accounts with API access). We exchange your OAuth2 client ID and secret for an access token (the client_credentials grant) and send that token with every request to your webhook. Without one, webhook calls are sent unauthenticated, as before.
  • The token request is a POST to your token URL with grant_type=client_credentials (plus scope and audience when set).
  • Each webhook call carries the token as Authorization: Bearer <access_token>. This covers watch notifications, retries, expiration notifications and the verification test, and it applies to your existing watches as soon as you save.
  • Tokens are reused until shortly before they expire. If your webhook answers 401, we fetch a new token and send the call once more.
  • When you save, we fetch a token with the details you entered. Nothing is saved if that fails, and the form shows the reason. Test on an existing entry fetches a token without calling your webhook.
  • Deleting a webhook authentication means calls to that address go out without any authentication.
The token URL and the webhook URL must both use https on port 443 and resolve to a public address. Certificates are verified and redirects are not followed.
A call that can’t be authenticated is not sent. It is recorded as a failed delivery and retried on the normal schedule. When you create or update a watch and the token can’t be fetched, the request returns 422 with a message naming the webhook authentication.After 3 failures in a row (a failed token request, or a 401 for a token we just fetched), the webhook authentication is paused for 15 minutes and we email your technical contact (or the account owner). Only a successful (2xx) webhook response resets the count. Once you’ve fixed the cause, a successful Test lifts the pause immediately.
An account can have up to 20 webhook authentications.

Rule types and conditions

Rules define what change triggers a notification. Each rule specifies a field (what to watch), a condition (how it must change), and optionally a threshold (by how much). Multiple rules all must match to trigger a notification (logical AND).

Supported conditions by field

The change condition triggers on any change and does not require a threshold. All other conditions require a threshold.

Threshold types

Allowed threshold values when threshold.type is "value": When threshold.type is "percentage": provide a number from 1–100.

Filters

You can optionally narrow which products trigger a watch using the filters array. Each filter specifies a field, an operator, and a value. Supported filter fields: network.id, merchant.id, direct_url, currency
Filters are not supported for ASIN watches. Including a filters array in an ASIN watch request will result in an error.

Available endpoints