Do weak AI job posts arrive on the firehose?

No. Only Hiring signals that clear VeilStrat’s proprietary quality gate are written — and only written signals can fire webhooks or appear in REST results.

What authentication do I need?

REST uses Authorization: Bearer vs_… from Settings → API. Webhooks use a separate secret under Settings → Webhooks. You also need the API Access add-on on Pro.

Can Growth plans call the Hiring API?

API calls require Pro plus the API Access add-on. Without the add-on, /api/v1 routes return 403 plan_not_eligible. Docs pages remain public.

Hiring Signals API

BASE

Subscribe to AI-relevant hiring before it becomes a stale CRM note.

Wire quality-gated hiring rows into your stack — firehose when a new Hiring signal lands, then enrich with the company dossier. Same judgment as the dashboard: not every job post as intent.

Firehose on Hiring writes — realtime, not a nightly scrape
Search with signal_query patterns like signal:hiring:30d
Enrich via GET /api/v1/companies/{id}
Same quality gate as /signals/hiring — noise never ships

Read the API docs Sign up for Pro View signal guide

REST and firehose require the API Access add-on on Pro. Docs stay public.

hiring-api.previewPro

POST outbound · Settings → Webhooks · type=hiring

POST /api/v1/companies · signal_query: "signal:hiring:30d"

GET /api/v1/companies/{id}

At a glance

How this signal type shows up in the API

BASE

Written from live job ingest — available on firehose and REST

hiring

Filter company search and webhook subscriptions by this type

Dossier

Pull identity, signals, and AI adoption score after each ping

Capped

Prefer webhook + dossier over polling large hiring searches

What you get via API

Hiring as a first-class event in your systems

When VeilStrat writes a Hiring signal, Pro API subscribers with the API Access add-on can receive it on the firehose and pull the company dossier over REST. The payload reflects the same quality-gated, grouped openings the dashboard shows.

Use Hiring as the spine for outbound triggers, enrichment jobs, and agent workflows that should react to AI-relevant headcount — not raw board volume.

Subscribe to Hiring in Settings → Webhooks for outbound POSTs
Narrow REST search with a hiring-focused signal_query
Always enrich with GET /api/v1/companies/{id} after a firehose event

Integration loop

From Hiring write to action in your stack

Treat Hiring like any other realtime buying signal: subscribe, enrich, then expand only when the account clears your rules.

01
Subscribe to Hiring
Enable Hiring on your webhook endpoint. Each qualifying write POSTs company.id and signalId to your HTTPS URL.
02
Enrich the company
Call GET /api/v1/companies/{id} for identity, the Hiring row, AI adoption score, and slice membership.
03
Map role families into CRM
Write department, seniority, and confidence into Salesforce/HubSpot fields your sequences already read.
04
Expand hiring shortlists carefully
Use POST /api/v1/companies with a hiring signal_query only for net-new lists — page turns consume monthly budgets.

Example calls

Common Hiring API patterns

Illustrative requests — replace BASE_URL and YOUR_API_KEY. Full field notes live in the technical docs.

Companies with recent Hiring signals

Thin list for a buying window — enrich winners with the dossier.

curl -s -X POST "${BASE_URL}/api/v1/companies" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "signal_query": "signal:hiring:30d", "page": 1, "pageSize": 50 }'

Enrich

Company dossier after a webhook

Use the company.id from the firehose event — do not re-search blindly.

curl -s "${BASE_URL}/api/v1/companies/COMPANY_UUID" \
  -H "Authorization: Bearer YOUR_API_KEY"

Monitor

Health check (budget-exempt)

Safe for uptime probes — still requires a valid API key and API Access.

curl -s "${BASE_URL}/api/v1/health" \
  -H "Authorization: Bearer YOUR_API_KEY"

GTM automations

Where Hiring API hooks land

Pair the firehose with your existing ops stack so AI-relevant hiring becomes a workflow, not a tab.

CRM

Stamp accounts when AI roles open

Update opportunity stage or custom fields the moment a Hiring signal clears the gate.

Alerts

Ping the right pod in Slack

Route by department or confidence so AE and SDR channels stay high-signal.

Outbound

Trigger sequences with role evidence

Open with the hiring label and snapshot context instead of a generic AI pitch.

Agents

Feed internal research agents

Give copilots the dossier payload so they summarize why-now without scraping job boards.

Budget tip

Webhook first, search second

Polling large hiring searches burns monthly request and record budgets. Let the firehose tell you a Hiring row landed, then enrich with the company dossier.

Keep exploring this signal surface

Jump to the buyer-facing signal guide, sibling APIs, or the technical docs.

FAQ

Hiring API, answered

What teams ask before wiring Hiring into production.

/signals/hiring explains the product concept. This guide shows how to subscribe and query that same type via the Signals API. Schemas live at app.veilstrat.com/docs/api.

Put Hiring signalswhere your team already works.

Subscribe to Hiring, enrich on every ping, and keep outbound timed to AI-relevant roles — with the same confidence score as the dashboard.