Name: Job Opportunities API — Employer-Direct Jobs Data
Brand: tzekos
SKU: api-tzekos-jobopportunitiesapi
Availability: InStock
Author: API Market

## The jobs API you can audit before you pay

Most jobs APIs ask you to trust a number in a marketing page. This one asks you to check.

Every claim below is verifiable with an unauthenticated `curl`, right now, before you create an account or spend anything. That includes the numbers that make us look bad.

```bash
curl https://api.jobopportunitiesapi.org/public/coverage
```

That single endpoint returns live listing counts, per-field completeness, the number of rows we deliberately withhold, and the names of every source we refuse to republish. It is keyless, CORS-open, timestamped, and it tells you when it was last measured so you can see whether you are reading a stale figure.

---

## What you get

**Job postings collected from the employer's own careers page or applicant tracking system.** Not scraped from LinkedIn or Indeed. Not resold from an aggregator. When a record says a company is hiring, the apply link goes to that company's own application page.

As measured on the live endpoint at the time of writing:

| | |
|---|---|
| Live, servable postings | ~3.77 million |
| Employers resolved | ~220,000 |
| Countries represented | 247 |
| Posted in the last 7 days | ~347,000 |
| Closed postings with a recorded closure | ~2.35 million |
| Rows we hold and deliberately never serve | ~1.20 million |

Do not take those figures from this page. Take them from `/public/coverage`, which is where we take them from too.

---

## The three things that actually make this different

### 1. Every served row links to the employer, not to a redirect

`apply_url` coverage is **100%** of servable rows, and it points at the employer's own application page. No aggregator interstitials, no tracking redirects, no dead links into a board that no longer carries the job.

This is the thing that breaks most quietly in jobs data. A record can be perfectly formed and still be worthless if the link lands on a search page. If you are building a product where a user clicks through to apply, or where you attribute an application, this is the field that decides whether your product works.

```bash
curl "https://api.jobopportunitiesapi.org/public/jobs?country=NL&limit=3"
```

### 2. Every field tells you whether we were told it or inferred it

Every job object carries a `field_sources` block with one entry per field, valued `published`, `inferred` or `absent`:

- **`published`** — the value came out of the posting itself.
- **`inferred`** — we produced it. It may be right; it is still ours, not the employer's.
- **`absent`** — there is no value. Deliberately distinct from `inferred`, so an empty field can never be mistaken for a confident guess.

`title`, `company`, `location`, `employment_type`, `posted_at` and `description` are taken from the posting. `category` and `seniority` are **always** ours — a model reads the title and assigns them. `remote`, `salary` and `source_type` are published when the employer states them and inferred when we work them out.

Nobody else ships this. It means you can decide, per row and per field, what you are willing to build on — instead of discovering six months in that a filter you trusted was a guess all along.

### 3. We publish our own gaps, in the same place as our strengths

Current per-field completeness, straight off the live endpoint:

| Field | Coverage |
|---|---|
| `apply_url` | 100% |
| `category` | 95.3% |
| `description` | 88.1% |
| `country` | 76.2% |
| `city` | 70.9% |
| `remote` | 60.9% |
| `seniority` | 44.4% |
| `salary` | 7.8% |

**Salary coverage is 7.8%, and it is concentrated in the US.** If you are building a compensation benchmarking product, this is not your dataset, and we would rather you learned that from this paragraph than from a trial. Outside the US, salary is not a filter you can build on.

We publish this table keyless because a completeness number you cannot verify is a marketing claim, and we would rather be checkable than flattering.

---

## Where the data comes from

Three source classes, each tagged on the record so you can filter or audit by it:

| Source class | Providers | Live rows |
|---|---|---|
| Career-site parsing (direct) | 3 | ~2.56M |
| ATS platform APIs | 16 | ~1.18M |
| Public employment agency feeds | 3 | ~38.9K |

ATS coverage includes Greenhouse, Lever, Workday, SmartRecruiters and others — structured requests to public job-listing endpoints, not scraping.

### The 19 sources we refuse to republish

We also collect from job boards and aggregators for internal comparison. **None of it is ever served to you.** Those rows sit under a licence hold — currently ~1.20 million of them — and `/public/coverage` names all 19 refused sources so you can check the list yourself:

`adzuna`, `apify_all_jobs`, `apify_fantastic_jobs`, `apify_job_listings`, `apify_xing`, `arbeitnow`, `arbeitsagentur`, `careerjet`, `eures`, `france_travail`, `himalayas`, `jobicy`, `jooble`, `landing_jobs`, `remoteok`, `remotive`, `the_muse`, `weworkremotely`, `working_nomads`.

If you resell or redistribute, this matters more than volume. It is the difference between a dataset that survives a procurement review and one that quietly carries somebody else's terms of service into your product.

---

## The closure ledger

Most jobs APIs tell you what is open. Very few tell you what closed, and almost none tell you when.

Every posting that leaves the ledger keeps a row with the date it closed and why — either it expired at the source, or it stopped appearing. That is ~2.35 million closed postings you can query, and it is what makes hiring-signal work possible: you cannot measure how long a role stayed open, or how fast a team hires, from a snapshot of what is open today.

```bash
# everything that changed since a timestamp
curl -H "x-api-market-key: $API_MARKET_KEY" \
  "https://prod.api.market/api/v1/tzekos/jobopportunitiesapi/v1/changes?since=2026-08-01T00:00:00Z"
```

Nothing disappears silently. If a row leaves, there is a record saying so.

---

## Endpoints

Base URL: `https://prod.api.market/api/v1/tzekos/jobopportunitiesapi`

Every request must include your API.market key in the `x-api-market-key` header. No other key, token or account is required — subscribe to a plan on this page and your key works straight away. You can find or create your key on the [API Keys](https://api.market/account/apiKeys) page.

Endpoint paths are appended to the base URL, so `/v1/jobs` becomes `https://prod.api.market/api/v1/tzekos/jobopportunitiesapi/v1/jobs`.

```bash
curl "https://prod.api.market/api/v1/tzekos/jobopportunitiesapi/v1/jobs?country=NL&limit=3" \
  -H "x-api-market-key: $API_MARKET_KEY"
```

| Endpoint | What it does |
|---|---|
| `/jobs` | Search and filter live postings |
| `/jobs/{id}` | A single posting |
| `/jobs/closed` | Postings that have closed |
| `/jobs/expired` | Expiry feed |
| `/companies` | Resolved employers |
| `/companies/{slug}` | A single employer |
| `/changes` | Delta feed since a timestamp |
| `/export` | Resumable bulk export, cursored with `?after=` |
| `/meta/facets` | Available filter values |
| `/meta/freshness` | When the corpus was last verified |
| `/meta/providers` | Source list |
| `/me` | Your key, plan and usage |

Filter by country, city, category, seniority, employment type, remote status, provider and posting age. Full OpenAPI 3.1 spec at `https://jobopportunitiesapi.org/openapi.json`.

Endpoint access varies by plan — see the plan cards below for what each one includes. Every plan returns the same `field_sources` provenance block; nothing is stripped down for a cheaper tier.

---

## Plans

Each call returns up to 20 records, so "calls included" and "records included" are the same number divided by 20.

| Plan | Price | Included | Beyond that | Endpoints |
|---|---|---|---|---|
| **PAYGO** | $0/mo | — | $0.012 per call | 9 of 11 |
| **Pro** | $29/mo | 10,000 calls (~200,000 records) | Refused — no overage | 6 of 11 |
| **Ultra** | $119/mo | 50,000 calls (~1,000,000 records) | $0.008 per call | All 11, including the closure ledger (`/jobs/closed`, `/jobs/expired`) and the delta feed (`/changes`) |

Pro's limit is hard: once the month's 10,000 calls are spent, requests stop rather than billing further — predictable, no surprise invoice. PAYGO and Ultra keep serving past their included volume and bill per extra call.

Start on PAYGO with real data before committing to a plan — the response shape and the provenance block are identical across every tier.

---

## Who this is for

**A good fit if you are building:** hiring-signal or sales-intelligence products, recruitment technology, labour-market dashboards, staffing analytics, or anything where a click has to land on a real application page and you need to defend where a field came from.

**A bad fit if you need:** the largest possible catalogue regardless of provenance, comprehensive salary data outside the US, or a multi-year historical time series. We do not have those, and competitors who do will tell you so — we would rather say it first.

We do not claim to be the biggest jobs API. Several are larger. What we claim is that you can verify every statement on this page in about two minutes, without an account, and that the gaps are published next to the strengths rather than behind a sales call.

---

## Start in one command

```bash
curl "https://api.jobopportunitiesapi.org/public/jobs?country=GB&limit=1"
```

No key required. Look at `field_sources` in the response — that object is the product.

Full documentation, guides and examples: `https://jobopportunitiesapi.org/api`
AI disclosure (exactly which fields a model produces): `https://jobopportunitiesapi.org/ai`

---

## Contact Us

If you have any questions or need support, you can reach out to us through the chat available on this page, or email us at hello@magicapi.com.


Job postings from employer career pages and ATS platforms, never aggregators. 100% direct apply URLs, per-field provenance, and our own gaps published keyless.

Job Opportunities API — Employer-Direct Jobs Data

PAYG

TZEKOS[dot]EU

Ultra

Employer-direct postings with per-field provenance. Every row links to the company's own apply page; every field says whether we were told it or inferred it.