Jobs API Review: Unified Job Search Across LinkedIn, Bing, Indeed & Xing

What the Jobs API does and who it is for

Maintaining direct integrations with multiple job boards is tedious: each platform has its own auth model, response shape, and rate-limit policy. The Jobs API solves this by sitting in front of LinkedIn, Bing Jobs, Indeed, and Xing, normalizing their responses into a common JSON structure so your application talks to one endpoint instead of four.

The typical consumer is a developer building something that needs live job data: an aggregator site, an AI-powered career assistant, an HR analytics dashboard, or a recruitment automation tool. Researchers who want to track hiring trends across platforms or benchmark salaries by region will also find the built-in salary endpoints useful without needing to scrape anything.

Endpoint walkthrough

There are 16 endpoints in total, organized by data source. The v2 path is the current generation; a handful of v1-style endpoints (/list, /get, /salary/getJobTitles, /salary/getSalaryRange) are still present but marked deprecated.

Bing Jobs (/v2/bing/*)

Two endpoints handle Bing:

• GET /v2/bing/search — Accepts query, location, datePosted (day, week, or unrestricted), employmentTypes (semicolon-separated: contractor, fulltime, parttime, temporary), remoteOnly, and a pagination token. location is required unless you supply a token. Results include company name, employment type, a provider-specific ID, posting date, and the originating job board (e.g., Jobrapido, Bebee).
• GET /v2/bing/get — Takes an id from a search response and returns the full record: applyUrl, description (plain text and HTML variants), employmentType, location, companyName, and postedTimeAgo.

Pagination is token-based: the response includes meta.nextToken and _links.next with a ready-made URL for the next page.

Indeed (/v2/indeed/search)

Currently a single search endpoint — there is no Indeed detail endpoint in v2. Parameters include query, location, countryCode (two-letter ISO code, required unless a token is set), sortType (relevance or date), radius, and radiusType (km or miles). Responses include a direct applyUrl, company details with logo image URL, timestamped publication dates, and structured location data (country, country code, city).

LinkedIn (/v2/linkedin/*)

Three endpoints:

• GET /v2/linkedin/search — The search surface, which can optionally accept organizationIds to filter listings by specific companies or schools.
• GET /v2/linkedin/get — Full job detail by ID.
• GET /v2/linkedin/organizations — Returns organization IDs you can feed into the search endpoint's organizationIds filter, making it straightforward to scope a search to a particular employer without hardcoding internal identifiers.

Xing (/v2/xing/*)

Search and detail endpoints follow the same pattern as Bing. Xing is particularly relevant for coverage of the German-speaking job market (Germany, Austria, Switzerland), which LinkedIn and Bing may under-represent.

Salary range (/v2/salary/*)

Two dedicated salary endpoints round out the feature set:

• GET /v2/salary/titles — Accepts a query string and returns normalized job title objects to use downstream.
• GET /v2/salary/range — Takes a job title (from the titles endpoint) and returns salary range data.

This two-step lookup pattern — first resolve a canonical title, then fetch its range — avoids ambiguous free-text queries against salary data.

Pricing breakdown

The free BASIC tier gives you 50 requests per month — enough to test all four sources and verify response shapes, but not enough for any live product. A minimal production deployment doing one search per hour around the clock would consume about 720 requests per month, putting it squarely in PRO territory.

PRO at $10/month is the obvious entry point for real workloads. At 20,000 monthly requests with a 2 req/sec ceiling, it suits low-to-medium traffic use cases: a small job board refreshing listings a few times per day, or a chatbot handling dozens of user sessions. ULTRA triples the quota for double the price, useful when you're hitting multiple sources per user query. MEGA removes the quota ceiling with pay-as-you-go overage at $0.001 per request beyond 200,000, and raises the rate limit to 5 req/sec — appropriate for high-volume data pipelines or large aggregators.

Practical use cases

Job board with multi-source coverage: Query Bing, LinkedIn, and Indeed in parallel for each user search, deduplicate by title and company, and surface results in a unified feed. The standardized response schema makes this straightforward without source-specific parsing logic.

AI job recommendation engine: Collect job descriptions from multiple sources keyed to a user's skills, pass descriptions to an LLM for relevance scoring, and return ranked results. The detail endpoints supply full plain-text and HTML descriptions suitable for embedding.

Salary benchmarking tool: Chain /v2/salary/titles to resolve a user's job title query, then /v2/salary/range to return compensation data alongside matched job postings — a common pattern for career planning tools.

Regional hiring analytics: Combine LinkedIn (global) with Xing (DACH-focused) to get more complete coverage of German-speaking markets than either source provides alone.

Limitations and things to check before integrating

Indeed has no detail endpoint. The /v2/indeed/search response does include applyUrl and a description field inline, but if you need the same two-step search-then-fetch pattern you use for Bing, LinkedIn, and Xing, Indeed won't support it in the current v2 API.

The BASIC tier is effectively a sandbox. Fifty requests per month is insufficient for any recurring production workload. Budget for at least PRO from launch.

Rate limits apply to PRO and ULTRA. At 2 req/sec, fanout queries that hit multiple sources simultaneously need to be sequenced or queued carefully to stay within bounds.

Deprecated v1 endpoints still exist. The older /list, /get, /salary/getJobTitles, and /salary/getSalaryRange paths are present but marked deprecated. New integrations should target v2 exclusively to avoid future breaking changes.

Data freshness is source-dependent. The datePosted filter on Bing accepts day or week granularity, but Indeed and Xing may behave differently. Test your target source's recency before relying on it for real-time feeds.

Getting started

The provider supplies a Postman collection via a public GitHub URL, which is the fastest way to explore all endpoints interactively. After importing it:

1. Open the collection's Variables tab.
2. Replace the x-rapidapi-key placeholder with your API key from RapidAPI.
3. Run a /v2/bing/search or /v2/linkedin/search call with a known location to verify connectivity.

For code integration, all endpoints follow standard GET requests with query parameters and return consistent JSON envelopes containing data, meta (with pagination token), _links, errors, and warnings arrays, plus hasError and hasWarning boolean flags. This envelope structure makes uniform error handling straightforward across all sources.

With a popularity score of 9.9 out of 10 and over 4,700 marketplace subscribers, the Jobs API has a substantial active user base — a reasonable signal that the endpoint surface is stable and the support channel is responsive.