A hiring signal is a job posting read as a buying signal.
When a company posts for a Snowflake administrator, it has told you it is spending on Snowflake, in public, with budget attached, usually a quarter or two before any content-intent tool notices. This API turns that into three queries.
Three primitives
Watch an account
You already know who you want to sell to. The signal is that one of them started hiring for a role that implies the problem you solve.
company_name_or, posted_at_max_age_days
{
"company_name_or": ["Ramp", "Mercury", "Linear"],
"posted_at_max_age_days": 7
}Watch a skill market
You do not have a target list yet. The signal is that companies of a certain size started hiring for a certain skill, which tells you the market is moving before anyone announces it.
skills_or, min_employee_count, posted_at_max_age_days
{
"skills_or": ["snowflake", "dbt", "airflow"],
"min_employee_count": 200,
"posted_at_max_age_days": 14
}Push, not poll
A signal you find on Thursday for a posting that went live on Monday is not a signal, it is history. Webhooks deliver the posting when it appears.
job.created and job.closed webhooks, HMAC-SHA256 signed
POST https://your-app.example.com/hooks/jobspipe
X-JobsPipe-Signature: sha256=...
{ "event": "job.created", "data": { ... } }One request, no key
Companies over 200 people that posted for Snowflake or dbt in the last week. The sandbox takes the same filters and needs no authentication, though it answers with sample records.
curl -s -X POST https://api.jobspipe.dev/v1/sandbox/jobs/search \
-H 'content-type: application/json' \
-d '{
"skills_or": ["snowflake", "dbt"],
"min_employee_count": 200,
"posted_at_max_age_days": 7,
"limit": 25
}'Where this sits
Autobound and Signalbase sell the workflow around a signal: scoring it, routing it, and putting it in front of a rep with a drafted message. That is a different product from this one, and if what you want is a finished sales motion they are the better purchase. JobsPipe sells the layer underneath, the postings themselves as an API, for teams building their own scoring or feeding an agent. The wider category map, including where hiring signals fit against content intent and technographics, is in the intent data providers comparison.
This page is about running the queries yourself. If you would rather save the search once and be told when a new company matches it - by email, in Slack, or on a signed webhook - that is Signals, the managed version of the same filters.
FAQ
What is a hiring signal?
A new job posting read as a buying signal rather than as a job. If a company posts for a Snowflake administrator, that is public evidence they are standing up or expanding a Snowflake practice, published by the company itself, usually one to two quarters before any content-intent tool notices. The posting is the artifact; the signal is what it implies about spend and priority.
How is this different from intent data?
Most intent data infers interest from content consumption: someone at the company read an article, visited a comparison page, or appeared in a bidstream. Hiring signals are declarative rather than inferred, because the company published the posting deliberately and put budget behind it. They fire earlier and carry less noise, but they only cover things a company hires for.
Is this a replacement for Autobound or Signalbase?
No. Those products sell the workflow: scoring, sequencing, and getting a signal in front of a rep at the right moment. This is the layer underneath, the raw signal as an API. If you want a finished sales motion, buy the workflow. If you are building your own scoring or routing and want the postings themselves, buy the layer.
How fresh are the signals?
Collection runs continuously with a 6 to 24 hour cadence per source. For push delivery, job.created fires when the posting is first seen rather than on a batch schedule, which is the difference between reacting in hours and reacting next week.
Can an AI agent consume these signals directly?
Yes. The same filters are exposed as tools over MCP at jobspipe.dev/mcp, so an agent can ask which of a list of accounts started hiring this week without anyone writing an integration. That is the intended shape for agent-driven prospecting.
What does it cost?
One credit is one job returned. Free is 1,000 jobs a month, then $49/month for 25,000 and $349/month for 300,000, which is $1.16 per 1,000 against $1.50 at TheirStack. Webhooks are on paid plans.