The Watchatic API is the JSON HTTP surface at https://api-v2.watchcollect.com (paths under /v2/...). It powers linking WhatsApp, choosing which groups feed product data, browsing messages and listings, and related settings.

​
Who this documentation is for

These pages are for clients integrating with the API (mobile, web, scripts, partner backends). For request and response shapes, use the API reference in the sidebar; it is generated from the published OpenAPI contract.

​
What you typically do first

  1. Obtain a Clerk bearer token for a signed-in user (same identity model as the Watchatic apps).
  2. Call authenticated endpoints with
    Authorization: Bearer <token> — see Authentication.
  3. Link a WhatsApp session (QR or OTP), then enable groups you want in the feed — see WAHA sessions and Group selection.
  4. Use messages, views, market, classification, alerts, and dashboard endpoints as needed — guides summarise workflows; the reference defines payloads.

​
Download the contract

The machine-readable spec (single file) is here:

​
Relationship to WhatsApp

Messages originate from WhatsApp sessions you link to the user account. The API exposes stable IDs and projections you query over HTTPS; it does not require you to talk to WhatsApp or WAHA directly for normal product integrations.
If you configure WAHA to send events into Watchatic, see WAHA webhook. That path uses a shared secret header — not end-user Clerk tokens.