# Jobgether Jobs Lookup — Remote Jobs by Category (`accountable_eel/jobgether-jobs-lookup`) Actor

Search Jobgether's remote-jobs categories and get every open posting — title, company, location, remote type, contract type, salary if disclosed, apply link. Charged once per posting returned, never for a category with nothing open.

- **URL**: https://apify.com/accountable\_eel/jobgether-jobs-lookup.md
- **Developed by:** [Adrian Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Jobs, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 1,000 job posting returneds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Jobgether Jobs Lookup — Remote Jobs by Category

Paste one or more [Jobgether](https://jobgether.com) 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:
   ```bash
   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

```json
{
  "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/<slug>. Accepted formats: it-development, customer-service, sales.

```json
{
  "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:

```json
{
  "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:

```json
{
  "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.

```bash
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](https://apify.com/accountable_eel/workingnomads-jobs-lookup) — the
  same category-keyed shape for the Working Nomads remote feed.
- [ATS Jobs Unified Lookup](https://apify.com/accountable_eel/ats-jobs-unified-lookup) —
  company-keyed lookups across Greenhouse, Lever, Ashby, Workable and more.
- [Greenhouse Jobs Lookup](https://apify.com/accountable_eel/greenhouse-jobs-lookup) — every open
  role on a specific company's Greenhouse board.

# Actor input Schema

## `items` (type: `array`):

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/<slug>. Accepted formats: it-development, customer-service, sales. You're only charged for the ones we actually find — a miss costs nothing.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

## `maxResults` (type: `integer`):

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each job posting found gets its own row instead of being grouped under its category search. You're still only charged once per category search, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## `proxyConfiguration` (type: `object`):

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "items": [
    "it-development"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "columns": [
    "category",
    "jobCount",
    "totalAvailable",
    "jobs",
    "title",
    "company",
    "companySlug",
    "location",
    "remoteOfferType",
    "contractType",
    "salaryAverage",
    "skills",
    "postedAt",
    "url",
    "applyUrl",
    "isEasyApply"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "items": [
        "it-development"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/jobgether-jobs-lookup").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "items": ["it-development"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/jobgether-jobs-lookup").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "items": [
    "it-development"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/jobgether-jobs-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/jobgether-jobs-lookup"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/s2593zbW9DFJFwPaD/builds/9IbxMlWB0lnbf8lpS/openapi.json