Monitors
Poll Social Fetch sources on a schedule and get a signed webhook when something new appears.
Monitors poll a watchable Social Fetch source (a Twitter profile's tweets, a subreddit's new posts, a TikTok search) and POST a signed webhook when something new appears. Social Fetch owns the schedule, diffing, and delivery.
Creating, listing, and updating monitors and webhook endpoints is free. Only the scheduled poll bills, at that operation's normal per-request price. See Billing for monitors.
The dashboard wizard covers the same flow, including a one-click test inbox.
Guides
Monitoring quickstart
Create a monitor, capture a signed delivery in a test inbox, then point it at your endpoint.
Receiving & verifying webhooks
Next.js, Hono, and Express handlers — and the raw-body gotcha that breaks signature checks.
Testing webhooks locally
socialfetch listen forwards signed events to localhost. No tunnel.
Delivery, retries & idempotency
Retry schedule, at-least-once delivery, and deduping on event id.
Billing for monitors
Per-check credits × schedule, dryRun previews, and plan limits.
Related
- Create a monitor —
POST /v1/monitorsand the rest of the Monitors API - Webhook endpoints — create destinations for signed deliveries
- Credits — metering, balance, and
402 - TypeScript SDK —
client.monitorsand@socialfetch/sdk/webhooks - Dashboard — create, pause, inspect deliveries