# We Work Remotely Scraper — Remote Jobs, Salaries & Categories (`hipersoft/weworkremotely-scraper`) Actor

Scrape remote jobs from We Work Remotely: title, company, category, job type, region, salary (when listed), skills, logo, posted date, apply link and full description. Fast clean HTTP. For remote job boards, recruiting and talent research.

- **URL**: https://apify.com/hipersoft/weworkremotely-scraper.md
- **Developed by:** [Hipersoft](https://apify.com/hipersoft) (community)
- **Categories:** Jobs, Lead generation
- **Features:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.001 / job scraped

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

## We Work Remotely Jobs Scraper — Remote Jobs, Full Descriptions, Clean JSON

Scrape remote job listings from We Work Remotely and get clean, structured JSON — title, company, category, job type, region, salary (when listed), skills, logo, posted date, apply link and the full description. It reads WWR's rich public RSS feeds over fast, plain HTTP, so you can pull every remote job or just a single category.  Made for remote job boards, recruiters and talent researchers who want dependable data.

![We Work Remotely Jobs Scraper input — category slugs and per-category cap in the Apify Console](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/weworkremotely-scraper-input.png?v=2)

### Features

- 🌍 **All jobs or by category** — pass `"all"` for the full feed, or slugs like `remote-programming-jobs`, `remote-design-jobs`, `remote-devops-sysadmin-jobs`.
- 📝 **Full descriptions** — the `description` field carries the complete cleaned-up job text, not just a teaser.
- 🏢 **Company split out** — WWR's `"Company: Role"` title is parsed into separate `company` and `title` fields.
- 🌐 **Geo detail** — `region`, `state` and `country` are captured so you can filter by where the role can be done.
- 💰 **Salary + skills** — pulls `salary` when it appears in the listing, plus a `skills` field and the company `logo`.
- ⚡ **Fast, browser-free HTTP** — reads RSS feeds directly, no headless Chrome.
- 🎯 **Per-category caps** — `maxItemsPerCategory` keeps runs lean.

### What you get

![We Work Remotely Jobs Scraper output example — remote job listings as structured JSON](https://api.apify.com/v2/key-value-stores/SUfvnaFLd9z9eBCtV/records/weworkremotely-scraper-output.png?v=5)

Every listing becomes one clean JSON record:

```json
{
  "title": "Senior Full-Stack Engineer",
  "company": "Acme Software",
  "category": "Full-Stack Programming",
  "type": "Full-Time",
  "region": "Anywhere in the World",
  "state": null,
  "country": null,
  "skills": "JavaScript, React, Node.js",
  "salary": "$100,000 - $130,000",
  "logo": "https://weworkremotely.com/logos/acme.png",
  "postedAt": "Mon, 20 Jul 2026 09:00:00 +0000",
  "description": "Acme is hiring a senior full-stack engineer to build our product...",
  "url": "https://weworkremotely.com/remote-jobs/acme-senior-full-stack-engineer"
}
```

#### Output schema

| Field | Type | Description |
|-------|------|-------------|
| `title` | string | Job title, parsed out of WWR's `Company: Role` listing title. |
| `company` | string | Hiring company name. |
| `category` | string | Job category on We Work Remotely. |
| `type` | string | Employment type (e.g. Full-Time, Contract). |
| `region` | string | Where the role can be worked from (e.g. "Anywhere in the World"). |
| `state` | string | State/province the role is limited to, when specified. |
| `country` | string | Country the role is limited to, when specified. |
| `skills` | string | Skills or tags listed for the role. |
| `salary` | string | Salary range as listed, when present. |
| `logo` | string | URL of the company logo. |
| `postedAt` | string | When the job was posted (RFC-822 date string). |
| `description` | string | Full cleaned-up job description text. |
| `url` | string (URL) | Link to the job listing / apply page. |

### Input

```json
{
  "categories": ["remote-programming-jobs", "remote-design-jobs"],
  "maxItemsPerCategory": 100,
  "proxyConfiguration": { "useApifyProxy": false }
}
```

| Field | Description |
| --- | --- |
| `categories` | Category slugs, one per line. Use `"all"` for every remote job, or e.g. `remote-programming-jobs`, `remote-design-jobs`, `remote-sales-jobs`. A full WWR feed/category URL also works. |
| `maxItemsPerCategory` | Cap jobs per category (0 = all in the feed, ~100 for `"all"`). |
| `proxyConfiguration` | Optional. We Work Remotely works without a proxy. |

### Use cases

- Fill a remote job board with fresh, fully-described WWR listings.
- Build a category-specific feed (e.g. design or DevOps roles only).
- Source candidates by matching required skills across open remote roles.
- Track remote hiring by category, region and job type over time.

### Pricing

Pay-per-event: you're billed a small amount per run and per item scraped — you only pay for what you get. See the **Pricing** tab for current rates.

### FAQ

**How many jobs can I get per run?**
Pass `"all"` for the full feed (~100 latest jobs) or specific category slugs. Use `maxItemsPerCategory` to cap how many jobs each category returns.

**Is scraping We Work Remotely legal?**
Only public RSS feed data that WWR publishes openly is read. This is an independent tool, not affiliated with We Work Remotely; review their Terms of Service and applicable regulations for your use case.

**What's the output format?**
Clean JSON — one record per job with `title`, `company`, `category`, `type`, `region`/`state`/`country`, `salary`, `skills`, `logo`, `postedAt`, the full `description` and the apply `url`. Export as JSON, CSV or Excel.

**Can I filter by category?**
Yes. Pass category slugs like `remote-programming-jobs`, `remote-design-jobs` or `remote-devops-sysadmin-jobs`, one per line — or a full WWR feed/category URL. Use `"all"` for every remote job.

**Can I connect the We Work Remotely Jobs Scraper to other tools?**
The We Work Remotely Jobs Scraper can be connected with almost any cloud service or web app thanks to [integrations on the Apify platform](https://apify.com/integrations). It works with [Make](https://apify.com/integrations/make), [Zapier](https://apify.com/integrations/zapier), [Slack](https://docs.apify.com/platform/integrations/slack), [Airbyte](https://docs.apify.com/platform/integrations/airbyte), [GitHub](https://docs.apify.com/platform/integrations/github), [Google Drive](https://docs.apify.com/platform/integrations/drive) and [many more](https://apify.com/integrations), plus the [Apify API](https://docs.apify.com/api/v2), JavaScript/Python clients and MCP. Or use [webhooks](https://docs.apify.com/platform/integrations/webhooks) to trigger an action whenever a run finishes.

### Related Actors

Broaden your remote-jobs dataset with related scrapers:

- [RemoteOK Job Scraper](https://apify.com/hipersoft/remoteok-scraper) — remote roles with tags and salary ranges.
- [Remote Jobs Aggregator](https://apify.com/hipersoft/remote-jobs-aggregator) — five remote boards merged and de-duplicated into one dataset.
- [Dice Jobs Scraper](https://apify.com/hipersoft/dice-scraper) — US tech jobs from Dice with salaries.
- [Company Careers Job Scraper](https://apify.com/hipersoft/company-jobs-scraper) — roles straight from Greenhouse, Lever and Ashby boards.

### Notes

This Actor reads We Work Remotely's public RSS feeds. It is an independent tool and is not affiliated with, endorsed by, or sponsored by We Work Remotely; "We Work Remotely" is a trademark of its respective owner.

# Actor input Schema

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

Category slugs to scrape, one per line. Use "all" for every remote job, or e.g. "remote-programming-jobs", "remote-design-jobs", "remote-customer-support-jobs", "remote-devops-sysadmin-jobs", "remote-sales-jobs", "remote-marketing-jobs", "remote-product-jobs". A full weworkremotely.com feed/category URL also works.

## `maxItemsPerCategory` (type: `integer`):

Cap jobs per category (0 = all in the feed, ~100 for "all").

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

Optional. We Work Remotely works without a proxy.

## Actor input object example

```json
{
  "categories": [
    "all"
  ],
  "maxItemsPerCategory": 0,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# 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 = {
    "categories": [
        "all"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("hipersoft/weworkremotely-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 = { "categories": ["all"] }

# Run the Actor and wait for it to finish
run = client.actor("hipersoft/weworkremotely-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 '{
  "categories": [
    "all"
  ]
}' |
apify call hipersoft/weworkremotely-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hipersoft/weworkremotely-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/5R9oQeH05xDqUQley/builds/h1f1hNixHHksmktLi/openapi.json