Skip to main content
The GET /v1/products/watches/{watch_id} endpoint returns the full details of a single product watch. You can also retrieve watches by metadata without knowing the watch ID — see query by metadata below.

Endpoint

Path parameters

string
required
The unique identifier of the watch to retrieve. You can find this value in the watch_id field returned by list, create, or update responses.

Headers

string
required
Bearer token for authentication. Format: Bearer {your_api_key}.

Example request

Response

Response fields

data object

string
The unique identifier for this watch.
string
The human-readable name assigned at creation.
string
The watch type: "product", "asin", or "barcode".
string
The product identifier being watched.
string
Current watch status: "active", "paused", or "completed". A watch becomes "completed" when a rule condition is met.
object
Custom key-value pairs attached to the watch.
object[]
The conditions that trigger a notification.
object[]
The configured notification channels.
object[]
Filters limiting which product listings can trigger the watch. Each object has field, operator, and value properties.
integer
UNIX timestamp of when the watch expires.
string
ISO 8601 datetime when the watch was created.
string | null
ISO 8601 datetime of the most recent check. null if the watch has not been checked yet.

meta object

string
Unique identifier for this request. Include this value when contacting support.

Query by metadata

If you tagged your watches with metadata at creation, you can retrieve them without knowing the watch ID. Use the same GET /v1/products/watches endpoint with metadata[key]=value query parameters.
You can combine multiple metadata filters:

Example

The response uses the same paginated format as list watches.