# 🚀 JobsAPI.dev ### Job & Company Data Infrastructure for Developers **15 Sources. One API. Zero Platform Logins.** Build applications on top of structured, enriched job and company data without maintaining your own scraping infrastructure. JobsAPI.dev aggregates job postings and company intelligence from **15 sources** — including deep LinkedIn enrichment — and exposes them through a single, consistent API. ![Sources](https://img.shields.io/badge/sources-15-blue?style=for-the-badge) ![API](https://img.shields.io/badge/interface-REST%20%2B%20MCP-6E56CF?style=for-the-badge) ![LinkedIn](https://img.shields.io/badge/LinkedIn-enrichment-0A66C2?style=for-the-badge) ![No Login](https://img.shields.io/badge/platform%20logins-zero-2ea043?style=for-the-badge)
**[⚡ Quick Search](#-how-it-works--submit-then-poll)** · **[⏱️ Response Times](#️-response-times)** · **[🌎 Sources](#-the-15-sources)** · **[🤖 MCP](#-mcp--use-jobsapidev-with-ai-agents)** · **[📄 Fields](#-job-record-fields)** · **[🧪 Getting Started](#-getting-started)**

--- ## ⚡ Why JobsAPI.dev? Collecting job and company data at scale means dealing with: | Challenge | What it looks like | |---|---| | 🌐 **Fragmentation** | 15+ different platforms, each with its own structure | | 🛡️ **Anti-bot systems** | Rate limits and defenses, especially on LinkedIn | | 🧩 **Inconsistent schemas** | Different field names and formats across sources | | ♻️ **Data hygiene** | Deduplication and enrichment caching | | ⚙️ **Ongoing maintenance** | Source websites change constantly |

### 💡 **JobsAPI.dev handles all of it. You call one API.**

--- ## 🔐 No Platform Login Required Your application never touches LinkedIn, Wellfound, or any other source directly.

--- ## ⏱️ Response Times > **Not all sources move at the same speed** — plan your UX around it.

| Tier | Sources | Typical response time | |:---:|---|:---:| | ⚡ **Fast** | Greenhouse, Lever, Ashby, SmartRecruiters, Himalayas, Remotive, We Work Remotely, RemoteOK, Arbeitnow, Jobicy, Reed, Adzuna, Y Combinator — Work at a Startup | **Seconds** | | 🐢 **Slow (deep scrape)** | 💼 LinkedIn, 🚀 Wellfound | **Several minutes+** |

**Everything except LinkedIn and Wellfound is fast** — the 13 other sources resolve quickly, which is exactly what `GET /jobs/search` is built for: instant, synchronous, parallelized results. **LinkedIn and Wellfound take longer — often several minutes or more** — because getting real data out of them means genuine stealth browser automation, not a quick API call. That's why they run through the **asynchronous submit → poll** flow instead of the instant search endpoint. Build your UX expecting a wait on these two, and instant results on everything else. --- ## 🌎 The 15 Sources

| Source | What you get | Speed | |---|---|:---:| | 💼 **LinkedIn** | Job search, job details + enrichment (seniority, salary, applicant count), company profiles | 🐢 Minutes+ | | 🚀 **Wellfound** | Job listings + company intelligence (funding, headcount, hiring signals) | 🐢 Minutes+ | | 🌿 **Greenhouse** | Employer-hosted job listings | ⚡ Fast | | ⚡ **Lever** | Employer-hosted job listings | ⚡ Fast | | 📋 **Ashby** | Employer-hosted job listings | ⚡ Fast | | 🎯 **SmartRecruiters** | Employer-hosted job listings | ⚡ Fast | | 🏔️ **Himalayas** | Remote job listings | ⚡ Fast | | 🌍 **Remotive** | Remote job listings | ⚡ Fast | | 🏠 **We Work Remotely** | Remote job listings | ⚡ Fast | | 💻 **RemoteOK** | Remote job listings | ⚡ Fast | | 🇩🇪 **Arbeitnow** | Job listings | ⚡ Fast | | 🕒 **Jobicy** | Remote job listings | ⚡ Fast | | 📰 **Reed** | Public job search | ⚡ Fast | | 🔎 **Adzuna** | Public job search | ⚡ Fast | | 🧑‍💻 **Y Combinator — Work at a Startup** | Startup job listings | ⚡ Fast |

--- ## 🧰 How It Works — Submit, Then Poll Most of the API is **asynchronous**: you submit a job, then poll for results once it's done. This matters because real scraping — especially LinkedIn and Wellfound — takes longer than a typical instant API call. ```mermaid flowchart LR A["📤 POST /jobs
submit a URL"] --> B["🆔 get back a jobId"] B --> C["🔄 GET /jobs/{id}
check status"] C -->|queued → running → succeeded| D["📦 GET /jobs/{id}/records
fetch structured data"] style A fill:#6E56CF,color:#fff style B fill:#8A63D2,color:#fff style C fill:#A78BFA,color:#fff style D fill:#2ea043,color:#fff ``` ### 🔀 One endpoint, two kinds of data The URL you submit determines what comes back: - 📄 A **job-search URL** → returns job listings - 🏢 A **company-profile URL** (LinkedIn or Wellfound) → returns a company record There is **no separate `/companies` endpoint** — the same pipeline handles both job and company data based on the submitted URL. ### ⚡ Want results instantly? `GET /jobs/search` runs a **synchronous** keyword search across the **13 fast sources** in parallel and returns results in the same response — no polling required. Add `linkedin` to the `sources` parameter and LinkedIn is queued separately, with a `jobId` you can poll for the LinkedIn results.

📥 Example — submit and poll

```bash # 1. Submit curl --request POST \ --url 'https://api.jobsapi.dev/jobs' \ --header 'X-RapidAPI-Key: YOUR_API_KEY' \ --header 'X-RapidAPI-Host: YOUR_API_HOST' \ --header 'Content-Type: application/json' \ --data '{ "input": { "url": "https://www.linkedin.com/jobs/search/?keywords=backend%20engineer", "source": "linkedin", "target": "job-search" } }' # → { "jobId": "a1b2c3d4-...", "status": "queued" } # 2. Poll for records curl --request GET \ --url 'https://api.jobsapi.dev/jobs/a1b2c3d4-.../records' \ --header 'X-RapidAPI-Key: YOUR_API_KEY' \ --header 'X-RapidAPI-Host: YOUR_API_HOST' ```

⚡ Example — instant multi-source search

```bash curl --request GET \ --url 'https://api.jobsapi.dev/jobs/search?query=backend%20engineer&sources=himalayas,remotive,ashby,lever,greenhouse' \ --header 'X-RapidAPI-Key: YOUR_API_KEY' \ --header 'X-RapidAPI-Host: YOUR_API_HOST' ```

--- ## 🤖 MCP — Use JobsAPI.dev with AI Agents JobsAPI.dev supports **Model Context Protocol (MCP)**, allowing compatible AI assistants and agentic applications to use JobsAPI.dev as a set of tools instead of integrating every REST endpoint manually. With MCP, an AI agent can: - 🔎 Search jobs across supported sources - 📤 Submit asynchronous scraping jobs - 📊 Check job status - 📦 Retrieve job results - 🗂️ Retrieve structured records - 📈 Check API usage and remaining quota ### 🔀 RapidAPI MCP If you're using JobsAPI.dev through RapidAPI, **RapidAPI's MCP integration** lets compatible AI clients use the API directly through your existing RapidAPI subscription and credentials. No separate MCP server is required. The underlying JobsAPI.dev infrastructure remains the same: ```mermaid flowchart LR A[🤖 AI Agent] --> B[RapidAPI MCP] B --> C[🚀 JobsAPI.dev] C --> D[🗂️ 15 Job & Company Data Sources] style A fill:#6E56CF,color:#fff style B fill:#2ea043,color:#fff style D fill:#8A63D2,color:#fff ``` ### 🔌 Direct MCP (alternative) Prefer to connect straight to JobsAPI.dev instead of going through RapidAPI? A direct endpoint is also available: ``` https://api.jobsapi.dev/mcp ``` **Direct MCP authentication:** ``` Authorization: Bearer YOUR_API_KEY ``` Use the same API key you'd use with the REST API. ### 🛠️ Available MCP Tools | Tool | Purpose | |---|---| | `search_jobs` | Search jobs across supported sources | | `submit_scrape_job` | Submit a job or company URL for asynchronous scraping | | `get_job_status` | Check the status of a submitted job | | `get_job_result` | Retrieve a completed job result | | `get_job_records` | Retrieve structured records from a completed job | | `get_usage` | Check plan, usage and remaining quota | ### 🔄 MCP Workflow Instead of manually orchestrating REST requests: ```mermaid flowchart LR A[🤖 AI Agent] --> B[🛠️ MCP Tool] B --> C[🚀 JobsAPI.dev] C --> D[📦 Job & Company Data] style A fill:#6E56CF,color:#fff style B fill:#8A63D2,color:#fff style C fill:#A78BFA,color:#fff style D fill:#2ea043,color:#fff ``` The same flow applies to an asynchronous scrape — `submit_scrape_job` → poll `get_job_status` → `get_job_records` — just via MCP tool calls instead of REST endpoints. This gives developers **two ways** to use JobsAPI.dev with AI agents:

> MCP is an additional interface to JobsAPI.dev — the underlying job and company data pipeline remains the same. --- ## 📄 Job Record Fields > Field availability varies by source — LinkedIn (with enrichment) returns the richest set. | Field | Description | Notably strong on | |---|---|---| | `jobId` / `jobUrl` | Identifiers | All sources | | `title` / `companyName` / `location` | Core listing info | All sources | | `employmentType` | Full-time, Contract, etc. | 11 of 15 sources | | `jobDescription` | Full posting text | 14 of 15 sources | | `postingDate` / `postingAgeDays` | When it was posted | 14 of 15 sources | | `seniority` | Experience level | LinkedIn (near-exclusive) | | `salaryRaw` / `salaryCurrency` | Compensation, when disclosed | 11 of 15 sources | | `applicantCount` | Number of applicants | LinkedIn only | | `workplaceType` | Remote / Hybrid / Onsite | Ashby, Lever, SmartRecruiters, Reed, Arbeitnow, Wellfound | --- ## 🏢 Company Intelligence Submit a LinkedIn or Wellfound **company URL** instead of a job URL to get a company record: | Field | Description | |---|---| | `companySize` / `companyStage` | Headcount band, funding stage | | `totalRaisedAmount` | Total funding raised (USD) | | `openJobCount` / `activelyHiring` | Live hiring signal | | `hiringSignals` | Badges — "Actively Hiring", "Top Investors", etc. | | `markets` / `locations` | Industry and geographic tags | --- ## 💼 What You Can Build

### 🎯 Recruiting & Talent Platforms Aggregation tools, candidate discovery, hiring dashboards	### 🤖 AI Applications Job matching, career assistants, resume-to-job matching
### 📊 Market Intelligence Hiring trends, salary ranges, geographic demand	### 🏢 Company Intelligence Hiring activity trackers, sales & recruiting intelligence

--- ## 📊 Usage & Credits Every plan includes a monthly request quota. Check your current usage anytime: ```bash curl --request GET \ --url 'https://api.jobsapi.dev/usage' \ --header 'X-RapidAPI-Key: YOUR_API_KEY' \ --header 'X-RapidAPI-Host: YOUR_API_HOST' ``` Returns your plan limits, current period usage, and remaining quota. > Requests made through JobsAPI.dev are subject to the applicable usage limits and credit controls for the connection method you're using (REST, Direct MCP, or RapidAPI). --- ## 🧪 Getting Started

### 🌐 REST API 1. Subscribe to a plan on RapidAPI 2. Grab your `X-RapidAPI-Key` 3. `POST /jobs` with a job-search or company URL — or use `GET /jobs/search` for instant results 4. Poll `GET /jobs/{id}/records` once your job succeeds 5. Receive structured JSON

### 🤖 MCP 1. Connect your MCP-compatible client 2. Use the appropriate JobsAPI.dev or RapidAPI MCP connection 3. Authenticate using the credentials required by that connection 4. Let your AI agent call the available JobsAPI.dev tools

### **No platform accounts. No scraping infrastructure. Just data.**

---

### 🚀 **JobsAPI.dev — job and company data, one API, zero platform headaches.** **[https://jobsapi.dev](https://jobsapi.dev)**