Monitors
Poll Social Fetch sources on a schedule and get a signed webhook when something new appears.
Monitors check accounts, public channels and searches on Twitter/X, Instagram, TikTok, Reddit, YouTube and LinkedIn on a schedule you choose. The first check records what's already there. After that, when a check finds new items, Social Fetch sends a signed webhook to your endpoint. It runs the schedule, works out what's new and retries failed deliveries, so you don't need your own scheduler. You can also read a monitor's events from the API without a webhook.
Monitors need a workspace that has bought credits at least once, with a credit pack or a subscription. Creating, editing and deleting monitors and webhook endpoints has no separate charge. Each successful check costs that source's normal per-request price, including a first check or one that finds nothing new. See Billing for monitors.
To try one without a server, send its events to a test inbox: an endpoint inside Social Fetch that shows each signed delivery in the app. The quickstart sets one up in the dashboard or with the API.
Related
- Create a monitor:
POST /v1/monitorsand the rest of the Monitors API - Webhook endpoints: where signed deliveries go
- Credits: metering, balance and
402 - TypeScript SDK:
client.monitorsand@socialfetch/sdk/webhooks - Dashboard: create and pause monitors, and look at deliveries
Guides
Monitoring quickstart
Create a monitor, open a signed delivery in a test inbox, then point it at your endpoint.
Receiving and verifying webhooks
Handlers for Next.js, Hono and Express, and the raw-body mistake that breaks signature checks.
Testing webhooks locally
socialfetch listen forwards signed events to localhost, with no tunnel.
Delivery, retries and idempotency
The retry schedule, at-least-once delivery and removing duplicates by event id.
Ad Tracker events
The Ad Tracker's new ads, stopped ads, briefs and weekly digest as signed webhooks.
Billing for monitors
Credits per check times the schedule, dryRun previews and plan limits.
Quickstart
Create an account and an API key, run your first lookup in the Playground and with cURL, then read the `{ data, meta }` response and the credits it cost.
Monitoring quickstart
Create a monitor, send its events to a test inbox and open a signed delivery, in the dashboard or with the API. No public URL needed.