Recruiting Data API
The live recruiting API that saves you the LinkedIn scrolling.
Stop scrolling feeds and guessing which board to check. One API for the two events recruiting runs on: a company opening roles and a person changing jobs, detected live and pushed to you.
- Hiring signals from job boards, careers pages, and team posts
- Job changes with internal promotions and executive movement
- Sub-minute detection with the source attached to every event
- 1 signal = 1 full company profile with people data
Powering job data inside leading platforms
OxygenStock vs flow
Stop guessing who is hiring. Read who is about to.
LinkedIn scrolling and job-board roulette makes you lose deals. The events that predict hiring fire earlier. A funding round opens budget, an arriving leader starts a build-out, a departure opens a seat. Read those live and the companies about to hire surface before the first listing exists.
Benchmark
Job posting APIs scrape the last layer. This one reads all three.
Posting scrapers deliver the boards. People databases deliver last month's org chart. A recruiting data API has to read the boards, the careers pages, and the people, live, and hand back structured events.
| Layer | Job posting APIs board scrapers | People databases refresh diffs | Manual tracking alerts and saved lists | Signalbase |
|---|---|---|---|---|
| Sourcing: catching the event | Board listings only, after they go live | Changes surface when the record rebuilds | Whatever the rep happens to see | Boards, careers pages, and posts, read as they happen |
| Freshness: when you find out | Hourly to daily scrape cycles | Weeks, bounded by the rebuild | Same day, sometimes, for one account | Typically under a minute, source attached |
| Context: what you can act on | A listing, no company or people context | A record, no event or timing | A feed item, nothing exports | Structured event inside a full company profile |
Response shape
Every field, no scraping on your side.
Delivery
Three ways to push the data to you.
The same recruiting events, delivered where you work: pull them on your schedule, have them pushed the moment they land, or wire them natively into your agents.
REST API
Poll the endpoint with a since cursor on your own schedule.
Webhooks
We post the event to your endpoint the moment it lands. This is the flow, not a nightly batch.
MCP
Wire the same signals straight into your agent or GTM tooling over the Signalbase MCP.
Built for
Where teams point this API.
Agency BD
Reach the company while the mandate is forming, inside the window between the trigger and the public listing.
Rec-tech platforms
Embed live hiring and move events inside your own product instead of refreshing a stock of records.
Talent intelligence
Feed movement data into scoring and market views with the source attached to every event.
AI recruiting agents
Ground agent outreach in a sourced event over MCP, so the first line references what actually happened.
When I first tried Signalbase, I was completely surprised. Just two minutes after a post is made, we're already seeing it as a signal.
Zeynep Serra AvanCompanyEnrichAfter exhausting every major data provider, few met our hygiene standards. Proud to be able to build our agents on your signals.
Seb VissersCEO at CaideThis is f*cking wild! What used to take tens of hours of manual research now runs in about 4 minutes. These signals are really minute old!
Tanay MishraClay Bootcamp MentorSource coverage
The three layers a recruiting data API has to read.
Most job posting APIs read one layer, the boards, and the boards are the lagging end of the chain. Recruiting data starts earlier: on careers pages before aggregators mirror them, and in the posts people publish before a listing exists.
Job boards and aggregators
Global and regional boards read continuously across 190+ countries, deduplicated against the entity graph so a repost never reads as a new role.
- Global job boards
- Regional and country boards
- Niche and vertical boards
- Remote-work boards
- Government and public listings
Careers pages, wherever they are hosted
Roles detected on company careers pages directly, including pages hosted on the ATS platforms most companies hire through.
- Greenhouse
- Lever
- Ashby
- Workable
- Recruitee
- Teamtailor
- Personio
- SmartRecruiters
- Workday
- Join.com
- Homerun
- and self-hosted careers pages
Posts and profiles from the people themselves
The earliest layer: team representatives posting that a role is open before a listing exists, announcement posts for moves, and profile-experience monitoring for the moves nobody announces.
- Executive and founder posts
- Team-representative posts
- New-role announcements
- Internal promotions
- Profile experience changes
The boards, covered differently
Get recruiting signals for the roles on these job boards.
Detection starts outside the boards on purpose: exec and team posts fire 3 to 4 weeks before the listing. The boards still count, and results also come from careers pages and boards like these, so the feed carries the early post and the confirmed listing.
Hiring Signals API
A company is opening roles. Postings from boards and careers pages plus the team posts that precede them, with role, department, seniority, and location on every signal.
Explore the Hiring Signals API →The people sideJob Changes API
A person moved. New roles, internal promotions, and executive movement with the previous company when named, so a departure reads as an opening and an arrival as growth.
Explore the Job Changes API →The about-to-hire compound: pair these with the Funding API and reach companies that raised before their first role is public.
Questions
What teams ask before they wire it in.
Get the recruiting data API that builds your pipeline.
1 recruitment API, multiple job data signals: hiring posts, job changes, and the funding rounds that precede them.