Company Discovery Watcher - Crustdata Docs

A Company Discovery Watcher turns a Company Search filter into a recurring feed. Each run re-evaluates your filters against Crustdata’s database and delivers only the new matches to a webhook or Slack — a continuous, deduplicated feed, with no manual re-running.

POST https://api.crustdata.com/watch/company/search

Pricing: the first run is a free baseline (a sample of up to 5 matches), then 2 credits per new company delivered.

Common uses:

Sales / GTM — new accounts entering your ICP (e.g. Brazilian fintechs that crossed 30% headcount growth).
Market intelligence — companies that newly match a segment, funding stage, or growth band.
Sourcing — a fresh pipeline of recently founded or fast-growing companies in your target market.

A Discovery Watcher tracks companies that newly match a filter. To watch a known list of companies for profile changes instead, use the Company Entity Watcher.

How a watcher runs

Create the watch

POST your filters, a config (schedule + result cap), and one or more notifications channels. The response returns a watch id.

Baseline run (free)

The first run happens within seconds, delivering a free baseline sample of up to 5 matches so you can confirm the setup and payload shape. No credits charged.

Recurring runs

On the schedule you set (every_hours), the watcher re-runs your filters and delivers companies that are new or refreshed since the previous run, up to max_results_per_run. You’re charged per delivered company.

Each run delivers companies added or updated since the last run — a feed of movement within your filter set, not a one-time export. For the full current match set, use Company Search.

Request body

Field	Required	Description
`filters`	Yes	A filter tree, identical to Company Search. `{ "op": "and"\|"or", "conditions": [ { "field", "type", "value" } ] }`.
`config.trigger`	Yes	`{ "type": "interval", "every_hours": N }` — how often the watch runs (e.g. `1`, `6`, `24`, `168`).
`config.max_results_per_run`	No	Max records delivered per run. Default `25`. The first (baseline) run is always capped at 5.
`config.expires_at`	No	ISO date (`"2027-01-01"`). The watch auto-stops after this date.
`config.payload_delivery_type`	No	`"inline"` (default) or `"link"`. Where the records travel: inside the notification, or in one file the notification links to. See Payload delivery.
`notifications`	Yes	One or more delivery channels (see below).

The response returns the watch id:

{ "id": 46849 }

All examples require the headers authorization: Bearer YOUR_API_KEY, content-type: application/json, and x-api-version: 2025-11-01. For the full list of field values and operators, see the Company Search reference.

Company filter format

Watcher filters use the exact same syntax and fields as Company Search — no new filter language to learn. Each filter is a tree of leaf conditions combined with and / or operator groups:

Leaf condition — { "field": "...", "type": "...", "value": ... }, where field is a company attribute (e.g. headcount.total), type is the operator (e.g. =>, in, >), and value is what to match.
Operator group — { "op": "and" | "or", "conditions": [ ... ] }, where conditions is a list of leaf conditions or nested groups. and requires every condition, or any one; nest groups for compound logic.

Baseline limit: 500,000 companies. The baseline run only delivers 5, but it reads your entire match set to record what already exists. That read is capped at 500,000, and we check it when you create the watch, so a broader filter comes back 400 and you narrow it before anything runs. The cap applies to the baseline alone. Later runs deliver whatever newly matches, bounded by config.max_results_per_run.

Filters from other datasets

A company watch is not limited to company fields. Drop a job field or a person field into the same flat conditions list and the watch filters on the roles a company is hiring for, or the people it employs:

{
  "op": "and",
  "conditions": [
    { "field": "technographics.technologies.name", "type": "=",   "value": "Snowflake" },
    { "field": "job_details.title",                "type": "(.)", "value": "data engineer" }
  ]
}

Companies running Snowflake that are hiring a data engineer. Technology stack is not carried on job records and open roles are not carried on company records, so neither half of that is reachable from a single-dataset watch. You still receive companies, and you’re still charged 2 credits per company. Reading the other dataset is free, and nothing from it appears in your payload: to see the posting or the person that put a company in the feed, call POST /job/search or POST /person/search yourself with the delivered crustdata_company_id. See Cross-dataset filters for the join rules, the lookup fields for that follow-up call, the limits, and why negation (!=, not_in, (!)) is rejected on a filter from another dataset.

Recipes

Segment + headcount growth

New Brazilian software companies (50–500 employees) that grew headcount 30%+:

curl --request POST \
  --url https://api.crustdata.com/watch/company/search \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "filters": {
      "op": "and",
      "conditions": [
        { "field": "taxonomy.professional_network_industry", "type": "=", "value": "Software Development" },
        { "field": "locations.country", "type": "in", "value": ["Brazil"] },
        { "field": "headcount.total", "type": "=>", "value": 50 },
        { "field": "headcount.total", "type": "=<", "value": 500 },
        { "field": "headcount.growth_percent.6m", "type": "=>", "value": 30 }
      ]
    },
    "config": { "trigger": { "type": "interval", "every_hours": 24 }, "max_results_per_run": 25 },
    "notifications": [ { "type": "webhook", "url": "https://your-app.com/webhooks/crustdata" } ]
  }'

Well-funded companies in a country

New US companies that have raised more than $10M:

curl --request POST \
  --url https://api.crustdata.com/watch/company/search \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "filters": {
      "op": "and",
      "conditions": [
        { "field": "locations.country", "type": "in", "value": ["USA"] },
        { "field": "funding.total_investment_usd", "type": ">", "value": 10000000 }
      ]
    },
    "config": { "trigger": { "type": "interval", "every_hours": 24 } },
    "notifications": [ { "type": "slack", "webhook_url": "https://hooks.slack.com/services/T000/B000/XXXX" } ]
  }'

Recently founded companies

New companies founded after 2020:

curl --request POST \
  --url https://api.crustdata.com/watch/company/search \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "filters": {
      "op": "and",
      "conditions": [
        { "field": "basic_info.year_founded", "type": ">", "value": 2020 },
        { "field": "taxonomy.professional_network_industry", "type": "=", "value": "Software Development" }
      ]
    },
    "config": { "trigger": { "type": "interval", "every_hours": 168 } },
    "notifications": [ { "type": "webhook", "url": "https://your-app.com/webhooks/crustdata" } ]
  }'

High-growth mid-market

Software companies growing fast in the 200–2,000 range:

curl --request POST \
  --url https://api.crustdata.com/watch/company/search \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "filters": {
      "op": "and",
      "conditions": [
        { "field": "headcount.growth_percent.6m", "type": ">", "value": 15 },
        { "field": "headcount.total", "type": "=>", "value": 200 },
        { "field": "headcount.total", "type": "=<", "value": 2000 }
      ]
    },
    "config": { "trigger": { "type": "interval", "every_hours": 24 } },
    "notifications": [ { "type": "webhook", "url": "https://your-app.com/webhooks/crustdata" } ]
  }'

Delivery channels

Every watch needs at least one channel in notifications. Add one or more; matches fan out to all of them.

{ "type": "webhook", "url": "https://your-app.com/webhooks/crustdata", "headers": { "X-Watch-Name": "brazil-software-growth" } }

{ "type": "slack", "webhook_url": "https://hooks.slack.com/services/T000/B000/XXXX" }

[
  { "type": "webhook", "url": "https://your-app.com/webhooks/crustdata" },
  { "type": "slack", "webhook_url": "https://hooks.slack.com/services/T000/B000/XXXX" }
]

A Slack channel must be a genuine Slack incoming webhook (https://hooks.slack.com/services/…). Any other URL will fail delivery.

Where the records travel

By default a run’s companies arrive inside the notification, under results. Set config.payload_delivery_type to "link" and the body carries no records at all. It carries metadata.payload_delivery.url instead, a pre-signed S3 URL for one NDJSON file holding every record of that run. Switch when a run can outgrow what your receiver accepts. An AWS Lambda proxy integration caps a request at 6 MB and an ALB target at 1 MB, and an oversize body is refused whole.

curl --request PATCH \
  --url https://api.crustdata.com/watch/company/search/46849 \
  --header 'authorization: Bearer YOUR_API_KEY' \
  --header 'content-type: application/json' \
  --header 'x-api-version: 2025-11-01' \
  --data '{
    "config": {
      "trigger": { "type": "interval", "every_hours": 24 },
      "payload_delivery_type": "link"
    }
  }'

Every channel on the watch gets the same link, and the run-summary endpoint serves the same file. Read metadata.payload_delivery.type rather than testing for results: a link watch falls back to an inline body if the file cannot be written. See Payload delivery for the file format, the link lifetime, the run-summary shape, and the errors.

Manage a watch

curl --request GET \
  --url 'https://api.crustdata.com/watcher/watches/46849/runs?limit=20' \
  --header 'authorization: Bearer YOUR_API_KEY'

curl --request GET \
  --url https://api.crustdata.com/watcher/watches/46849/runs/54811/summary \
  --header 'authorization: Bearer YOUR_API_KEY'

curl --request DELETE \
  --url https://api.crustdata.com/watcher/watches/46849 \
  --header 'authorization: Bearer YOUR_API_KEY'

Pricing

	Credits
First run (baseline, up to 5 matches)	Free
Each new company delivered on later runs	2

You’re charged only for companies actually delivered — never for a run that finds nothing new. See Pricing for full details.

Company entity watchers

Watch a known list of companies for profile changes.

Company Search

Pull the full current set of matches in one call.

Company Search reference

Every filter field, operator, and value.

Pricing

Credit costs across all Crustdata endpoints.

​How a watcher runs

​Request body

​Company filter format

​Filters from other datasets

​Recipes

​Segment + headcount growth

​Well-funded companies in a country

​Recently founded companies

​High-growth mid-market

​Delivery channels

​Where the records travel

​Manage a watch

​Pricing

​Related

Company entity watchers

Company Search

Company Search reference

Pricing

How a watcher runs

Request body

Company filter format

Filters from other datasets

Recipes

Segment + headcount growth

Well-funded companies in a country

Recently founded companies

High-growth mid-market

Delivery channels

Where the records travel

Manage a watch

Pricing

Related