Push · Firehose
Settings → WebhooksWebhooks
Subscribe to the signal types you care about. When a new row lands, VeilStrat POSTs the event to your HTTPS endpoint — realtime, not a nightly batch.
Firehose webhooks plus a capped REST scalpel — the same scored AI adoption signals as the dashboard, delivered where your team already works.
REST and firehose require the API Access add-on on Pro. Docs stay public.
POST outbound · Settings → Webhooks
GET /api/v1/companies/{id}
POST /api/v1/companies · signal_query: "signal:funding:30d"
GET /api/v1/slices?slice=funded-ai-hiring&countries=US
API surfaces
The dashboard is the human product. Pro teams get firehose webhooks and REST access to the same truth — for CRMs, agents, and internal pipelines.
Push · Firehose
Settings → WebhooksSubscribe to the signal types you care about. When a new row lands, VeilStrat POSTs the event to your HTTPS endpoint — realtime, not a nightly batch.
Pull · Scalpel
/api/v1/*After a webhook ping — or on a schedule — pull company dossiers, company search, or slice search. Capped and fresh by design, not a full-database export.
REST and firehose require the API Access add-on on Pro. Docs stay public.
Signal APIs
Six ways to subscribe, query, and enrich VeilStrat signals — each guide covers the automation angle and links to the technical docs.
Recommended loop
React to what just happened, then pull depth only for companies that matter — so monthly request and record budgets stay focused.
Pick signal types in Settings → Webhooks. Each write that matches your subscription arrives as an outbound POST with company.id and signalId.
Call GET /api/v1/companies/{id} for the same scored timeline the dashboard shows — identity, signals, AI adoption score, and slice context.
Use POST /api/v1/companies with a signal_query, or GET /api/v1/slices, to find more accounts in a buying window without burning monthly budgets on blind polls.
Authenticate with a team API key, subscribe to the types you care about, and enrich only the companies that just moved — without living in our UI.
REST and firehose require the API Access add-on on Pro. Docs stay public.