Update a watch
Changes the alert a watch is filed under, its notification configuration, its destination or whether it is enabled. Only the fields present in the body change; the property never does. Moving a watch where you already watch the property merges it into the watch already there, which is returned: that watch keeps its notification rules and takes the moved watch's rules for the event types it has none for and its destination can deliver; one with no rules takes the rules, destination and enabled value of a moved watch that has rules. Otherwise the watch already there keeps its own destination and enabled value, and those sent with the move are not applied to it. The watch returned keeps the prices it measures changes from, unless it takes a rule at a level, property or listing, it had none at, which restarts them from the current prices; the moved watch's are discarded. It returns 409 when both watches have rules and differ in whether they are enabled or in their destination.
Authorization
apiKey Value for the X-API-KEY header parameter.
In: header
Path Parameters
Watch identifier
The updated Watch resource
Response Body
curl -X PUT "https://example.com/watchlist/3fa85f64-5717-4562-b3fc-2c963f66afa6" \ -H "Content-Type: application/json" \ -d '{}'{ "propertyId": "0198f5c4-3b0a-7c1e-9d2f-4a5b6c7d8e9f", "alertId": "0198f5c4-1a2b-7c3d-8e4f-5a6b7c8d9e0f", "expired": false, "enabled": true, "notificationConfig": { "rules": [ { "eventType": "PRICE_CHANGE", "scope": "PROPERTY", "variationPercent": [ { "gte": -5, "lte": -3 } ] } ] }, "eventDestination": "https://example.com/", "signingKey": "whsec_abc123...", "signingKeyHint": "b75b1473", "id": "3fa85f64-5717-4562-b3fc-2c963f66afa6", "createdAt": "2026-01-15T10:30:00+00:00", "updatedAt": "2026-05-20T14:45:00+00:00"}