Jobgether Jobs Lookup — Remote Jobs by Category

Paste one or more Jobgether remote-jobs category slugs and get every current posting in each — title, company, location, contract type, remote policy, average salary, required skills and a direct apply link. This calls Jobgether's own API directly: no API key, no scraping of the rendered page.

Who it's for

The accountable_eel catalogue also covers remote-jobs feeds — actors that take a category or a keyword rather than a company, and return every current posting that matches as one flat, stably-named row. Each reads the board's own API rather than scraping rendered HTML, so the columns don't move when the site is redesigned, and an AI agent or a Clay column that reads the schema once keeps working. Pricing is pay-per-event and per posting: you pay for postings actually returned, and nothing at all for a category that comes back empty. No seat licence, no monthly minimum, no credit system to decode. This one covers Jobgether's remote-jobs categories.

Why this one

• Reads Jobgether's own API. The same JSON their site is built on — no CSS selectors that break when the page is redesigned.
• You don't pay for an empty category. A slug that doesn't exist, or one with nothing currently posted, comes back found: false and is never billed.
• Salary and skills come parsed. salaryAverage is a number and skills is a de-duplicated array, so you can filter and sort without cleaning strings first.
• One row per category, or one per job. Turn on expandRows when you want postings as their own rows for a table.
• isEasyApply tells you the application route. Useful when you're routing candidates and care whether an application stays on Jobgether or bounces to the company's own ATS.

What you get

One row per input category by default, with postings nested in jobs. Turn on expandRows to get one row per posting. Field names are stable and won't be renamed between runs.

Field	Type / format	Description
query	text	The category slug exactly as submitted.
found	boolean	Whether the category resolved to at least one current posting. Gates billing.
status	text	OK, NOT_FOUND (unknown slug or nothing posted), or BAD_FORMAT.
category	text	The normalized category slug.
jobCount	number	Postings returned for this category in this run.
totalAvailable	number	Total Jobgether reports for the category — shows when jobCount is a subset.
jobs	array	The postings, each with the fields below.
title	text	Job title.
company	text	Hiring company name.
companySlug	text	Jobgether's slug for the company, stable for joins.
location	text	Countries the role is open to, comma-separated, or the stated location requirement.
remoteOfferType	text	Jobgether's remote classification for the role.
contractType	text	Full-time, contract, and so on.
salaryAverage	number	Average of the posted salary range. null when no salary is published.
skills	array	Required skills, de-duplicated.
postedAt	date (ISO 8601)	When the posting was created.
url	link	The posting's Jobgether page.
applyUrl	link	Direct apply link, which may point at the company's own ATS.
isEasyApply	boolean	Whether the application can be completed on Jobgether itself.
scrapedAt	date (ISO 8601)	When this actor fetched the row.

Price

$1 per 1,000 job postings, plus a $0.005 start fee. Misses (found:false) are never charged.

You're billed per job posting actually returned, not per category and not per run. A category slug that doesn't exist, or one with nothing currently posted, costs nothing. A category returning 300 postings costs about $0.30 at the FREE-tier rate, less on paid Apify plans. The start fee is per run, so batch your categories into one run rather than running them separately.

How to use

1. In the Apify Console. Open the actor page and click Start — the items field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. Via the API. Call it directly with a POST request — no Console needed once you have an API token:

   curl "https://api.apify.com/v2/acts/accountable_eel~jobgether-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"items":["it-development"]}'
   

3. On a schedule. Save this actor as an Apify Task with the input you want, then add a Schedule (hourly, daily, weekly) so it runs on its own — no server of your own required.

1. Paste your category slugs into items — the slug from jobgether.com/remote-jobs/<slug>.
2. Run the actor. Each category is fetched in parallel up to maxConcurrency.
3. Turn on expandRows if you want one row per posting rather than postings nested per category.
4. Read the dataset. Empty categories are written as found: false rows and are never charged.

Common ways teams use this:

• Build a remote-jobs board for a niche by pulling one or more categories on a schedule.
• Track salary benchmarks across a category over time using salaryAverage.
• Find companies hiring remotely in a discipline by grouping postings on company.
• Feed a candidate-matching pipeline with skills already parsed into an array.
• Route applications intelligently using isEasyApply to separate on-platform applies from ATS hand-offs.

Input

{
  "items": [
    "it-development"
  ]
}

One remote-jobs category slug per line, e.g. it-development, customer-service, sales, marketing, design, human-resources, finance, product, data-science. Matches the slug in jobgether.com/remote-jobs/

{
  "items": ["it-development", "design"],
  "expandRows": false,
  "onlyFound": false,
  "maxConcurrency": 5
}

items is your list of Jobgether category slugs — the segment after /remote-jobs/ in a Jobgether URL. Common slugs include it-development, customer-service, sales, marketing, design, human-resources, finance, product and data-science. Turn on testRun to try a small sample first. expandRows switches between one row per category and one row per posting. onlyFound drops empty categories, maxResults stops the run early, includeKeywords and excludeKeywords filter rows by content, and columns picks which fields come back.

Sample output

query	found	status	category	jobCount	totalAvailable	jobs	title	company	companySlug	location	remoteOfferType	contractType	salaryAverage	skills	postedAt	url	applyUrl	isEasyApply	scrapedAt
it-development	true	OK	it-development	50	13231	<all postings found (full list)>	Technical Lead Microsoft 365/ Microsoft Cloud (m/w/d) - Remote	ARES Consulting GmbH	aresconsultinggmbh	Germany	Full Remote	Full time	96000	["Microsoft 365","Azure Cloud Services","Integrated Mathematics","Requirements Management"]	2026-08-23T15:30:21.896Z	https://jobgether.com/offer/6a8b120d1de6f4542a536c16-technical-lead-microsoft-365-microsoft-cloud-m-w-d---remote	https://ares.jobs.personio.com/job/2126912	false	2026-08-24T11:22:32.708Z

That table lists every available column. With expandRows on, a single posting reads like this:

{
  "query": "it-development",
  "found": true,
  "status": "OK",
  "category": "it-development",
  "jobCount": 120,
  "totalAvailable": 340,
  "title": "Senior Backend Engineer",
  "company": "Acme Remote",
  "companySlug": "acme-remote",
  "location": "Spain, Portugal, Poland",
  "remoteOfferType": "Fully remote",
  "contractType": "Full-time",
  "salaryAverage": 78000,
  "skills": ["Go", "PostgreSQL", "Kubernetes"],
  "postedAt": "2026-08-19T08:31:00Z",
  "url": "https://jobgether.com/offer/senior-backend-engineer-acme",
  "applyUrl": "https://boards.greenhouse.io/acme/jobs/123456",
  "isEasyApply": false,
  "scrapedAt": "2026-08-24T06:01:11.918Z"
}

A category with nothing currently posted still returns a row, and is never charged:

{
  "query": "not-a-real-category",
  "found": false,
  "status": "NOT_FOUND",
  "scrapedAt": "2026-08-24T06:01:11.918Z"
}

Miss rows are written so you can see exactly which slugs failed rather than diffing your input list against the output. Set onlyFound to drop them.

Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

curl "https://api.apify.com/v2/acts/accountable_eel~jobgether-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"items":["it-development"]}'

n8n. Add an HTTP Request node: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~jobgether-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body Content Type JSON, JSON Body {"items":["it-development"]} (swap in an expression from an earlier node for a real value).

Clay. Add an "HTTP API" column: Method POST, URL https://api.apify.com/v2/acts/accountable_eel~jobgether-jobs-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>, Body {"items":["{{category search}}"]}, mapping the row's category search into the items array.

MCP. In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "Jobgether Jobs Lookup | Apify" — the agent will find and run this actor.

Tips

• Compare jobCount against totalAvailable. When they differ, you're looking at a subset of what Jobgether has for that category, not the whole thing.
• Treat salaryAverage as an average, not a range. It's the midpoint of the posted band, so it's fine for benchmarking and misleading for negotiation.
• applyUrl often leaves Jobgether. Check isEasyApply before assuming an application can be completed in one place.
• Batch categories into one run. The start fee is per run, so five categories in one run costs one start fee rather than five.
• Join on companySlug, not company. Display names get edited; slugs are stable.

vs. alternatives

	What it costs	What you get	Trade-off
This actor (jobgether-jobs-lookup)	$1 per 1,000 postings returned, $0.005 actor start, nothing for an empty category	Every current posting in a category — company, location, contract type, remote policy, parsed salary and skills, apply route — as one flat row	Category-keyed. It won't look up a specific company, and it returns what Jobgether currently lists rather than a historical archive.
automation-lab/jobgether-remote-jobs-scraper (14 users)	$0.000083 per item, $0.005 start	Substantially cheaper per posting for the same source	Roughly a twelfth of the per-posting price here. If cost per row is your binding constraint, that's the cheaper tool; this one gives you parsed salary and skills plus the never-charged-for-an-empty-category guarantee.
Jobgether's own site	Free	The same postings, in a browser	Fine for reading. This is for getting a few hundred postings into a table, on a schedule, with salary and skills already parsed.
Doing it yourself	Your time + finding the API, parsing salary bands, de-duplicating skills, retries	The same data	This actor absorbs the parsing and the retries and hands you a flat table.

Competitor prices are their published FREE-tier list prices as of August 2026 and are not tracked here — check the actor's own page before relying on the comparison.

FAQ

Where do I find a category slug? It's the segment after /remote-jobs/ in a Jobgether URL, so jobgether.com/remote-jobs/it-development gives you it-development.

Can I look up a specific company instead? Not with this actor — it's category-keyed. For company-keyed lookups, use one of the ATS actors in this catalogue, or ats-jobs-unified-lookup if you don't know which ATS a company uses.

How am I billed? Per job posting actually returned. A category that comes back empty costs nothing beyond the per-run start fee.

Why is salaryAverage empty on some postings? Because no salary was published. The field is derived from Jobgether's posted band, so a posting without one yields null rather than an estimate.

Does jobCount always equal totalAvailable? No. totalAvailable is what Jobgether reports for the category; jobCount is what this run returned. When they differ you're seeing a subset.

Do I need a proxy? No. The API is public and unauthenticated. proxyConfiguration is exposed if your own network policy requires it.

Can an AI agent call this directly? Yes — it's registered with the Apify MCP server. An agent with that MCP connected can find and run "Jobgether Jobs Lookup" by name and get dataset rows back with no integration code.

Related actors

• Working Nomads Jobs Lookup — the same category-keyed shape for the Working Nomads remote feed.
• ATS Jobs Unified Lookup — company-keyed lookups across Greenhouse, Lever, Ashby, Workable and more.
• Greenhouse Jobs Lookup — every open role on a specific company's Greenhouse board.