BASE
Live funding ingest — available on firehose the day the round lands
Each published round becomes one scored Funding signal — stage, amount, and investors when known. Subscribe on the firehose, enrich with the dossier, and time outreach the week capital lands.
REST and firehose require the API Access add-on on Pro. Docs stay public.
POST outbound · Settings → Webhooks · type=funding
POST /api/v1/companies · signal_query: "signal:funding:30d"
GET /api/v1/companies/{id}
At a glance
BASE
Live funding ingest — available on firehose the day the round lands
1:1
One published round → one Funding signal — never a merged blur
Journey
Spine for Funding + AI composition when hiring evidence arrives
/funding
Same store powers the funding list and company timelines
What you get via API
Funding signals are BASE rows from live funding ingest. Via the Signals API (Pro + API Access) you can receive each write on the firehose and pull the company dossier — label, confidence, stage, and amount context when disclosed.
Unlike news digests, the API exposes the same 1:1 timeline fact GTM teams see in VeilStrat — ready for CRM fields, alerts, and journey automation.
Integration loop
Capital windows close fast. Prefer firehose → dossier → CRM stamp over polling funding lists.
Enable Funding on your webhook. Each qualifying round POSTs company.id and signalId to your endpoint.
GET /api/v1/companies/{id} for stage, amount, investors when known, confidence, and related signals.
Write stage, amount, and a why-now note into Salesforce/HubSpot; notify the owner the same day.
Also subscribe to Funding + AI so composed stories fire when hiring catches up to the raise.
Example calls
Illustrative requests for capital-timed workflows. Full reference in the technical docs.
Search
Thin list for a capital window — enrich before outbound.
curl -s -X POST "${BASE_URL}/api/v1/companies" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "signal_query": "signal:funding:30d", "page": 1, "pageSize": 50 }'Enrich
Pull the round context and AI adoption score in one call.
curl -s "${BASE_URL}/api/v1/companies/COMPANY_UUID" \
-H "Authorization: Bearer YOUR_API_KEY"Slices
Combine slice filters with capital-backed AI windows when available.
curl -s "${BASE_URL}/api/v1/slices?slice=funded-ai-hiring&countries=US" \
-H "Authorization: Bearer YOUR_API_KEY"GTM automations
Turn the raise into a workflow the same day it publishes.
Timing
Alert owners with stage and amount so sequences start while the window is open.
Enrichment
Patch CRM funding fields from the dossier instead of manual research.
Journeys
Subscribe to the composed type so capital + hiring stories surface automatically.
Research
Use API for machines; send reps to /funding when they need a browsable list.
Capital timing
VeilStrat keeps one signal per published round. If you roll multiple raises into a single CRM field, you lose the timing clarity the API was designed to preserve — especially for Funding + AI aging.
Related
Jump to the buyer-facing signal guide, sibling APIs, or the technical docs.
Subscribe to Funding, enrich on every ping, and keep capital timing in the systems your team already opens every morning.
REST and firehose require the API Access add-on on Pro. Docs stay public.