# Web Developer Jobs Scraper: 12 Boards + Only New Jobs (`nomad-agent/web-dev-bundle`) Actor

$0.2/1K jobs | Web and software developer jobs from 12 boards in one run: LinkedIn, Remote OK, Remotive, Built In, NoFluffJobs, Tecnoempleo, InfoJobs and more, with full descriptions. Default search keeps developer roles. No login or API key.

- **URL**: https://apify.com/nomad-agent/web-dev-bundle.md
- **Developed by:** [Nomad.Devs](https://apify.com/nomad-agent) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 10 total users, 4 monthly users, 87.9% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.10 / 1,000 job results

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Web Developer Jobs Scraper (No Login) + 12 Boards

$0.2/1K jobs | Web and software developer jobs from 12 boards in one run: LinkedIn, Remote OK, Remotive, Built In, NoFluffJobs, Tecnoempleo, InfoJobs and more, with full descriptions. Default search keeps developer roles. No login or API key. Independent, unofficial tool. Not affiliated with or endorsed by the job boards and sites it reads.

### Web Developer Jobs Bulk Scraper

Our scraper collects web and software developer jobs from 12 boards in one run and lets you filter by keyword, location, work arrangement, employment type and posting age. Every row carries the complete original description in text and HTML and the source link. If you pass no `queries`, it searches 20 default developer phrases and keeps a stored posting only when its job title contains one (like "software engineer", "developer", "frontend" or "react"). LinkedIn is searched live and keeps its own ranking. Your own `queries` search both title and description, and an empty list returns every posting. It is ideal for developer job boards, tech-stack demand analytics and freelance or recruiter lead lists.

- Want every kind of job from 21 boards? Use [All Jobs Scraper (No Login) + 21 Boards in One](https://apify.com/nomad-agent/all-jobs-scraper).
- Need one board with its own filters? Use [JustJoin.it Jobs Scraper (No Login) + Full Descriptions](https://apify.com/nomad-agent/justjoinit-scraper), [NoFluffJobs Scraper (No Login) + Full Descriptions](https://apify.com/nomad-agent/nofluffjobs-scraper), [Tecnoempleo Jobs Scraper (No Login) + Full Descriptions](https://apify.com/nomad-agent/tecnoempleo-scraper), [Welcome to the Jungle Jobs Scraper (No Login) + Full Text](https://apify.com/nomad-agent/wttj-scraper) or [Remote Jobs Scraper — RemoteOK, Remotive, WWR, Himalayas](https://apify.com/nomad-agent/remote-boards-scraper). They are narrower than this bundle.
- Need LinkedIn only, searched deeply? Use [LinkedIn Jobs Scraper (No Cookies) + Full Descriptions](https://apify.com/nomad-agent/linkedin-scraper).
- Browse all our job-board scrapers: https://apify.com/nomad-agent

#### Key Benefits

- No login or API key: nothing to set up, no account of yours at risk, and no cookies to hand over.
- Low pricing: **$0.20 per 1,000 jobs** ($0.0002 per job), with lower rates on Scale and Business plans ($0.15 and $0.1 per 1,000), plus $0.00005 per run start.
- Full descriptions only: a posting with a missing or truncated description is never returned.
- Developer roles by default: with no `queries`, a stored posting is kept only when its job title names developer work (`software engineer`, `developer`, `frontend`, `react` and 16 more phrases), and `queries: []` returns every posting.
- Developer-focused mix: remote-first boards, Polish and CEE IT, Spanish IT and French tech boards in one schema.
- No repeats across runs: schedule the same search daily and get only postings you have not received yet.

### How It Works

1. Provide your search. Every filter is optional, and an empty list means no filter:
   - (optional) Search queries (e.g., `react`). A posting matches when its title or description contains every word of a query, as whole words. Leave them out for the built-in developer searches.
   - (optional) Locations (e.g., `Europe`, `DE`, `Berlin`). Countries match by name, code and native name, and `EU` and `Europe` cover their member countries.
   - (optional) Work arrangement (`remote`, `hybrid`, `onsite`) and employment type (`Full-time`, `Part-time`, `Contract`, `Internship`).
   - (optional) Posted within (e.g., `24h`, `7d`, `2w`). Default is `any`.
2. Set how many jobs you want with `maxItems`.
3. Click Start. The form opens with `Europe`, 20 jobs and the 20 built-in developer searches in `queries`; keep them for the default scope, or empty the list to search every posting.

More settings:

- `maxItems` - Maximum number of jobs per run. Default is 200; `0`, or anything above 200, means 200.
- `maxItemsPerSource` - Caps how many postings each board contributes. Default is 50, at most 200. `maxItems` then keeps the newest postings across all boards.
- `dedupe` - On by default: postings already delivered to your Apify account for the same search are skipped. Set `dedupe.enabled` to `false` to get everything again, or set `dedupe.key` to keep separate alert histories.

Run the same search twice and the second run returns only new postings, possibly none. That is the repeat suppression working; turn `dedupe` off to see every posting again.

Coverage: Remote OK, Remotive, We Work Remotely, Built In, JustJoin.it, NoFluffJobs, Hacker News (Who is hiring), Welcome to the Jungle, Tecnoempleo, Y Combinator Work at a Startup and InfoJobs are served from verified postings, and LinkedIn is read live on every run. Each row keeps its own `source`.

LinkedIn can be limited or blocked during a run. When that happens its rows are fewer than requested or missing, the other boards are still returned, `RUN-SUMMARY.unavailableSources` names LinkedIn, and the run is marked `partial`.

When you set work arrangement or employment type, a posting whose source does not state that fact is left out. Salary and hiring contacts are filled only when the source publishes them (in our test run only a small share of rows had either), so treat them as bonus fields.

#### Data You'll Receive

- Job details: title, complete description (text and HTML), locations, posting date, deadline (when published), work arrangement, employment types, salary (when published).
- Employer: company name.
- Links: original posting URL.
- Hiring contacts: the people a source names, when it names any (otherwise an empty list).
- Identity: `source` and a stable `id`, so you can deduplicate across runs.

Rows use the `nomad-agent-job-row-v3` format, newest postings first. Unknown optional facts are `null`.

#### Sample output data

Here is an example job from this Actor (one row of our test run, description shortened):

```json
{
  "schemaVersion": "nomad-agent-job-row-v5",
  "source": "tecnoempleo",
  "id": "b82814cd72e573a29344",
  "url": "https://www.tecnoempleo.com/tech-lead-ingeniero-fullstack-react-digital-talent/typescript-javascript-s/rf-b82814cd72e573a29344",
  "title": "Tech Lead - Ingeniero/a Fullstack React",
  "company": "Digital Talent Agency",
  "locations": [
    "Málaga (Híbrido)"
  ],
  "countryCodes": null,
  "applicantLocations": null,
  "postedAt": "2026-10-13",
  "deadline": null,
  "description": "Zemsania está buscando un/a Tech Lead - Ingeniero/a Fullstack altamente cualificado/a y con una sólida trayectoria para unirse a nuestro equipo en Málaga. Si tienes una pasión por la tecnología, experiencia en el desarrollo fullstack con React, Typescript y Javascript, y buscas un rol desafiante don… [truncated for display]",
  "descriptionHtml": "\r\n\t\t\t\t\t\tZemsania está buscando un/a Tech Lead - Ingeniero/a Fullstack altamente cualificado/a y con una sólida trayectoria para unirse a nuestro equipo en Málaga. Si tienes una pasión por la tecnologí… [truncated for display]",
  "workType": "hybrid",
  "salary": null,
  "employmentTypes": [
    "Full-time"
  ],
  "hiringContacts": []
}
```

### Web Developer Jobs API

Results are stored in a dataset that you can export as CSV, JSON or Excel, or read on demand through the Apify API. A run summary, including any input field that was mapped or ignored, is written to the `RUN-SUMMARY` record of the run's key-value store.

#### Support and Feedback

We improve these scrapers from your feedback. If something breaks or you need a filter:

- Open an issue on the Actor's Issues tab
- If this Actor saved you time, a short review on the Store helps other users find it.

### Run evidence

#### Start with one input and output

An Apify account is required. Use your Apify API token when calling the API; Console runs do not need that token pasted into the input. No user API-key field is required by this input schema.

Free-tier event rates checked 2026-10-04: `result` $0.0002; `actor-start` $0.00005.

**Cost:** Total = Actor event charges + platform usage if separately billed + any BYO-provider charges. See “Current costs” for your event rates, plan tiers and a calculation. A sample does not promise future billable volume.

Input and output below were read from the same successful run `ddmqveSEcloy4w62a` (2026-10-03, immutable build `yZ4MbtQ2hIlqEd5AF`). This is an observed example, not a guarantee that repeating it returns this row.

**Input JSON**

```json
{
  "dedupe": {
    "enabled": false,
    "key": ""
  },
  "maxItems": 3,
  "queries": [],
  "locations": [],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "any",
  "maxItemsPerSource": 50,
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}
```

**Matching output excerpt**

Long strings and arrays are shortened for display; this is not a complete dataset fixture.

```json
{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "infojobs",
  "id": "8a57161d174eac8707428ed823ebae",
  "url": "https://www.infojobs.net/mostoles/asesor-inmobiliario-best-house/of-i8a57161d174eac8707428ed823ebae",
  "title": "Asesor/a Inmobiliario/a BEST HOUSE",
  "company": "Best House Corner",
  "locations": [
    "Móstoles"
  ],
  "postedAt": "2026-10-03T19:00:00Z",
  "deadline": null,
  "description": "BEST HOUSE, Mejores condiciones del sector. 20 años de experiencia, proyecto de ámbito nacional con +500 inmuebles de segunda mano y +50 promociones de Obra Nueva. ¿Tienes varios años de experiencia y deseas aumentar cartera y cerrar más operaciones al año? Sesión Incorporación Onboarding intensiva, para Asesores en activo con Experiencia previa ¿No tienes e… [truncated for display]",
  "descriptionHtml": "BEST HOUSE, Mejores condiciones del sector. 20 años de experiencia, proyecto de ámbito nacional con +500 inmuebles de segunda mano y +50 promociones de Obra Nueva.\n¿Tienes varios años de experiencia y deseas aumentar cartera y cerrar más operaciones al año? Sesión Incorporación Onboarding intensiva, para Asesores en activo con Experiencia previa \n¿No tienes … [truncated for display]",
  "workType": "remote",
  "salary": "36.000 € - 70.000 € Bruto/año",
  "employmentTypes": [
    "Contract"
  ],
  "hiringContacts": []
}
```

Recent web and software developer jobs with complete original descriptions. Each row carries the source ID and URL, title, employer, locations, the original description as text and HTML, posting date, deadline, work arrangement, employment type, salary and the hiring contacts the source names, whenever the source publishes them. Unknown optional facts are `null`; an empty `locations` array means the source names no physical place, and an empty `hiringContacts` array means the source names nobody. `locations` is where the job is, `countryCodes` lists the countries of those places as ISO 3166-1 two-letter codes (`null` when no place has a known country), and `applicantLocations` is where an applicant may live, for example a remote job open only to residents of some countries: it is `null` when the source states nothing and `[]` when it states no restriction. `workType` is set only when the source names exactly one arrangement and is `null` when it names several, such as remote or hybrid; `locationTypes` matches a posting when any arrangement it names is selected.

Coverage includes these public job sources: Remote OK, Remotive and We Work Remotely; Built In; JustJoin.it; NoFluffJobs; Hacker News Who is hiring; Welcome to the Jungle; Tecnoempleo; Y Combinator's Work at a Startup; InfoJobs. LinkedIn is also served, fetched live on every run. Each row keeps its own `source`. Every posting is verified before it is served. A posting with a missing, truncated or unverified description is never returned: every row has the full original text. LinkedIn results use the requested search filters. Each posting still has its full description or it is left out. LinkedIn may limit or block a run, so its rows can be fewer than requested or missing: the other boards are still returned, `RUN-SUMMARY.unavailableSources` names LinkedIn, and the run is marked `partial`.

Without `queries` (or the older `keyword`), runs mostly return web and software developer roles: the default `queries` are listed under Input, and a stored posting is kept only when its job title contains one of them. An empty `queries` list (`queries: []`) returns every posting. LinkedIn is searched live and keeps its own ranking.

LinkedIn is searched live for at most 6 combinations of query, location and work arrangement per run. With the default `queries` it searches a curated subset of them, `software engineer`, `developer`, `frontend`, `backend`, `full stack` and `react`, while the stored boards use all of them. Naming several `locations` or `locationTypes` shares the six searches, so each location gets fewer of those phrases: two locations get the first three each, three get the first two, and four to six get the first phrase only. With your own `queries`, or more than six locations and work arrangements together, combinations beyond the sixth are not searched: the last locations you list can get no LinkedIn rows, the run is marked `partial`, and `RUN-SUMMARY.unavailableSources` says how many combinations were searched.

#### Input

```json
{"schemaVersion": "nomad-agent-simple-inventory-search-v2", "queries": ["software engineer", "developer", "développeur", "desarrollador", "programador", "programmer", "frontend", "front end", "backend", "back end", "full stack", "fullstack", "devops", "react", "javascript", "typescript", "python", "php", "java", "sre"], "locations": ["Europe"], "locationTypes": ["remote"], "employmentTypes": [], "postedWithin": "7d", "maxItems": 200, "maxItemsPerSource": 50, "dedupe": {"enabled": true, "key": ""}}
```

Every filter is optional, and an empty list means no filter. Filters are applied to all available postings before `maxItems` is counted.

- `queries`: a posting matches a query when its title or description contains every word of it, as whole words, ignoring case. A posting matches when any query matches. **Default:** a run that sets neither `queries` nor the older `keyword` searches for web and software developer roles with these queries: `software engineer`, `developer`, `développeur`, `desarrollador`, `programador`, `programmer`, `frontend`, `front end`, `backend`, `back end`, `full stack`, `fullstack`, `devops`, `react`, `javascript`, `typescript`, `python`, `php`, `java`, `sre`. On the stored boards it also keeps only postings whose job title contains one of them. Your own `queries` or `keyword` replace them and are matched in the title and the description, and an empty list means no query filter.
- `locations`: a city, region, country name or two-letter ISO country code. Countries match by name, code and native name (`Germany`, `DE` and `Deutschland` find the same postings), and `EU` and `Europe` cover their member countries.
- `locationTypes` (`remote`, `hybrid`, `onsite`) and `employmentTypes` (`Full-time`, `Part-time`, `Contract`, `Internship`): while one is set, a posting whose source does not state that fact is left out.
- `postedWithin`: a positive duration in hours (`h`), days (`d`), weeks (`w`) or 30-day months (`m`), up to 36500 days, or `any`. Postings without a source date use the date they were first seen, which later refreshes never reset.
- `maxItems` defaults to 200; 0, or anything above 200, means 200.
- `maxItemsPerSource` (default 50, at most 200) caps how many postings each source contributes; `maxItems` then keeps the newest postings across all sources.
- `dedupe` suppresses postings already delivered to the same Apify account for the same search; different filters keep separate histories. Set `dedupe.enabled` to `false` to get stateless results, or set `dedupe.key` to keep separate alert histories.

#### Output

One flat row per posting in the `nomad-agent-job-row-v5` format: `schemaVersion`, `source`, `id`, `url`, `title`, `company`, `locations`, `countryCodes`, `applicantLocations`, `postedAt`, `deadline`, `description`, `descriptionHtml`, `workType`, `salary`, `employmentTypes`, `hiringContacts`. `employmentTypes` lists the types the source states (`Full-time`, `Part-time`, `Contract`, `Internship`) or is `null`. `countryCodes` lists the countries of the job's places as ISO 3166-1 alpha-2 codes (for example `DE`, `FR`), in the same order as `locations`, each once. A code comes from the source if it states one, otherwise from the place label. It's `null` when no place has a known country (a remote job with no country, or an unidentifiable place) and never an empty list. A place without a known country adds nothing, so the list can name fewer countries than there are places. A posting stored on a single-country board with no place at all carries that board's country, so `locations` can be `[]` while `countryCodes` names one. Postings read live from LinkedIn's public pages always have `countryCodes: null`. Those pages give a place label but no country code, so only stored postings carry a code. The `locations` filter matches countries against these codes as well as names and text. `applicantLocations` lists the regions where the source says an applicant may live (for example `United States` for a remote job open to US residents), `null` when it states nothing and `[]` when it states no restriction. Each hiring contact has a `name`, and a `title` and `url` or `null`. Newest postings come first. A run summary, including any input field that was mapped or ignored, is written to the `RUN-SUMMARY` record of the run's key-value store.

#### Changes

- **November 2026: the default search keeps web and software developer roles.** Previously a run with no search matched every posting on every board. Now it searches 20 built-in phrases, listed under Input, and keeps a stored posting only when its job title contains one of them. Your own `queries` still match both title and description, an empty `queries` list (`queries: []`) still returns every posting, and LinkedIn is searched live for six of them. The built-in phrases are part of the repeat-delivery scope, so the first run without `queries` after this change can return postings you already received.
- **October 2026: `countryCodes` added (row v5).** Rows are now `nomad-agent-job-row-v5`: one new field, `countryCodes`, lists the ISO 3166-1 alpha-2 country codes of the job's places, in the order of `locations`, each once (`null` when no place has a known country, never an empty list). A code is the country the source states, or if it doesn't state one, the country read from the place label. A place whose country can't be determined adds nothing. Postings read live from LinkedIn carry `null`; its public pages show a place label but no country code. `locations` and `applicantLocations` are unchanged. Input, other fields, and pricing are unchanged. Integrations validating against the v4 schema must allow the new field and the new `schemaVersion`.
- **October 2026: `applicantLocations` added (row v4).** Rows are now `nomad-agent-job-row-v4`: one new field, `applicantLocations`, lists where an applicant may live as the source states it (`null` when the source states nothing, `[]` when it states no restriction). `locations` is unchanged and still the physical place only; for a remote job open to some regions it is often `[]` while `applicantLocations` lists the regions. Input, other fields and pricing are unchanged. Integrations that validate rows against the v3 schema must allow the new field and the new `schemaVersion`.
- **October 2026: LinkedIn is read live.** LinkedIn results reflect its current public job pages. Every row still has the complete description or is left out, and the other boards are unchanged. A LinkedIn failure no longer affects the other boards: the run is marked `partial` and `RUN-SUMMARY.unavailableSources` names it. Pricing is unchanged.
- **October 2026: `recordType` removed.** `nomad-agent-job-row-v3` rows no longer include the `recordType` field, because every dataset row is a posting. Read `schemaVersion` instead. The `RUN-SUMMARY` record is unchanged.
- **September 2026: search filters and richer rows.** The input (`nomad-agent-simple-inventory-search-v2`) adds `queries`, `locations`, `locationTypes` and `employmentTypes`, and `maxItemsPerSource` (default 50). Rows are now `nomad-agent-job-row-v3` and add `employmentTypes` and `hiringContacts`. Integrations that still send `keyword` or `location` keep working: those values become `queries` and `locations`, `remote: true` becomes `locationTypes: ["remote"]`, and other old fields are ignored with a note in `RUN-SUMMARY` instead of failing the run. Pricing is unchanged.
- **Earlier:** this Actor moved to verified available postings in the shared simple job format, and every row includes the complete description.

#### Fast setup and source code

[Public repository](https://github.com/Exdenta/nomad-agent-job-scrapers) · [Agent setup skill](https://github.com/Exdenta/OinkAIJobSearch/blob/main/.agents/skills/public-apify-actors/SKILL.md).

Use the Actor’s current input form for filters, or start with its documented API example. Select the `latest` build. Read the dataset together with the run summary: a successful status alone does not show that every source was reached.

Restrictive filters or repeat-delivery suppression can produce zero results.

##### Observed output example

Selected fields from a real source record inspected on 2026-10-03; consult the output schema for the full contract. Values change with the source.

```json
{
  "schemaVersion": "nomad-agent-job-row-v3",
  "source": "builtin",
  "id": "11432024",
  "url": "https://builtin.com/job/senior-frontend-react-engineer/11432024",
  "title": "Senior Frontend React Engineer",
  "company": "Modern Family Law",
  "locations": [
    "USA"
  ],
  "postedAt": "2026-09-30",
  "deadline": null,
  "workType": null,
  "salary": null,
  "employmentTypes": null,
  "hiringContacts": []
}
```

#### Product guides and related tools

- [Guide and starter input on nomadagent.dev](https://nomadagent.dev/actors/web-dev-bundle)
- [Product overview and public links](https://jobatlas.dev/actors/directory/source-jobs#nomad-agent-web-dev-bundle)
- [Public setup guide](https://github.com/Exdenta/jobatlas/blob/main/docs/public-actors-setup.md)
- [Job Atlas job-data tools](https://jobatlas.dev/actors)
- [Oink personal job alerts](https://oinkjobsearch.com/)
- [Search ten job boards with one API call](https://oinkjobsearch.com/articles/search-ten-job-boards-with-one-api-call/)

#### Current costs

Current Actor event rates, checked 2026-10-16. USD; use the **Pricing** tab for your plan and later changes.

| Event | Free | Bronze | Silver | Gold | Platinum | Diamond |
|---|---:|---:|---:|---:|---:|---:|
| Job result (`result`) | $0.0002 | $0.0002 | $0.00015 | $0.0001 | $0.0001 | $0.0001 |
| Actor start (`actor-start`) | $0.00005 | $0.00005 | $0.00005 | $0.00005 | $0.00005 | $0.00005 |

For example, 100 × `result`, 1 × `actor-start` totals **$0.02005 in Actor event charges on Free**. This is an arithmetic example, before any waiver; actual charged events depend on the run and selected options. It is not a promise of output or a charge for simply setting an item cap.

Your total is the charged Actor events, plus platform usage **only if this Actor’s Pricing tab bills it separately**, plus any external provider you use with your own key. Do not add platform usage twice when it is included. Apify credits and plan discounts affect your invoice. Set a run cost limit in Console before starting.

***

**Independent tool.** We built and run this Actor ourselves. The job boards and sites it reads do not operate, sponsor or endorse it, and their names are used only to say where the data comes from.

# Actor input Schema

## `queries` (type: `array`):

Match postings whose title or description contains every word of a query, as whole words, ignoring case. A posting matches when any query matches. Words match as the posting wrote them, so where postings are not in English, add the local term as a further query. Empty: no filter. Default: queries that find web and software developer roles; replace them with your own, or clear the list to search every posting. With the defaults, a stored posting also needs one of those terms in its job title. Your custom queries match against both title and description.

## `locations` (type: `array`):

City, region, country name or two-letter ISO country code. Countries match by name, code or native name; EU and Europe expand to their countries. A posting also matches when the source names the place as somewhere an applicant may live (`applicantLocations`). Empty: no filter.

## `locationTypes` (type: `array`):

remote, hybrid or onsite. A posting matches when any arrangement it names is selected; `workType` in the row is set only when the source names exactly one. Postings whose arrangement the source does not state are left out. Empty: no filter.

## `employmentTypes` (type: `array`):

Full-time, Part-time, Contract or Internship. Postings whose type the source does not state are left out. Empty: no filter.

## `postedWithin` (type: `string`):

Positive duration in hours, days, weeks, or 30-day months, at most 36500 days; any disables the filter. Uses the first inventory admission date when the source has no posting date.

## `maxItems` (type: `integer`):

Maximum returned jobs. Zero, or anything above 200, means 200.

## `maxItemsPerSource` (type: `integer`):

Most postings any one source contributes, at most 200. maxItems then keeps the newest postings across sources.

## `dedupe` (type: `object`):

Suppress confirmed repeat deliveries for the same Apify user and search.

## `schemaVersion` (type: `string`):

Version marker for database-only simple job search. Version 1 inputs remain valid.

## Actor input object example

```json
{
  "queries": [
    "software engineer",
    "developer",
    "développeur",
    "desarrollador",
    "programador",
    "programmer",
    "frontend",
    "front end",
    "backend",
    "back end",
    "full stack",
    "fullstack",
    "devops",
    "react",
    "javascript",
    "typescript",
    "python",
    "php",
    "java",
    "sre"
  ],
  "locations": [
    "Europe"
  ],
  "locationTypes": [],
  "employmentTypes": [],
  "postedWithin": "any",
  "maxItems": 20,
  "maxItemsPerSource": 5,
  "dedupe": {
    "enabled": true,
    "key": ""
  },
  "schemaVersion": "nomad-agent-simple-inventory-search-v2"
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `runSummary` (type: `string`):

One record describing this run: what was attempted, what was delivered, and anything that degraded. Written to the run's key-value store under RUN-SUMMARY.

# 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 = {
    "locations": [
        "Europe"
    ],
    "postedWithin": "any",
    "maxItems": 20,
    "maxItemsPerSource": 5,
    "dedupe": {
        "enabled": true,
        "key": ""
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("nomad-agent/web-dev-bundle").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 = {
    "locations": ["Europe"],
    "postedWithin": "any",
    "maxItems": 20,
    "maxItemsPerSource": 5,
    "dedupe": {
        "enabled": True,
        "key": "",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("nomad-agent/web-dev-bundle").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 '{
  "locations": [
    "Europe"
  ],
  "postedWithin": "any",
  "maxItems": 20,
  "maxItemsPerSource": 5,
  "dedupe": {
    "enabled": true,
    "key": ""
  }
}' |
apify call nomad-agent/web-dev-bundle --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nomad-agent/web-dev-bundle"
        }
    }
}
```

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/m6h2Dtyzxd2C0biiP/builds/UDKvD4BSN6hGBbl0r/openapi.json