Skip to main content
This guide strings together the full pipeline: test a query, create a webhook, schedule a monitor, and handle the results your endpoint receives. Each step links to its detailed reference if you need to go deeper.

Before you begin

  • Get a CatchAll API key from platform.newscatcherapi.com.
  • Set up a publicly accessible HTTPS endpoint that returns a 2xx and accepts a JSON POST, or use webhook.site for testing.
  • Optionally, install the CatchAll SDK for your language:

Build the feed

1

Test the query

Submit your query as a one-off job and review the results before committing it to a schedule. Keep the job_id; you reference it when creating the monitor.
Each record is structured according to an LLM-generated enrichment schema. A single record looks like this:
Field names inside enrichment are LLM-generated and vary between jobs, even for the same query. To lock the schema, define custom enrichments on the job or preview suggestions with POST /catchAll/initialize. See Dynamic schemas.
2

Create a webhook

A webhook is created once at the organization level, then attached to any number of jobs or monitors. Save the returned webhook.id.
Verify your endpoint is reachable before going live with POST /catchAll/webhooks/{webhook_id}/test. CatchAll also supports slack and teams webhook types. See Set up webhooks.
3

Schedule a monitor

A monitor re-runs your query on a schedule, deduplicates against previous runs, and delivers each run to the webhooks in webhook_ids.
The reference job’s end_date must be within the last 7 days, and the default minimum schedule interval is 24 hours, but can be more frequent depending on your subscription plan. See Configure monitors.
4

Handle the delivery

After each scheduled run, CatchAll sends a POST to your webhook URL. Return a 2xx within 5 seconds and process asynchronously.The payload:
A minimal receiver reads the structured fields directly:
Prefer no code? Point the webhook url at an n8n, Make, or Zapier webhook trigger and map records into a Slack message, a spreadsheet row, or a CRM record.

Adapt it

Swap the query for any event you want to watch: product recalls, executive moves, regulatory actions, competitor launches. The pipeline is identical: test the query, create a webhook, schedule a monitor, handle the delivery. To change which webhooks a monitor notifies, PATCH /catchAll/monitors/{monitor_id} with new webhook_ids.

See also