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.History endpoints
Get history for a specific watch
Retrieve all notifications sent for a single watch by its ID.Get history filtered by metadata
Retrieve notifications across watches that share a metadata key-value pair. At least onemetadata parameter is required for this endpoint.
Filter by metadata key-value pair. At least one metadata parameter is required. You can combine multiple pairs in a single request.Examples:
?metadata[campaign]=summer_sale?metadata[campaign]=summer_sale&metadata[priority]=high
Webhook notification formats
When a rule triggers, the API sends an HTTP POST request to the webhook URL you configured. Your endpoint should respond with a2xx status code.
Standard product change notification
Sent when a watch rule is triggered by a product field change such as a price drop or sale status update.Product unavailable notification
Sent when a watched product is removed from the Affiliate.com database. The watch is automatically deleted after this notification. Thefield value "__product__" indicates a watch-level event rather than a product field change.
Watch expiration notification
Sent when a watch reaches itsexpire_timestamp. The field value "__watch__" indicates a watch status change. After receiving this notification, use the PUT endpoint within 60 days to reactivate the watch with a new expire_timestamp, or create a new watch.
Metadata in webhooks
Every webhook notification includes themetadata object from the watch. This lets you route and process notifications programmatically using the tags you applied at watch creation — for example, dispatch notifications by campaign, priority, or any other dimension you track.
After you receive an expiration notification, the watch stops checking. To continue monitoring, call the PUT endpoint with
status: "active" and a new expire_timestamp within 60 days of expiration, or create a new watch. After 60 days the watch is removed.Response fields
Single-watch history response
Metadata-filtered history response
The metadata-filtered history endpoint returns a paginated list where eachdata item is a history record. The meta object includes total, from, to, current_page, last_page, per_page, and trace_id fields following the standard paginated envelope.