Skip to content
BetterJobs Docs
API v1 preview — endpoints and fields may change before general availability.

SignalsAPI

What does SignalsAPI contribute, and when does BetterJobs route to it?

View .md

SignalsAPI sells recruiter-focused hiring signals. BetterJobs uses it as one of six partner providers, for the job signals it sees.

SignalsAPI

signalsapi

Recruiter-focused hiring signals plus the hiring owner's verified work email.

Sources
290+ sources: job boards, LinkedIn, funding databases, news, government filings
Signals
About 210k signals per 30 days
Markets
506 markets in 7 regions
Recheck
Sources rechecked every 15 minutes

Growth includes 2 partner providers; Pro and above include all six. GET /v1/providers shows what your plan enables.

Facts per SignalsAPI docs.

What it is strong at

Section titled “What it is strong at”

All facts in this section are per SignalsAPI docs.

  • Wide signal net. 290+ sources: job boards, LinkedIn, funding databases, news and government filings.
  • Fast recheck. Sources are rechecked every 15 minutes.
  • Broad market reach. About 210k signals per 30 days across 506 markets in 7 regions.
  • Provenance on every value. Each value comes in an envelope: value, source_board, observed_at, confidence.
  • Hiring owner contact. Signals can carry the hiring owner’s verified work email.

What it contributes to a BetterJobs job

Section titled “What it contributes to a BetterJobs job”

SignalsAPI feeds job signals into the same merge as every other source. Where its field names have a confident BetterJobs equivalent:

— = no confident one-to-one equivalent in that provider's published field names.
BetterJobsSignalsAPI
sources[].last_seen_atobserved_at

What it filled on a given job is in that job’s sources[] entry for signalsapi, under fields.

Refresh

Section titled “Refresh”

Per SignalsAPI docs, its sources are rechecked every 15 minutes. On each BetterJobs job, the signalsapi entry in sources[] carries first_seen_at and last_seen_at for that source.

Notes and quirks we normalize

Section titled “Notes and quirks we normalize”

Provenance envelope becomes sources[]

Section titled “Provenance envelope becomes sources[]”

SignalsAPI wraps each value in {value, source_board, observed_at, confidence}. BetterJobs records provenance per source instead of per value. Each job has a sources[] array: one entry per provider, with url, first_seen_at, last_seen_at and the fields it contributed. SignalsAPI’s observed_at maps to sources[].last_seen_at.

Cross-source confidence on the whole job is p_real (0 to 1). It comes from corroboration across sources, not from one provider’s confidence. See Provenance and confidence.

Signals, not only postings

Section titled “Signals, not only postings”

Per SignalsAPI docs, some of its 290+ sources are funding databases, news and filings, not job boards. BetterJobs returns jobs. Only signals that resolve to a job opening become, or merge into, a canonical job.

When BetterJobs routes to it

Section titled “When BetterJobs routes to it”

Only when SignalsAPI is enabled on your plan. Then:

  • max_coverage asks it on every search.
  • cheapest_first asks it only if the BetterJobs index and earlier sources did not fill the page.
  • waterfall.providers: ["betterjobs", "signalsapi"] pins it.

Check metadata.providers.tried and metadata.providers.hit to see whether it was asked and matched.

Plans that include it

Section titled “Plans that include it”

Growth includes 2 partner providers; Pro and above include all six. GET /v1/providers shows what your plan enables. See the plan table.

Provider docs

Section titled “Provider docs”

We do not link to SignalsAPI’s docs from this site. Everything you need to use SignalsAPI data through BetterJobs is on this page and in the field dictionary.

Section titled “Related”