NewSearch millions of jobs from your AI agent with MCP

Glossary

The jobs-data terms, defined.

Short, plain-English definitions of the integration and jobs-data terms developers actually search for - what they mean, why they are confusing, and how they fit together. Written by the team that indexes the ATSs.

How the vocabulary breaks down

The jobs-data and B2B-intent vocabularies overlap with three adjacent fields - ATSs, CRMs, and data infrastructure - in ways that confuse documentation searches. “ATS API” means one thing to a recruiter (workflow integration) and a different thing to a developer (public read endpoint). “Intent data” means six different things depending on which provider category you’re shopping for. This glossary picks one definition per term and is explicit about which adjacent meaning each entry does not cover.

Terms cluster into four implicit categories:

  • Data shapes - how postings are modeled. Job posting schema, job posting deduplication, job board API.
  • Infrastructure - the plumbing under a jobs-data product. API rate limiting, unified API, job aggregator.
  • Integration patterns - how you connect an ATS or job source to a downstream system. ATS API, ATS integration, job scraping.
  • Intent surfaces - the B2B signal categories. Intent data, hiring-signal intent, talent intelligence.

If you’re new to the space, the most useful starting terms are job board API and ATS API (clarify the two surfaces), unified API (the integration pattern most teams converge on), and job posting deduplication (the problem that becomes obvious only at scale). The intent-data terms make most sense after reading the intent data providers comparison hub.

Concepts

Integrations

Data

Technographics

More definitions on the way

We’re adding entries on job feeds, careers-page crawling, rate limiting, and freshness. Want a term defined next? Hit us on the contact page.

Back to home