COMPUTED
Built only from prior Hiring evidence — available via API when written
COMPUTED
React when AI hiring actually accelerates.
Velocity is computed from prior Hiring signals — one live row per company when the ramp is meaningful. Wire it so your stack notices acceleration, not just another opening.
- Firehose when a Velocity row writes or refreshes
- Pair with Hiring for full ramp context in the dossier
- Skip weak acceleration — empty ramps never ship
- Use for prioritization rules, not raw headcount deltas
REST and firehose require the API Access add-on on Pro. Docs stay public.
velocity-api.previewPro
POST outbound · Settings → Webhooks · type=velocity
POST /api/v1/companies · signal_query: "signal:velocity:30d"
GET /api/v1/companies/{id}
At a glance
How this signal type shows up in the API
Meaningful
Weak or empty acceleration does not create a Velocity row
1 / co
One live Velocity fact per company when the ramp clears judgment
Hiring
Read Hiring + Velocity together in the dossier for full context
What you get via API
Acceleration as an automation trigger
Velocity tells you whether AI-qualifying hiring is speeding up. When VeilStrat writes that row, the firehose can push it to your endpoint and REST can return it inside company search and dossiers — on Pro with API Access.
Use Velocity to re-rank accounts mid-cycle — the companies ramping AI seats, not only posting a single role.
- Subscribe specifically to Velocity if your play is ramp-sensitive
- Always pull the dossier — Hiring context sits beside Velocity
- Do not invent acceleration client-side; trust write-time judgment
Integration loop
Treat Velocity as a prioritization event
Velocity is rare by design. When it lands, enrich deeply and update scores — do not flood your CRM with every Hiring ping.
- 01
Subscribe only to Velocity
Keep this path quiet: enable Velocity on the firehose so only acceleration events hit scoring automations.
- 02
Enrich with Hiring context
GET /api/v1/companies/{id} returns Velocity plus underlying Hiring rows so agents see why the ramp matters.
- 03
Bump account priority
Write a score or tier field in your CRM; optionally page the owning AE when confidence is elevated.
- 04
Weekly ramp shortlist
Run a bounded Velocity signal_query for pipeline review — keep pageSize modest to protect budgets.
Example calls
Common Velocity API patterns
Illustrative requests for ramp-focused workflows. See docs for rate-limit headers and pagination.
Search
Companies with Velocity in-window
Build a shortlist of accounts whose AI hiring pace just cleared the bar.
curl -s -X POST "${BASE_URL}/api/v1/companies" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "signal_query": "signal:velocity:30d", "page": 1, "pageSize": 25 }'Enrich
Dossier after a Velocity webhook
Pull Hiring + Velocity together before updating CRM priority.
curl -s "${BASE_URL}/api/v1/companies/COMPANY_UUID" \
-H "Authorization: Bearer YOUR_API_KEY"Budgets
Check remaining API budget
GET /stats is exempt from request budgets — pace clients from remaining + resetUnix.
curl -s "${BASE_URL}/api/v1/stats" \
-H "Authorization: Bearer YOUR_API_KEY"GTM automations
Where Velocity API hooks land
Use acceleration as a scarce, high-intent trigger inside existing GTM systems.
Scoring
Lift ICP score on meaningful ramps
Add points only when Velocity writes — keep Hiring for broader awareness.
AE alert
Notify owners of accelerating accounts
Page the AE with dossier context when Velocity confidence is elevated.
Lists
Weekly ramp shortlist
Run a bounded Velocity search for pipeline review — not a continuous poll.
Agents
Explain the ramp to copilots
Feed dossier signals into an agent that drafts why-now notes for the AE.
Product rule
No row means no webhook
If acceleration is weak or empty, VeilStrat does not write Velocity — and the firehose stays quiet. Do not invent velocity client-side from Hiring counts.
Related
Keep exploring this signal surface
Jump to the buyer-facing signal guide, sibling APIs, or the technical docs.
FAQ
Velocity API, answered
Ramp-focused questions before you ship automations.
Velocity is computed only from prior Hiring signals. The dossier will typically show both; subscribe to Velocity when your workflow cares about acceleration specifically.
Prioritize accountswhose AI hiring just sped up.
Subscribe to Velocity, enrich on every ping, and keep scoring logic aligned with the same ramp judgment as the dashboard.
REST and firehose require the API Access add-on on Pro. Docs stay public.
© 2026 VeilStrat. All rights reserved.All systems operational