api
Keyless access
What /public/* gives you with no account: real aggregate numbers against the live ledger (coverage, facets, freshness, providers, the price list, the spec). Job and company ROWS are not part of that anymore: they need a free key, full stop.
1What you get without an account
Every STATISTICAL read shape the API has, against the live ledger, with no key: aggregate counts, coverage, provenance, providers, freshness, the price list and the spec. Rows (individual jobs and companies) are not part of the keyless surface: GET /public/jobs, /public/jobs/{id}, /public/companies and /public/companies/{slug} now require a key, exactly like their /v1 twins.
In depthWhy it exists, what it is not, what people get wrong
Until 2026, the four listing routes above answered keylessly too, capped at one 50-row page per query with no cursor. That was meant to make evaluating free and extracting expensive, but a page cap alone does not stop a patient caller: pacing itself just under the keyless rate limit, an anonymous script could still change the filters and walk the whole ledger, one bounded page at a time, forever. The rate limit made that slow. It did not make it impossible, and "slow" was never the offer. The four routes now return 401 to anyone who is not jobopportunitiesapi.org's own page rendering, with or without a key: rows have exactly one door now, /v1, metered on a plan.
What is unchanged, and stays open on purpose: every STATISTICAL route reads a precomputed aggregate or a small bounded audit table, never a row-by-row walk of the ledger, so none of them can be extracted the way /public/jobs could. Coverage, facets, freshness and the provider table carry the entire "check us before you buy" pitch, and none of that needed row-level access to make.
Exact contractTypes, defaults, ranges, errors, edge cases
| Keyless endpoint | Keyed equivalent | Difference |
|---|---|---|
| (needs a free key) | /v1/jobs | No keyless tier anymore. Was capped at one 50-row page; now 401 without a key, whoever asks. |
| (needs a free key) | /v1/jobs/{id} | Same change. Slug or uuid on /v1. |
| (needs a free key) | /v1/companies | Same change. |
| (needs a free key) | /v1/companies/{slug} | Same change. |
/public/facets | /v1/meta/facets | Identical data. Unaffected (STATISTICAL, stays keyless). |
/public/providers | /v1/meta/providers | Identical data. Unaffected. |
/public/freshness | /v1/meta/freshness | Identical data. Unaffected. |
/public/coverage | (no keyed twin) | The canonical coverage report. Unaffected. |
/public/coverage/countries | not available | Per-country coverage. Unaffected. |
/public/coverage/employers | not available | Per-employer coverage. Unaffected. |
/public/stats | not available | Convenience summary; see why it looks different. Unaffected. |
/public/plans | not available | The price list. Unaffected. |
/public/openapi.json | /v1/openapi.json | The same document. Unaffected. |
/public/ai-prompt | not available | An integration brief, from the API host, for a model. Unaffected. |
| (no keyless twin) | /v1/changes | The delta feed is licensed. |
| not available | /v1/jobs/expired | Same. |
| not available | /v1/jobs/closed | Same. |
| not available | /v1/export | Bulk export is licensed. |
$ A=https://api.jobopportunitiesapi.org $ curl -s "$A/public/coverage" | jq '{live_listings, employers, countries, measured_at, stale}' { "age_seconds": 2142, "as_of": "2026-10-27", "closed_listings": 8653347, "closure_date_note": "JOA records as the closure date the day its daily verification confirmed that an advert had gone. Before late September 2026 that verification ran in large catch-up batches, so closure dates recorded before then show when JOA confirmed a closure, not when the employer closed the role; daily verification applies from late September 2026.", "countries": 236, "definitions": { "as_of_times": "/public/facets and /public/providers carry the latest snapshot (every 3 hours, generated_at). /public/coverage, /public/coverage/countries, /public/stats, /public/site-stats and the website carry the snapshot frozen once a day (as_of, measured_at = that snapshot's generated_at). Two surfaces agree exactly when their timestamps are equal; otherwise each states its own.", "closed_listings": "Roles that came off their source, retained with a closure date and reason. JOA records as the closure date the day its daily verification confirmed that an advert had gone. Before late September 2026 that verification ran in large catch-up batches, so closure dates recorded before then show when JOA confirmed a closure, not when the employer closed the role; daily verification applies from late September 2026.", "countries": "Distinct country codes with at least one served row. Only ISO 3166-1 alpha-2 codes (plus XK, Kosovo) are countries; any other value is published as country unknown and filtered by no country= value.", "employers": "Distinct employers with at least one served row.", "ledger_rows": "live_listings + withheld_listings + closed_listings. It reconciles exactly.", … 178 more lines
2The limits, exactly
STATISTICAL routes carry no per-address limit at all: they are O(1) reads of a precomputed snapshot or a small bounded table, so there is nothing to walk. The four listing routes still sit behind the old IP throttle (about two requests a second, a burst of ten, forty a minute, a ten-minute block on breach) as a second layer, but it no longer matters much in practice: since the key requirement is checked first for every caller but jobopportunitiesapi.org's own rendering, an anonymous or wrongly-keyed request gets 401 regardless of how it is paced.
In depthWhy it exists, what it is not, what people get wrong
The throttle numbers below describe api/publiclimit.go, which still wraps the four listing routes and has not changed. What changed is what sits behind it: those four routes used to serve rows to anyone who respected the rate limit; now they serve rows to nobody but the website's own page rendering, whatever the rate limit would have allowed through. The throttle is defence in depth, not the boundary: the boundary is the key requirement below.
For history: the page cap mattered more than the rate, and neither was ever enough on its own. Before either existed, /public/jobs served 294 rows a second to an unauthenticated caller with working keyset pagination: the entire live ledger in a bit over two hours single-threaded. The paid entry plan is €80 a month for sixty thousand records, and the keyless path was handing that over every three and a half minutes. Capping the page size and rate-limiting the caller slowed that down; it took requiring a key on the route itself to actually stop it.
Exact contractTypes, defaults, ranges, errors, edge cases
| Limit | Value | Applies to |
|---|---|---|
| Sustained rate | 2 requests/second | Per client IP, on the four listing routes only. STATISTICAL routes carry none. |
| Burst | 10 requests | The bucket's capacity. |
| Window ceiling | 40 requests/minute | Per client IP. |
| Block on breach | 10 minutes | 429 with Retry-After. Not permanent, and moot anyway once the key check below refuses the request first. |
| Key required | always, for rows | GET /public/jobs, /public/jobs/{id}, /public/companies, /public/companies/{slug} all answer 401 to anyone without a valid Explore-or-better key on /v1. |
$ curl -s 'https://api.jobopportunitiesapi.org/public/jobs?limit=2' { "error": "key_required", "message": "Listings require an API key. Get a free Explore key (no card) at https://jobopportunitiesapi.org/register. Statistics under /public/stats, /public/facets and /public/coverage remain open.", "docs": "https://jobopportunitiesapi.org/api" }
One exemption exists on the four listing routes and it does not help a third party: the website's own server-side rendering, which authenticates with a header the browser never sees and no external caller can send. There is no Host-based or address-based exemption: a request that merely arrives from an internal-looking address is not, on its own, treated as trusted.
3Getting the rows the statistics describe
The statistics above tell you whether the data is worth having. Reading an actual job or company, even one, now needs the free key. There is no smaller step in between.
In depthWhy it exists, what it is not, what people get wrong
The free Explore plan is not a trial: it does not expire, and it needs no card. It is, as of PUBLIC_LISTINGS_GATE, the only way to read a job or company row from this API without being jobopportunitiesapi.org's own server. For a lot of small projects it is also the end of the story: it replaces nothing you had before, because there was no smaller keyless row tier for it to replace.
- You want any row at all.
/v1/jobs,/v1/jobs/{id},/v1/companies,/v1/companies/{slug}all need a key now, Explore included. - You need to page. Any key pages; the keyless single-page tier no longer exists.
- You need the delta feed.
/v1/changesand/v1/jobs/expiredrequire a plan withdelta_feed. Polling a listing endpoint and diffing is the alternative, and it costs far more records than the feed does. - You need bulk export.
/v1/exportrequiresbulk_export. - You need throughput. The per-minute ceiling on a paid plan is measured in hundreds rather than tens.
- You need closed rows.
status=closedand/v1/jobs/closedare paid-only.
Exact contractTypes, defaults, ranges, errors, edge cases
| Plan | Price | Records / month | Requests / day | Requests / min | Delta feed | Bulk export |
|---|---|---|---|---|---|---|
Exploreexplore | Free | 1,000 | 5,000 | 30 | no | no |
Starterstarter | €29/month | 10,000 | 20,000 | 60 | no | no |
Growthgrowth | €80/month | 60,000 | 100,000 | 120 | yes | no |
Signalsignal | €299/month | 400,000 | 400,000 | 300 | yes | yes |
Scalescale | €899/month | 2,000,000 | 1,000,000 | 600 | yes | yes |
Starter (annual)starter_annual | €261 | 10,000 | 20,000 | 60 | no | no |
Growth (annual)growth_annual | €720 | 60,000 | 100,000 | 120 | yes | no |
Signal (annual)signal_annual | €2,691 | 400,000 | 400,000 | 300 | yes | yes |
Scale (annual)scale_annual | €8,091 | 2,000,000 | 1,000,000 | 600 | yes | yes |
Rendered from /public/plans when this page was built. Only purchasable plans appear there, so this table is the price list: if a plan is not here, you cannot buy it. Compare on /pricing.
Note that the ladder is about records, not requests, above the free tier. That is the single most commonly misunderstood thing about the pricing and it is explained properly in the record meter. Read it before comparing the numbers above with another vendor's, because a request-priced API and a record-priced one are not comparable line by line.
This page was rendered 27 October 2026, 11:28 UTC. Every figure on it comes from the endpoint named beside it, and every published request is re-sent against the live API before this site is allowed to build. If something here is wrong, the thumbs-down above reaches a person.