# JobsPipe glossary

> Plain-English definitions of the jobs-data and B2B-intent terms developers and buyers actually search.

**Canonical URL:** https://jobspipe.dev/glossary

## Terms

- **ATS API** - https://jobspipe.dev/glossary/ats-api
  An ATS API is the programmatic interface an applicant tracking system exposes so software can read or write recruiting data - job requisitions, candidates, applications, and interview stages - without going through the ATS web interface.
- **ATS integration** - https://jobspipe.dev/glossary/ats-integration
  ATS integration is the work of connecting an applicant tracking system to other software - a job board, a sourcing tool, an HRIS, an analytics product - so recruiting data moves between them automatically instead of by manual export.
- **Job board API** - https://jobspipe.dev/glossary/job-board-api
  A job board API is a programmatic interface for reading job postings - title, company, location, salary, description, apply link - usually across many employers, so software can ingest listings without scraping web pages.
- **Job aggregator** - https://jobspipe.dev/glossary/job-aggregator
  A job aggregator is a system that collects job postings from many sources - company career pages, applicant tracking systems, and other boards - and combines them into a single searchable, deduplicated index.
- **Job posting schema** - https://jobspipe.dev/glossary/job-posting-schema
  A job posting schema is the defined structure of a job record - the field names, types, and meanings - that lets job data from different sources be stored, searched, and exchanged consistently.
- **Job posting deduplication** - https://jobspipe.dev/glossary/job-posting-deduplication
  Job posting deduplication is the process of detecting that several collected job records describe the same real-world opening and collapsing them into one, so an aggregated index does not count the same job many times.
- **Unified API** - https://jobspipe.dev/glossary/unified-api
  A unified API is a single API that abstracts many similar third-party services behind one schema and one authentication flow, so a developer integrates once instead of once per provider.
- **Talent intelligence** - https://jobspipe.dev/glossary/talent-intelligence
  Talent intelligence is the practice of collecting and analyzing workforce data - job postings, skills, compensation, hiring activity, talent movement - to make better decisions about recruiting, workforce planning, and competitive strategy.
- **Job scraping** - https://jobspipe.dev/glossary/job-scraping
  Job scraping is the automated extraction of job postings from websites - company career pages, job boards, and ATS-hosted listings - by programmatically fetching pages and parsing the posting data out of them.
- **API rate limiting** - https://jobspipe.dev/glossary/api-rate-limiting
  API rate limiting is the practice of capping how many requests a client can make to an API within a set time window, protecting the service from overload and enforcing fair use across all consumers.
- **Intent data** - https://jobspipe.dev/glossary/intent-data
  Intent data is any signal that suggests an account or buyer is moving toward a purchase decision - inferred from third-party content consumption, software-review activity, first-party website engagement, or capital-allocation moves like hiring.
- **Hiring-signal intent** - https://jobspipe.dev/glossary/hiring-signal-intent
  Hiring-signal intent is a category of B2B intent data that uses a company's open job postings and headcount changes as a leading indicator of buying intent - typically 1-2 quarters before content or review intent fires.
- **Technographics** - https://jobspipe.dev/glossary/technographics
  Technographics is data about the technology stack a company runs - its frameworks, analytics, hosting, CRM, payments, and other tools - used by B2B teams to target and qualify accounts by the software they already use.
- **Technographic data** - https://jobspipe.dev/glossary/technographic-data
  Technographic data is structured data on the technologies a company uses, attached to its domain, exposed via API so sales, marketing, and competitive-intelligence teams can target and segment by tech stack.
- **Firmographic vs technographic data** - https://jobspipe.dev/glossary/firmographic-vs-technographic
  Firmographic data describes a company's attributes (industry, size, revenue, location); technographic data describes the technologies it uses. B2B teams combine both to define and prioritize target accounts.
- **B2B technographic data** - https://jobspipe.dev/glossary/b2b-technographic-data
  B2B technographic data is technology-usage data on companies, used by sales, marketing, and competitive-intelligence teams to build target lists, qualify accounts, and personalize outreach around the tools a prospect already runs.
- **Technographic segmentation** - https://jobspipe.dev/glossary/technographic-segmentation
  Technographic segmentation is the practice of grouping accounts by the technologies they use, so messaging, targeting, and prioritization can be tailored to each group's stack.
- **Technographic data examples** - https://jobspipe.dev/glossary/technographic-data-examples
  Technographic data examples are the concrete technology data points attached to a company, such as the analytics suite, hosting provider, ecommerce platform, CRM, or payment processor it uses.
- **Employment Type** - https://jobspipe.dev/glossary/employment-type
  Employment type is the field on a job posting that records the kind of working relationship an opening offers - full-time, part-time, contract, temporary, or internship - using a small, fixed set of values so jobs can be filtered and compared across sources.