Job Opportunities API

Check the data. Then trust it.

start

Moving from Fantastic.jobs

Their `_advanced` boolean expressions work here as written, and their parameter names are accepted as aliases. This page lists every difference, side by side.

Last verified 2026-11-10 · Assumes: That you have a working Fantastic.jobs integration and a JOA API key. · Markdown copy

1What you change, and what you do not

Change the host, the path and the key. Keep the boolean expressions: (react | vue) & (node | golang) & !aws means the same thing on both APIs.

In depthWhy it exists, what it is not, what people get wrong
  • Host and path. Their job routes are /v1/active-ats, /v1/active-jb and the expired- and modified- variants. Ours is one route, GET https://api.jobopportunitiesapi.org/v1/jobs, for every source, with GET /v1/jobs/closed for postings that came off their source and GET /v1/changes for the delta feed.
  • Key. Authorization: Bearer <key>. See authentication.
  • Boolean notation. & | ! :* <-> <N>, single-quoted phrases and parentheses are part of our grammar, with the same precedence (! before & before |). The full grammar: the query grammar.
  • Parameter names. title_advanced, description_advanced and organization_advanced are accepted as aliases (the table below). location_advanced is not: places are structured filters here.

2The parameter map

Each Fantastic.jobs name, the JOA parameter it maps to, and the difference if there is one.

In depthWhy it exists, what it is not, what people get wrong
Fantastic.jobsJOADifference
title_advanced (also advanced_title_filter, title_filter)titleNone in meaning: a boolean search of the job title.
titletitleTheir bare title is Google-style (space is AND, quotes, leading -). Ours takes the same and the full grammar.
description_advanced (also advanced_description_filter, description_filter)description_containsTheirs searches the title and the description as one text. Ours searches the advert text only, and live postings only. Adverts almost always repeat the title, but a term that is only in the title is not matched: add title= for that.
descriptionq or description_containsNot an alias, because it is ambiguous here: q searches title, company and location; description_contains the advert text.
organization_advanced (also advanced_organization_filter)company_name_containsNone in meaning: a boolean search of the employer name.
organization, exclude_organizationcompany_name_contains or companyRefused with a 400 naming the JOA parameter. Exclude with company_name_contains=!(Amazon | Meta).
location_advanced, locationcountry, city, state, regionlocation_advanced is refused with a 400 naming these. Our places are normalised fields (ISO country codes), not a text to search: a country name is present in the location text of a minority of the rows of that country, so a text search would silently miss most of them.
date_posted_gte, date_posted_ltposted_after, posted_beforeNot aliases. listed_after is the time a row reached the API, the one to poll on.
limit, offsetlimit, cursorlimit is 1 to 200. Paging is keyset: follow next_via; offset is refused.

3Their documented examples, side by side

Every example from the Fantastic.jobs advanced searching guide, and the JOA request that answers it.

In depthWhy it exists, what it is not, what people get wrong
The alias names work too: title_advanced=... is the same request as title=....
Fantastic.jobsJOA
title_advanced=(AI | 'machine learning' | robotics) & !marketingtitle=(AI | 'machine learning' | robotics) & !marketing
title_advanced=senior & (python | rust) & !stafftitle=senior & (python | rust) & !staff
title_advanced=project <-> manag:*title=project <-> manag:*
title_advanced='data engineer' | 'data scientist' | 'analytics engineer'title='data engineer' | 'data scientist' | 'analytics engineer'
description_advanced='remote work' & (equity | 'stock options') & !contractordescription_contains='remote work' & (equity | 'stock options') & !contractor
description_advanced=(kubernetes | k8s) & terraform & awsdescription_contains=(kubernetes | k8s) & terraform & aws
location_advanced='United States' & !Californiacountry=US, then drop rows with state CA on your side, or list the states you want in state=
location_advanced=Germany & !(Berlin | Munich)country=DE, then drop the two cities on your side, or list the cities you want in city=
location_advanced='New York' | 'San Francisco' | Bostoncity=New York,San Francisco,Boston
organization_advanced=University & !Harvardcompany_name_contains=University & !Harvard
organization_advanced=(Microsoft | Google | Apple)company_name_contains=(Microsoft | Google | Apple)
organization_advanced=OpenAI | 'Open AI'company_name_contains=OpenAI | 'Open AI'
Their combined example, on JOA
curl -s -H "Authorization: Bearer $JOA_KEY" --get \
  https://api.jobopportunitiesapi.org/v1/jobs \
  --data-urlencode 'title=(engineer | developer) & !manager' \
  --data-urlencode 'country=US' \
  --data-urlencode 'company_name_contains=!(Amazon | Meta | Google)' \
  --data-urlencode "description_contains=remote & (equity | 'stock options')" \
  --data-urlencode 'limit=5'

4Where the grammars differ

Ours accepts everything theirs does, plus a few forms theirs refuses. Errors are 422 here, 400 there.

In depthWhy it exists, what it is not, what people get wrong
  • A space is AND here. title_advanced=software engineer is a 400 on Fantastic.jobs, which requires an explicit operator between terms. Here it is software & engineer.
  • Word operators too. AND, OR and NOT (upper case) work as well as & | !, and -word excludes. Quote "OR" to search for the word.
  • Prefix. manag:* and manag* are the same. A prefix needs 3 or more characters. A bare word is always exact, as on Fantastic.jobs.
  • Phrases. 'machine learning' and "machine learning" are both the words adjacent and in order.
  • Errors. A malformed expression is a 422 query_syntax (Fantastic.jobs answers 400), and the message names the character position. A boolean expression of more than 32 terms or parentheses nested more than 8 deep is a 422 query_too_complex. Values may be up to 500 bytes. A refused request costs no records.
  • Matching. Case-insensitive and accent-insensitive. OpenAI and Open AI are different words here too: list both.

This page was rendered 17 November 2026, 07:47 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.