What is a job changes API?

A job changes API returns people-movement events (the person, their new role, and the company they joined) as structured data you can query and pipe into your own tools. The Signalbase Job Changes API detects the move in under a minute from public role announcements and ties it to a verified company profile.

How are role moves detected?

Moves are detected on a flow from public new-role announcements, then the old and new role are confirmed and the source is attached. Typical lag is under a minute, against the quarterly refresh most people databases run on.

Can I filter by seniority or function?

Yes. Seniority band, function, and location are all query parameters. Narrow the flow to your ICP before it reaches your CRM, with no post-processing on your side.

Does the Job Changes API cover every move?

No, and we would rather say so. Coverage is strongest where the move is announced publicly and the person and company resolve cleanly. Private moves and thinly reported regions are where it drops off. If you need timing on decision-maker moves, this is built for that.

How do I start using the Job Changes API?

Start a 7-day trial, pull your first events in a few lines, and test against real data. Full endpoints and parameters are in the documentation.

Job Changes API

Capture job changes that go beyond your CRM.

Get a real-time job changes API that catches role moves like promotions and executive changes as they happen.

Global coverage across markets and functions
Person, new title, and prior company on every event
1 signal = 1 verified move with the source attached

Start 7-day trial Read the docs

GET /v1/job-changesstreaming

Jane D.VP of Sales

detected just now

from Stripe → Northwindnew decision maker

Marco R.CRO

detected 41s ago

from Datadog → Globex

Priya S.Head of RevOps

detected 2m ago

from Notion → Initechnew decision maker

Tom K.VP Marketing

detected 4m ago

from HubSpot → Vantia

Role move → your endpoint, in under a minute.

Powering people-movement signals inside leading platforms

Oxygen

Stock vs flow

Databases record who someone was. We catch where they went.

A live job change stream tells you a champion just landed somewhere new, with budget and a mandate, before their old title goes stale in anyone's database. That timing is a warm intro nobody else has yet.

What happenedThe downstream effect

VP of Sales changes jobs

Day 1

Recorded in Signalbase

Record still shows the old role

Day 9

New role and company confirmed

Day 2

Recorded in Signalbase

Contact still routes to the old company

Day 16

Former team starts to follow

Day 15

Recorded in Signalbase

Org chart unchanged

Day 24

Champion now owns the budget

Day 22

Recorded in Signalbase

You reach out after everyone else

Day 30

190+

countries covered, from team profiles to announcements

IC → C-suite

every seniority of move captured, filterable to your ICP

<1 min

typical lag from the move going public to it landing in your endpoint

Benchmark

Most tools store yesterday's org chart. We catch the move as it happens.

Every other tool hands you a contact record that was true when it was last refreshed. The Job Changes API detects the move itself and hands you the person, the new company, and the source.

Layer	Exa search API	Apify scraper marketplace	Traditional database	Signalbase
Sourcing: catching the move	Search results, no events	Scraped profiles, you schedule the runs	Refreshed on a schedule	Detected in under a minute from public role announcements
Verification: confirming the change	Not provided, you build	Not provided, you build	Stale the day it ships	Old and new role confirmed, every source attached
Contextualization: the full picture	Not provided, you build	Not provided, you build	Person only, no company context	Person tied to the company profile they just joined

Response shape

Every field, no scraping on your side.

personName"Jane D."Person who changed roles, handled per GDPR.

newRole"VP of Sales"Their new title.

companyName"Northwind"The company they joined.

personLocation"Austin, US"Location, for territory filtering.

discoveredAt"2026-07-03"When Signalbase detected the move.

sources["linkedin.com/…"]Source URLs the change was captured from.

Need all parameters?Check the full API docs →

Delivery

Three ways to push the data to you.

The same role-move events, delivered where you work: pull them on your schedule, have them pushed the moment they land, or wire them natively into your agents.

Pull

REST API

Poll the endpoint with a since cursor on your own schedule.

Push

Webhooks

We post the event to your endpoint the moment it lands. This is the flow, not a nightly batch.

Native

MCP

Wire the same signals straight into your agent or GTM tooling over the Signalbase MCP.

Built for

Where teams point this API.

Champion tracking

Follow your buyers when they move, so a warm relationship turns into a warm pipeline at the new account.

New-decision-maker alerts

Get pinged the day a new VP or C-level lands in a target account, before the org chart everyone else uses updates.

Territory routing

Route each executive move to the rep who owns the account the same day it clears, straight into your CRM.

Building internal AI SDRs

Find your ICP once and let people-movement signals populate while you never touch the UX again.

We have tried other financial signals providers, such as Crunchbase. Despite being more expensive, they could not match Signalbase's timeliness or the ability to trace data back to source posts.

Jack CaneRevenanas

We have been searching for a signal infrastructure for months and happily ended up with Signalbase. The data is top tier and the platform and API are very straightforward.

Tim ScheuerOxygen

Signalbase is one of the intent sources feeding our SaaS platform, and the Dutch company signals get better and better every week. Highly recommend Signalbase, the support is amazing as well!