# Remote Jobs Scraper — RemoteOK, WWR & Himalayas API | $0.50/1k (`glasswing/remote-jobs-scraper`) Actor

Scrape remote jobs from Remote OK, We Work Remotely, Himalayas, Jobicy, Working Nomads and Arbeitnow public feeds in one run, merged across boards. Filter by keyword, category, location, job type, salary and date. Company, salary, tags, description, link back. CSV, JSON, Excel.

- **URL**: https://apify.com/glasswing/remote-jobs-scraper.md
- **Developed by:** [Raffy](https://apify.com/glasswing) (community)
- **Categories:** Jobs, Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

### What does Remote Jobs Scraper do?

Remote Jobs Scraper collects **remote job listings from seven remote job boards in one run** and delivers them as one clean dataset (JSON, CSV or Excel): [Remote OK](https://remoteok.com/), [We Work Remotely](https://weworkremotely.com/), [Himalayas](https://himalayas.app/), [Jobicy](https://jobicy.com/), [Working Nomads](https://www.workingnomads.com/), [Arbeitnow](https://www.arbeitnow.com/) (remote jobs only) and, if you pick it, [Remotive](https://remotive.com/). Every row has the same fields whatever board it came from: title, company, where applicants may live, job type, seniority, categories and tags, salary when the board publishes one, posting date, plain-text description, and the link back to the listing on the board.

It works as a **remote jobs API**: the data comes from the **public feeds and APIs these boards publish for reuse** (the Remote OK API, the We Work Remotely RSS feeds, the Himalayas, Jobicy, Arbeitnow, Working Nomads and Remotive job APIs). No account, no login, no API key, no browser and no proxy. The same job posted on several boards is **merged into one row**, and the `sources` column tells you every board it is on.

**Try it:** leave the input as it is and click **Start**. You get the 50 newest remote jobs, balanced across the boards, in about 10 seconds. Raise **Maximum jobs** to 2,000 for a full sweep of more than 1,000 unique jobs.

### Use cases for this remote job scraper

- **Remote job boards and newsletters:** fill your board, Slack channel or weekly email with fresh remote jobs from seven sources, deduplicated, with the attribution link each board asks for.
- **Job seekers and career coaches:** one filtered list for "python, Europe, posted this week, $100k+" instead of seven browser tabs.
- **Recruiting and sales teams:** see which companies are hiring remotely right now, in which roles and at what published salary.
- **Market research:** count remote jobs by category, region, job type and salary band across boards, week after week.
- **AI agents and automations:** a scheduled run with `postedWithinDays: 1` is a clean "new remote jobs today" feed; every row carries `status` and `error`.

### What data you get from every remote job

| Field | Type | Description |
|---|---|---|
| `jobId` | string | Stable id `<board>:<id on that board>`, e.g. `remoteok:1137434` |
| `title` | string | Job title as the board publishes it |
| `companyName` | string | Hiring company |
| `source` | string | Board the row comes from: `remoteok`, `weworkremotely`, `himalayas`, `jobicy`, `workingnomads`, `arbeitnow`, `remotive` |
| `sourceName` | string | The board's name to credit, e.g. "Remote OK", "We Work Remotely" |
| `sourceUrl` | string | The listing on the board. Link back to it when you show the job |
| `applyUrl` | string | Where to apply, as the board publishes it (usually its own listing or apply link) |
| `sources` | array | Every board this job was found on (`source` first) |
| `sourceUrls` | array | Every listing of this job: one per board, plus reposts and per-country copies on one board |
| `companyUrl` | string | Employer website, when the board publishes it |
| `companyLogo` | string | Company logo image URL |
| `remote` | boolean | Always `true` |
| `location` | string | Location text as published, e.g. "USA Only", "Europe, USA", "Worldwide" |
| `locationRestrictions` | array | Countries or regions applicants must be in |
| `timezoneRestrictions` | array | Accepted UTC offsets (Himalayas), e.g. `[-8, -7, -6, -5]` |
| `isWorldwide` | boolean | `true` when the board says anyone, anywhere may apply |
| `jobType` | string | `full_time`, `part_time`, `contract`, `freelance`, `internship` or `temporary` |
| `seniority` | string | Seniority as published, e.g. "Senior", "Mid-level" |
| `categories` | array | Board categories, e.g. "Software Development", "Design" |
| `tags` | array | Skill and topic tags |
| `salaryMin`, `salaryMax` | number | Salary range, only when the board publishes one (never estimated) |
| `salaryCurrency` | string | ISO code, e.g. `USD`, `EUR` |
| `salaryPeriod` | string | `year`, `month`, `week`, `day` or `hour` |
| `salaryText` | string | Salary as published when it came as text (Remotive), e.g. "$90k - $105k" |
| `postedAt` | string | ISO 8601 time the job was posted |
| `expiresAt` | string | ISO 8601 time the listing expires, when stated |
| `descriptionText` | string | Full description as plain text; e-mail addresses and phone numbers removed |
| `descriptionHtml` | string | Description as HTML, only with `includeDescriptionHtml` |
| `matchedKeywords` | array | Which of your `keywords` the job matched (only when keywords are given) |
| `matchedCategories` | array | Which of your `categories` the job matched (only when categories are given) |
| `status` | string | `ok`, `not_found` or `error` (see below) |
| `error` | string | Reason when `status` is not `ok` |
| `scrapedAt` | string | ISO 8601 time the feed was read |

Optional fields are left out when a board does not publish them. Measured on a 1,077-job run (2026-09-28): every row has a title, company, board link, posting date and description; 85% have a job type, 74% a location restriction and 92% a worldwide flag, and 30% a published salary.

#### Result status (tri-state output)

| `status` | Meaning | Billed? |
|---|---|---|
| `ok` | A remote job. | Yes |
| `not_found` | A board answered, but none of its current jobs matched your filters. One row per board says how many jobs were read. | No |
| `error` | A board could not be read after retries (it was down or refused the request). The row names the board; the other boards are still collected. | No |

A run whose filters match nothing ends **successfully** with its free `not_found` rows, so a narrow scheduled search that is empty today is not a failed run.

### How to scrape remote jobs with this Actor

1. Open the Actor in Apify Console and click **Try for free**.
2. Pick the **Job boards** to read (all but Remotive are on by default).
3. Optionally narrow the results: **Keywords** (`python`, `react native`), **Categories or tags** (`design`, `devops`), **Where applicants may live** (`US`, `Europe`, `Germany`, `anywhere`), **Job types**, **Minimum yearly salary**, **Posted within the last N days**.
4. Set **Maximum jobs** and click **Start**. Rows appear in the **Output** tab; export them as JSON, CSV, Excel, XML or HTML.

### Input

Everything is optional. The default input reads every board except Remotive and returns the newest jobs, balanced across boards. Example: Python or Go jobs open to people in Europe, posted in the last 7 days, paying at least 90,000 a year:

```json
{
    "keywords": ["python", "golang"],
    "locations": ["Europe"],
    "postedWithinDays": 7,
    "minSalary": 90000,
    "maxItems": 200
}
```

| Field | What it does |
|---|---|
| `sources` | Boards to read: `remoteok`, `weworkremotely`, `himalayas`, `jobicy`, `workingnomads`, `arbeitnow`, `remotive`. Default: all but `remotive`. |
| `keywords` | Keep jobs mentioning any of these words or phrases in title, tags, categories, company or description (whole words). |
| `categories` | Keep jobs whose board category or tags match any of these. |
| `locations` | Keep jobs open to applicants in any of these places. A European country also matches jobs limited to Europe/EU/EMEA; `anywhere` keeps only worldwide jobs. |
| `includeWorldwide` | With `locations` set, also keep worldwide jobs (default `true`). |
| `jobTypes` | `full_time`, `part_time`, `contract`, `freelance`, `internship`, `temporary`. |
| `minSalary`, `includeJobsWithoutSalary` | Yearly salary floor over published salaries (hourly, weekly and monthly pay is converted; no currency conversion). |
| `postedWithinDays` | Only jobs posted in the last N days. |
| `maxItems` | Maximum rows (default 100; 50 in the Console form). |
| `maxItemsPerSource` | Optional cap per board. |
| `dedupe` | Merge the same job across boards (default `true`). |
| `order` | `balanced` (boards take turns, newest first within each) or `newest` (one list by date). |
| `includeDescriptionHtml` | Also save the description as HTML. |
| `startUrls` | Advanced: read only these public feed URLs, e.g. a We Work Remotely category feed or `https://jobicy.com/api/v2/remote-jobs?geo=usa&industry=marketing`. |

### Output

A real row from a platform run on 2026-09-28 (description and categories shortened). This job was on Himalayas and Arbeitnow, so it is one row with both boards in `sources`:

```json
{
    "url": "https://himalayas.app/companies/paddy/jobs/ai-product-engineer",
    "status": "ok",
    "jobId": "himalayas:paddy/ai-product-engineer",
    "title": "AI Product Engineer",
    "companyName": "Paddy",
    "source": "himalayas",
    "sourceName": "Himalayas",
    "sourceUrl": "https://himalayas.app/companies/paddy/jobs/ai-product-engineer",
    "applyUrl": "https://himalayas.app/companies/paddy/jobs/ai-product-engineer",
    "sources": ["himalayas", "arbeitnow"],
    "sourceUrls": [
        "https://himalayas.app/companies/paddy/jobs/ai-product-engineer",
        "https://www.arbeitnow.com/jobs/companies/paddy/ai-product-engineer-bielefeld-8892"
    ],
    "companyLogo": "https://cdn-images.himalayas.app/4damiw2wrr34drmiv7udmudnpyv6",
    "remote": true,
    "location": "Germany",
    "locationRestrictions": ["Germany"],
    "timezoneRestrictions": [1],
    "isWorldwide": false,
    "jobType": "full_time",
    "seniority": "Mid-level",
    "categories": ["Data Science", "Developer", "AI Engineer", "Product Engineer"],
    "salaryMin": 70000,
    "salaryMax": 100000,
    "salaryCurrency": "EUR",
    "salaryPeriod": "year",
    "postedAt": "2026-09-28T03:45:54.000Z",
    "expiresAt": "2026-11-27T03:45:53.000Z",
    "descriptionText": "Das ist kein gewöhnlicher Job. Wir arbeiten an dem, was unsere Gesellschaft zukunftsfähig macht: Bildung. Dafür bauen wir paddy, das Agentic Operating System für Teaching & Learning. ...",
    "scrapedAt": "2026-09-28T19:19:31.548Z",
    "tags": ["Software Development"]
}
```

A board that is down adds one free row such as `{"status": "error", "source": "jobicy", "error": "Jobicy could not be read: HTTP 503 after 3 attempts. The other boards were still collected; run again later for this board."}` at the top, and the jobs from the other boards follow.

### How much does it cost to scrape remote jobs?

This Actor uses **pay-per-event** pricing. Platform usage (compute, storage, data transfer) is included in these prices:

| Event | Price | Charged when |
|---|---|---|
| Actor start | $0.005 per run | Once when the run starts (one event per GB of memory; the Actor runs on 1 GB). |
| Result | $0.0005 per job | One job with `status: ok` was saved to the dataset. |

**1,000 remote jobs cost about $0.51** ($0.005 to start plus 1,000 x $0.0005). A job found on several boards is one row and is billed once. Rows with `status` `not_found` or `error` are never billed, and jobs your filters leave out are never saved or billed. You can cap spending per run with **Maximum jobs** and with the run's **Max total charge** option; the Actor stops gracefully at either limit.

### Speed and reliability (real cloud runs)

| Run | Jobs | Run time | Board requests |
|---|---|---|---|
| Full sweep (`maxItems: 2000`), 2026-09-28 | 2,000 jobs (the cap; 2,678 read) | 17 s | 121 of 121 succeeded |
| 6 repeated sweeps (25 Himalayas pages each), 2026-09-28 | 1,077-1,165 unique jobs per run | 7-10 s | 271 of 271 succeeded |
| Default input (`maxItems: 50`) | 50 jobs | about 10 s | every board on the first try |

All boards are read in parallel from Apify's regular datacenter servers; each request is retried up to 3 times. If a board is down, its `error` row says so and the run still delivers the other boards.

### Sources and attribution

The data comes from the public feeds these boards publish for developers and partners. Each board asks for credit, so every row carries `sourceName` and `sourceUrl`: **when you publish or display these jobs, link each one back to its `sourceUrl` and name the board.**

| Board | Feed used | What the board asks |
|---|---|---|
| [Remote OK](https://remoteok.com/) | `remoteok.com/api` (about 100 newest jobs) | Link back to the job on Remote OK (followed link) and mention Remote OK as the source. Do not use its logo. |
| [We Work Remotely](https://weworkremotely.com/remote-job-rss-feed) | Main RSS feed and its 11 category feeds (about 270 jobs) | Attribute the links back to We Work Remotely. |
| [Himalayas](https://himalayas.app/docs/remote-jobs-api) | `himalayas.app/jobs/api` (20 jobs per page; up to 2,000 per run) | Visible link back to himalayas.app and mention Himalayas as the source. Data refreshes daily. |
| [Jobicy](https://jobicy.com/jobs-rss-feed) | `jobicy.com/api/v2/remote-jobs` (200 newest jobs) | Credit Jobicy with a direct link; application buttons go to the Jobicy listing. Poll at most hourly. |
| [Working Nomads](https://www.workingnomads.com/) | `workingnomads.com/api/exposed_jobs/` (about 50 newest jobs) | Credit and link back to the listing. |
| [Arbeitnow](https://www.arbeitnow.com/blog/job-board-api) | `arbeitnow.com/api/job-board-api` (only jobs flagged remote are kept) | Link back to Arbeitnow.com; do not abuse the free API. |
| [Remotive](https://github.com/remotive-com/remote-jobs-api) (opt-in) | `remotive.com/api/remote-jobs` (a few dozen jobs, 24 hours delayed) | Link back to the Remotive URL and mention Remotive; at most 4 calls a day; do not submit its jobs to Jooble, Neuvoo, Google Jobs or LinkedIn Jobs. |

### Integrations, exports and API access

Results export to **CSV, JSON, Excel**, XML and HTML from the **Output** tab or the dataset API. Apify integrations and webhooks push the same rows into **Google Sheets, Airtable, Notion or a CRM**, Slack, Amazon S3 or your own endpoint, directly or through Zapier, Make and n8n. Call the Actor from the **Apify API** (snippets on the **API** tab), from the **Apify MCP server** or from any AI agent: every input is optional, and every row carries `status` and `error`.

### Tips

- Schedule it daily with `postedWithinDays: 1` for a feed of new remote jobs. Jobicy asks integrations not to poll more than once an hour, and the boards update a few times a day, so there is no gain in running more often.
- Use `order: "newest"` when you want the freshest jobs first regardless of board, and `maxItemsPerSource` to stop one board from dominating.
- Keywords are matched on whole words, so `go` does not match "good"; use `golang` for the language.
- Paste a filtered feed into **Feed URLs** when a board's own filter is exactly what you need, e.g. `https://jobicy.com/api/v2/remote-jobs?geo=canada&industry=marketing`.

### Limitations

- **Each board exposes only its current public feed.** Remote OK's API lists its ~100 newest jobs, We Work Remotely's feeds ~270, Jobicy's 200, Working Nomads' ~50, Remotive's a few dozen (24 hours delayed). Himalayas pages deeper (up to 2,000 jobs per run). There is no history of closed jobs.
- **Filters run inside the Actor** on what the feeds return, so a narrow keyword finds the matching jobs among the current listings, not an archive search.
- **Dedupe is by company and title.** The same job with a clearly different title on two boards stays two rows; openings with the same title at the same company within 7 days become one row (per-country copies of one job add up in `locationRestrictions`; every listing stays in `sourceUrls`). Set `dedupe: false` to keep every listing as its own row.
- **Salaries are only what boards publish** (about 30% of jobs). No estimates and no currency conversion.
- **Location data varies by board.** Himalayas and Jobicy state eligible countries; Remote OK and Arbeitnow often give an office city; some jobs state nothing.
- **Descriptions are the employer's own text.** E-mail addresses and phone numbers are removed, but a description may still mention a person by name.

### FAQ

**Is this a Remote OK, We Work Remotely or Himalayas product?** No. It is an independent tool that reads the public feeds these boards publish for reuse. It is not affiliated with, endorsed by or sponsored by any of them.

**How many jobs can I get?** A run with `maxItems: 2000` returned 2,000 remote jobs in 17 seconds on 2026-09-28. The fixed-size feeds (Remote OK, We Work Remotely, Jobicy, Working Nomads, Arbeitnow) add up to about 680 jobs; Himalayas pages deeper and supplies the rest, up to 2,000 per run.

**Why is Remotive off by default?** Remotive asks API users to call it at most 4 times a day, shows only a few dozen jobs and delays them by 24 hours. Pick it in **Job boards** when you need it and schedule accordingly.

**What happens when a board is down?** You get one free `error` row naming the board and the jobs from every other board. The run only fails when no board could be read at all.

**Do I need a proxy?** No. The boards publish these feeds for reuse and answer Apify's regular servers.

**Can I get recruiter names or e-mail addresses?** No. The feeds do not publish them, and contact details inside descriptions are removed.

### Legal and data-protection notice

This Actor reads only public job feeds that the boards publish for reuse; it does not log in, does not work around access controls and does not extract private user data such as member profiles, recruiter names, e-mail addresses or phone numbers (e-mail addresses and phone numbers found in free-text job descriptions are removed before a row is saved). However, your results could still contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you are unsure whether your reason is legitimate, consult your lawyers. You are responsible for following each board's terms, including its attribution requirements listed above, and applicable law when you use or republish the data.

This Actor is an independent tool and is not affiliated with, endorsed by or sponsored by Remote OK, We Work Remotely, Himalayas, Jobicy, Working Nomads, Arbeitnow or Remotive. All trademarks belong to their respective owners.

# Changelog

This Actor's version history is a separate document: https://apify.com/glasswing/remote-jobs-scraper/changelog.md

# Actor input Schema

## `sources` (type: `array`):

Boards to read. Default: every board except Remotive. Remotive asks API users to call it at most 4 times a day and shows only a few dozen jobs with a 24-hour delay, so pick it only when you need it.

## `keywords` (type: `array`):

Keep jobs that mention any of these words or phrases in the title, tags, categories, company name or description (whole words, case-insensitive; every word of a phrase must appear). Examples: python, react native, customer support. Leave empty for all jobs.

## `categories` (type: `array`):

Keep jobs whose board category or tags match any of these, e.g. design, devops, marketing, customer support, data. Leave empty for all.

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

Keep jobs open to applicants in any of these places, e.g. US, Europe, Germany, UK, Canada, LATAM, APAC. A European country also matches jobs limited to Europe/EU/EMEA. Use "anywhere" to keep only jobs open worldwide. Leave empty for all.

## `includeWorldwide` (type: `boolean`):

With a location set, also keep jobs the board marks as open to anyone, anywhere.

## `jobTypes` (type: `array`):

Keep only these employment types. Jobs whose board does not state a type are left out when this is set.

## `minSalary` (type: `integer`):

Keep jobs whose published salary reaches this much per year (hourly, weekly and monthly pay is converted to a year; no currency conversion). Jobs without a published salary are left out unless the next option is on.

## `includeJobsWithoutSalary` (type: `boolean`):

With a minimum salary set, also keep jobs that publish no salary at all.

## `postedWithinDays` (type: `integer`):

Keep only jobs posted in the last N days. Leave empty for every job the boards currently list.

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

Stop after this many rows. Each saved job (status `ok`) is one billable result. The boards together list well over 1,000 current remote jobs; raise this to 2,000 for a full sweep.

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

Optional cap on how many jobs one board may contribute. Himalayas can supply up to 2,000 on its own when this is high.

## `dedupe` (type: `boolean`):

One row per job when the same company posts the same title within 7 days, on several boards or several times on one board (reposts, one listing per country). `sources` lists every board, `sourceUrls` every listing.

## `order` (type: `string`):

Balanced: newest first within each board, boards taking turns, so one big board cannot fill the whole dataset. Newest: one list, newest posting first.

## `includeDescriptionHtml` (type: `boolean`):

Also save the description as HTML. The plain-text description is always included.

## `startUrls` (type: `array`):

Read only these public feeds instead of the boards above, e.g. a We Work Remotely category feed or page, https://jobicy.com/api/v2/remote-jobs?geo=usa\&industry=marketing, https://himalayas.app/jobs/api?limit=20 or https://remoteok.com/api. While this field holds exactly the pre-filled example, it is ignored and the boards above are read.

## `query` (type: `string`):

Same as one entry in Keywords; kept for callers that send a single `query`.

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

Alias of `maxItems` for API callers.

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

Optional. The boards publish these feeds for reuse and answer datacenter IPs, so no proxy is needed. Turn on Apify Proxy (datacenter) only if a board starts refusing requests; residential proxies are not needed.

## Actor input object example

```json
{
  "sources": [
    "remoteok",
    "weworkremotely",
    "himalayas",
    "jobicy",
    "workingnomads",
    "arbeitnow"
  ],
  "keywords": [],
  "categories": [],
  "locations": [],
  "includeWorldwide": true,
  "jobTypes": [],
  "includeJobsWithoutSalary": false,
  "maxItems": 50,
  "dedupe": true,
  "order": "balanced",
  "includeDescriptionHtml": false,
  "startUrls": [
    "https://weworkremotely.com/categories/remote-programming-jobs.rss"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "sources": [
        "remoteok",
        "weworkremotely",
        "himalayas",
        "jobicy",
        "workingnomads",
        "arbeitnow"
    ],
    "maxItems": 50,
    "startUrls": [
        "https://weworkremotely.com/categories/remote-programming-jobs.rss"
    ],
    "proxyConfiguration": {
        "useApifyProxy": false
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("glasswing/remote-jobs-scraper").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 = {
    "sources": [
        "remoteok",
        "weworkremotely",
        "himalayas",
        "jobicy",
        "workingnomads",
        "arbeitnow",
    ],
    "maxItems": 50,
    "startUrls": ["https://weworkremotely.com/categories/remote-programming-jobs.rss"],
    "proxyConfiguration": { "useApifyProxy": False },
}

# Run the Actor and wait for it to finish
run = client.actor("glasswing/remote-jobs-scraper").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 '{
  "sources": [
    "remoteok",
    "weworkremotely",
    "himalayas",
    "jobicy",
    "workingnomads",
    "arbeitnow"
  ],
  "maxItems": 50,
  "startUrls": [
    "https://weworkremotely.com/categories/remote-programming-jobs.rss"
  ],
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}' |
apify call glasswing/remote-jobs-scraper --silent --output-dataset

```

## MCP server setup

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

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/J1iMczamvZsSTBz7u/builds/4f9BOeF5bmkgEAgZF/openapi.json