Private beta. Watch is callable today with your normal API key on any paid plan, and watchers cost no ops; the free Founding plan cannot create them at all. It is not announced or generally available: the request and response shapes can change without notice, and there is no stability or support commitment, so do not build anything load-bearing on it yet. The roadmap is on
Coming Soon, and every release is announced in
the changelog.
`POST /v2/watch` is a website change detection API: you register a page
once, and a droplet-local scheduler re-renders it on a fixed cadence in
real headless Chrome, diffs each capture against the previous one, and
notifies you (by HMAC-signed webhook, email, or both) when the page
actually changes. It will replace the cron job plus diffing plus alerting
plumbing you would otherwise stand up around
[the perceive endpoint](/docs/endpoints/perceive.md): one record instead of a
scheduler, a storage bucket, and a comparison script.
Here is the smallest useful call. Send a URL and get back a watcher
scheduled to check hourly:
```bash
curl -X POST https://api.enconvert.com/v2/watch \
-H "X-API-Key: sk_your_private_key" \
-H "Content-Type: application/json" \
-d '{
"url": "https://example.com/pricing"
}'
```
The response is the full watcher record. It is `active` immediately, and
`next_check_at` is set to the poller's next tick:
```json
{
"watcher_id": "wat_3f9a2c1b8e7d4a6f90b1c2d3e4f5a6b7",
"url": "https://example.com/pricing",
"status": "active",
"frequency_minutes": 60,
"diff_mode": "auto",
"track_fields": null,
"webhook_url": null,
"notify_email": true,
"consecutive_errors": 0,
"checks_count": 0,
"last_check_at": null,
"next_check_at": "2026-06-24T18:31:07Z",
"last_change_at": null,
"created_at": "2026-06-24T18:31:07Z",
"updated_at": null
}
```
---
## Endpoints
| Method | Path | Purpose |
|--------|------|---------|
| `POST` | `/v2/watch` | Create a watcher for one URL. Returns `201`. |
| `GET` | `/v2/watch` | List this project's watchers, newest first. |
| `GET` | `/v2/watch/{watcher_id}` | Fetch one watcher's full record. |
| `GET` | `/v2/watch/{watcher_id}/snapshots` | List a watcher's check history, newest first. |
| `PATCH` | `/v2/watch/{watcher_id}` | Update cadence, diff settings, or pause/resume. |
| `DELETE` | `/v2/watch/{watcher_id}` | Soft-delete a watcher (idempotent). |
**Content-Type:** `application/json` on `POST` and `PATCH`.
---
## Authentication
Authenticate with a private key in the `X-API-Key` header for
server-to-server calls. This is the path every example below uses.
```http
X-API-Key: sk_your_private_key
```
Public keys with a JWT bearer token also work, using the same flow as
every other endpoint: generate a token with your `pk_` key, then send it
as `Authorization: Bearer