canonical: https://jentic.com/apis/reqbeat.com/reqbeat

# Reqbeat API

The Reqbeat API turns public job postings into company hiring signals: it tells you whether a company is hiring, lists its open reqs deduped across job boards, and scores hiring velocity, first hires per function, hard-to-fill reposts, ATS vendor switches, and a calibrated intent score. It searches open roles and hiring companies across the market, matches live reqs to an ideal customer profile, and returns firmographics gathered from ATS and job board data. Watches on a company or saved search deliver opened, reposted, reobserved, or closed events to your webhooks, with a cursor-based change feed, delivery log, and replay.

## For AI agents

Check whether a company is hiring, pull its open reqs and hiring momentum, find companies hiring for a role or ICP, and watch companies for new or closed reqs with Reqbeat.

## Scope

Does not post jobs, manage applicants, or run an ATS. Use for reading company hiring signals, job market searches, and hiring-event watches only.

## Capabilities

- Check whether a company is hiring and list its open reqs deduped across job boards, filtered by function or country
- Read a company's hiring pulse: velocity, direction, and momentum from ATS and board data
- Find companies hiring for a role by geo, industry, headcount_band, or source_type, excluding agencies
- Match live reqs to an ideal customer profile with salary_min_usd and salary_max_usd bounds
- Watch a company or saved search for opened, reposted, reobserved, or closed reqs and deliver them to a webhook
- Resolve a company id from a domain or name and enrich it with firmographics
- Report a conversion outcome on a company and read back attribution of the signals that won

## Use cases

### Agent pre-call research

Before a sales or recruiting outreach, an agent connected through Jentic resolves the company from its domain, then pulls the pre-action brief, which joins hiring signals into one bounded call. When data is cold, the brief returns 202 with a job_id and status crawling, and the agent checks back later.

Example prompt: Call GET `/v1/companies/resolve` with domain set to acme.com, then GET `/v1/companies/{company_id}/pre-action-brief` for the returned id

### Hiring-intent prospecting

Revenue teams find accounts actively hiring for roles their product serves. The role search filters by role, geo, since, industry, and headcount_band and can exclude agencies, while the qualified-reqs search takes ICP criteria with salary bounds and an option to include each company's pulse.

Example prompt: Call GET `/v1/reqs/search` with role set to 'data engineer', geo set to DE, and exclude_agencies set to true

### Account watches with webhooks

Register a webhook endpoint, then create a watch on a company or saved search with event_types such as opened and closed. Deliveries are logged and can be replayed, and the events feed returns the same changes since a cursor for polling setups.

Example prompt: Call POST `/v1/webhooks` with url set to the receiver, then POST `/v1/watches` with company_id, event_types set to ["opened", "closed"], and the returned webhook_endpoint_id

### Closed-loop signal attribution

After a deal closes, report the outcome on the company with observed_at and optionally the req_key that triggered it. Reqbeat uses submitted outcomes for its calibrated intent score, and the attribution operation shows which delivered signals were won.

Example prompt: Call POST `/v1/companies/{company_id}/outcomes` with outcome set to your conversion label and observed_at set to 2026-11-12T00:00:00Z, then GET `/v1/attribution`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/companies/{company_id}/is-hiring` | Is this company hiring? |
| GET | `/v1/companies/{company_id}/open-reqs` | Company's open reqs deduped across boards |
| GET | `/v1/companies/{company_id}/hiring-pulse` | Hiring velocity and momentum |
| GET | `/v1/reqs/search` | Find companies hiring for a role |
| POST | `/v1/reqs/qualified` | Find live reqs matching an ICP |
| GET | `/v1/companies/resolve` | Find a company id by domain or name |
| POST | `/v1/watches` | Watch a company or saved search |
| GET | `/v1/events` | Change feed since your cursor |

## Key resources

- **Companies** — Hiring status, open reqs, hiring pulse, first hires, repost pain, ATS migrations, intent score, and enrichment per company_id
- **Reqs and jobs** — Market-wide role and req search, ICP matching, and single-role detail
- **Watches and webhooks** — Watches on companies or saved searches, webhook endpoints, delivery log, and replay
- **Events** — Cursor-based change feed of hiring events
- **Account and keys** — API keys, usage, and account pause and resume

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 56 / 100
- **View full report:** https://jentic.com/apis/reqbeat.com/reqbeat/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Reqbeat by hand means handling its X-API-Key header, Idempotency-Key headers on paid routes, 202 crawling responses, and webhook registration before watches. Through Jentic you install once, import Reqbeat from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Reqbeat puts company_id in the URL path (`/v1/companies/{company_id}/open-reqs`), so a rule can confine your agent to the companies you name. You choose the operations it may call, so destructive ones like key revocation, watch cancellation, or account pause are not included unless you add them.
- **Credential handling:** Your Reqbeat API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'is this company hiring' or 'watch a company for new jobs', and Jentic returns the matching Reqbeat operation with its input schema so the agent sends the right company_id and filters.

## Related APIs

- **TheirStack API** — Job postings and technographic data
- **Crustdata API** — Company and people data with headcount signals
- **Apollo.io API** — Contact search and enrichment for outreach

## FAQ

### What authentication does the Reqbeat API use?

Per its OpenAPI spec, the Reqbeat API authenticates with an API key sent in the X-API-Key header, and GET `/v1/whoami` shows what your key resolves to. Keys can be listed, issued, rotated, and revoked through the `/v1/keys` operations. Through Jentic, the key is stored encrypted by your own Jentic One instance and injected at execution time.

### Can I check whether a specific company is hiring with Reqbeat?

Yes. Resolve the company with GET `/v1/companies/resolve` using its domain or name, then call GET `/v1/companies/{company_id}/is-hiring.` For detail, GET `/v1/companies/{company_id}/open-reqs` lists its open reqs deduped across boards and accepts function and country filters.

### What happens when Reqbeat has no fresh data for a company?

The hiring pulse and pre-action brief operations honor a max_age parameter in seconds. When no ATS or board data exists yet and max_age demands freshness, they return 202 with a job_id and status crawling instead of a synchronous body, so retry the call later.

### How do Reqbeat watches deliver events?

Register an endpoint with POST `/v1/webhooks`, then create a watch with POST `/v1/watches`, giving event_types from opened, reobserved, reposted, and closed plus the webhook_endpoint_id. The delivery log at `/v1/webhook-deliveries` shows each attempt, and a delivery can be replayed.

### What are the rate limits for the Reqbeat API?

The OpenAPI spec defines a rate_limited error but does not publish the limits. GET `/v1/usage` reports your metered usage over a rolling window; see https://reqbeat.com for plan limits.

### How do I find companies hiring for a role through Jentic?

Search Jentic for 'find companies hiring for a role'. Jentic returns GET `/v1/reqs/search` with its input schema; your agent sets role, geo, and since, and Jentic sends the call with your stored key. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a Reqbeat MCP server?

You don't need an MCP server to give your agent Reqbeat. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent discovers the company, search, and watch operations on demand instead of carrying all their tool definitions in context.

### Can I limit what my agent is allowed to do with the Reqbeat API?

Yes. A research agent could be allowed the GET operations under `/v1/companies/{company_id}`/ for the accounts it covers, plus GET `/v1/reqs/search`, and nothing else. It can then read hiring signals but cannot issue or revoke keys, pause the account, or create watches.
