Home / Solutions / Consumer apps
Watchlists that actually fire
Price alerts look trivial until you are the one operating them: thousands of standing conditions, sellers that change shape, and users who notice immediately when an alert is late.
Consumer apps
One primitive
Create a watch with a condition and a callback. It fires when the condition is met, signed and idempotent, and it keeps working when a seller changes its layout.
Consumer apps
Context makes the notification worth sending
“Now $198” is a notification people mute. “Now $198 — lowest in 89 days” is one they open. The second costs one extra field.
Endpoints that do this
Where it lands in the API.
Watches
A standing condition on a product, a seller, a brand or a whole category.
Events
Six event types, signed on delivery and replayable by cursor. Every consumer eventually needs to backfill a gap.
Price context
Is this actually a good price? Percentile against the product's own history at that seller, time-weighted, with low, median and high.
Questions
Common questions.
How are callbacks secured?
Standard Webhooks: a versioned HMAC signature over id, timestamp and body, with the webhook-id doubling as your idempotency key.