Job boards reference
Every Job boards operation, from the registry
11 operations wired in the registry, 11 of them proven by real traffic.
Choose a Job boards operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Other operations
- Bing job posting — One aggregated job posting from Bing with its description and apply link.
- Indeed job posting — One Indeed job posting with its description, employer and apply link.
- LinkedIn job posting — One LinkedIn job posting with its description, seniority, function, industries and applicant count.
- LinkedIn organisation lookup — Organisation ids for a name, to filter LinkedIn job searches by employer.
- Salary range — Yearly, monthly, weekly, daily and hourly salary bands (min, max, mean, median) for a job title in a country.
- Salary job titles — Canonical job titles matching a query, to feed the salary range route.
- Xing job posting — One Xing job posting with its salary band, benefits, skills and responsibilities.
Search and discovery
- Bing job search — Search Bing's aggregated job postings by location and keywords.
- Indeed job search — Search Indeed job postings in a country by keywords, location and radius.
- LinkedIn job search — Search LinkedIn job postings by keywords, location, organisation, date, employment type, experience level and workplace type.
- Xing job search — Search Xing job postings (the German-speaking market) by keywords, location, level, remote options and salary.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/jobs to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Job boards
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Job boards
11 operationsElsewhere
The same registry, other shapes
- Job boards overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=jobs— the same rows to your code at runtime, for 0 credits.