Hiring signals · Webhook API
Watch the accounts you sell to. Get a webhook when they post a new req.
You get the real posting with the ATS link, not an intent score. Reqbeat sends it to your webhook, Clay, n8n, or your agents. Free tier, no card.
$ curl api.reqbeat.com/v1/watches first signal in about 5 minutes
| TIME | COMPANY | ROLE | SOURCE |
|---|---|---|---|
| 14:09:02 | Braze | Platform Engineer | greenhouse.io |
| 14:07:48 | Clay | GTM Engineer | ashbyhq.com |
| 14:05:11 | Liqui Moly | Fullstack Developer | personio.com |
| 14:03:22 | Ekohealth | Revenue Ops Lead | lever.co |
| 14:01:57 | Flextronics | IT Administrator | pracuj.pl |
| 14:00:36 | Cloudgruppen | Account Manager | join.com |
native to Clay · n8n · MCP · webhooks · REST
Reqbeat watches. You act.
Add the accounts you sell to. Reqbeat scans the sources every 3 hours. When a target posts a new req, the webhook fires.
all pages and payloads, 7 regions EU to US
the real posting with the ATS link, not an intent score
Watch → Signal → Act
Three steps. Save a watch, get the webhook, act on the req.
Watch
Save a search for a company, or for a role and a country. One watch covers all postings that match.
curl -s -X POST 'https://api.reqbeat.com/v1/watches' \
-H "X-API-Key: $REQBEAT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"webhook_endpoint_id": 42, "company_id": 5512,
"event_types": ["opened"]}' Signal
Do not poll. Reqbeat pushes new matches to your webhook, signed and deduplicated. You pay only for accepted deliveries.
{
"envelope": "reqbeat.webhook.v1",
"idempotency_key": "watch:311:event:184203",
"repeat_of": null,
"events": [{
"event_type": "opened",
"title": "Senior Platform Software Engineer I",
"company_id": 5512,
"company_name": "Braze",
"url": "https://boards.greenhouse.io/braze/jobs/7210045",
"board": "greenhouse",
"country": "United Kingdom",
"event_seq": 184203
}],
"…": "…"
} Act
Start the sequence, enrich the row, or brief the agent. Use REST, MCP, Clay, or n8n on the day the req goes live.
{ "mcpServers": {
"reqbeat": { "url": "https://mcp.reqbeat.com/mcp" }
} }
// then ask your agent:
// "who is hiring for my ICP this week?" One detected req. Four ways into your stack.
New matches land as rows
"Watch this company for new reqs"
Trigger node, deduplicated
on opened → enrich → send
Ask your agent directly
"who is hiring for my ICP this week?"
Pull it into anything
POST /v1/watches · signed webhooks
Steal a recipe
These plays run on Reqbeat data today. Our own outbound is one of them.
Email the hiring manager same-day
A watch fires → Clay enriches the company → your sequence sends while the req is hours old.
read the recipe →An agent that qualifies accounts by hiring pulse
Your agent calls who_is_hiring_for and ranks accounts by velocity, direction and surge flag.
read the recipe →Fresh segments for client campaigns, weekly
One pull per client ICP per week. A segment nobody else emails yet.
read the recipe →The motion behind the account
One call gives a company's hiring pulse: new roles in 30 days, velocity, direction, and a surge flag. The data comes from the live corpus, not from a model. Rank your target list by real movement.
{
"company": "Toast",
"new_roles_30d": 60,
"velocity": 0.68,
"direction": "down",
"is_surge": false,
"source_boards": ["dice", "greenhouse",
"himalayas", "welcometothejungle"]
} Simple, usage-based pricing
No card to start. No sales call. Cancel at any time. Above your plan's allowance, you pay $0.10 per sourced company row. Every plan has a hard spend cap set by default.
Free
start here$0 /month
| Calls / rolling 24h | 100 |
| Watches | 3 |
| Delivered changes | 50 included |
| Spend cap | hard-capped |
Starter
$49 /month
| Calls / rolling 24h | 50,000 |
| Watches | 5 |
| Delivered changes | 250 included |
| Row credits | 1,000 included |
Growth
$199 /month
| Calls / rolling 24h | 200,000 |
| Watches | 25 |
| Delivered changes | 1,500 included |
| Row credits | 5,000 included |
Signup includes a 14-day trial: 10,000 calls per rolling 24h, no card. See plan and cap details on the pricing page.