# We Work Remotely Jobs Scraper (`xtracto/weworkremotely-jobs`) Actor

Scrape remote job listings from We Work Remotely with the full job description, company, category, employment type, region and expiry date. Keyless RSS source, no login, no browser.

- **URL**: https://apify.com/xtracto/weworkremotely-jobs.md
- **Developed by:** [Farhan Febrian Nauval](https://apify.com/xtracto) (community)
- **Categories:** Jobs
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.33 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Roles with Full Descriptions

Scrape remote job listings from We Work Remotely: company, role, category, employment type, region
and country, posting and expiry dates — and **the complete job description**, which the source
publishes inline. Keyless public RSS. No login, no browser, no proxy needed.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `categories` | array | *all eight* | `programming`, `design`, `customer-support`, `devops-sysadmin`, `sales-marketing`, `product`, `management-finance`, `all-other` |
| `latestAcrossAllCategories` | boolean | `false` | One request, but capped at 90 jobs — see below |
| `maxItems` | integer | *all* | Stop after this many jobs |

### Output

```jsonc
{
  "_input": "sales-marketing",
  "_source": "S1-wwr-rss",
  "_scrapedAt": "2026-09-09T12:31:44Z",

  "url": "https://weworkremotely.com/remote-jobs/salesloft-enterprise-account-director",
  "slug": "salesloft-enterprise-account-director",
  "fullTitle": "Salesloft: Enterprise Account Director",
  "company": "Salesloft",
  "title": "Enterprise Account Director",

  "category": "All Other Remote",
  "employmentType": "Full-Time",
  "region": "Anywhere in the World",
  "country": "United States of America",
  "countryRaw": "🇺🇸 United States of America",
  "state": null,
  "skills": null,

  "description": "Headquarters: United States, Remote\n\nJob Title: …",
  "descriptionHtml": "<p><strong>Headquarters:</strong> …</p>",

  "publishedAt": "2026-09-09T07:30:45Z",
  "expiresAt": "2026-10-09T07:30:45Z"
}
```

### Three things worth knowing

**The combined feed is capped; the category feeds are not.** `/remote-jobs.rss` returns 90 items,
roughly ten per category, and looks like the whole board until you compare it. Reading the eight
category feeds at the same moment returned **238 distinct jobs**. So "all categories" is the
default and `latestAcrossAllCategories` is offered only as a one-request "what is new" shortcut,
labelled as such.

**The title packs company and role together, and the split is on the *first* colon.**
`Salesloft: Enterprise Account Director` is easy; `IxDF - Interaction Design Foundation: Course
Director: UX, UI, and AI` is not. Four of ninety titles in one sample carried more than one colon,
and splitting on the last would have moved half the company name into the role. `fullTitle` is kept
alongside the split so nothing is lost.

**No per-job request is needed.** The RSS carries the entire description inline — 737 characters at
the shortest, a median of 5,267, up to 18,707. Scraping the whole board costs eight requests.

### Country is usually empty, and that is the data

Only 30 of 238 jobs named a country; the rest are `Anywhere in the World` or similar, which is what
`region` is for. An empty `country` here means "not restricted to one", not a missing value.

### Errors

| `_error` | Meaning |
|---|---|
| `feed_not_found` | 404 — the category slug moved |
| `empty_feed` | 200 with no `<item>` elements, so the feed format changed |
| `unexpected_shape` | An item with neither a link nor a guid |
| `blocked` | Every TLS profile was refused |
| `network_error` | The ladder never reached the server — DNS, timeout, reset |

A job listed under two categories is emitted once: these feeds are slices of one board, so
de-duplication is across the whole run, by URL.

If no jobs are scraped at all, the run fails rather than reporting success over an empty dataset.

# Actor input Schema

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

Which category feeds to read. Leave empty for all eight, which is the way to get the most jobs.

## `latestAcrossAllCategories` (type: `boolean`):

Read the combined feed instead of the category feeds. It is one request but capped at 90 jobs, roughly ten per category — use it for a quick 'what is new', not for coverage.

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

Stop after this many. Leave empty for everything the chosen feeds hold.

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

Optional. These are public RSS feeds with no anti-bot layer, so a proxy is not needed.

## Actor input object example

```json
{
  "latestAcrossAllCategories": false
}
```

# Actor output Schema

## `overview` (type: `string`):

Dataset items shown in the 'Jobs' view.

## `items` (type: `string`):

Every record this run produced, with all fields, as JSON.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("xtracto/weworkremotely-jobs").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("xtracto/weworkremotely-jobs").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 '{}' |
apify call xtracto/weworkremotely-jobs --silent --output-dataset

```

## MCP server setup

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

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/XLHbufe20lE5eU2yX/builds/1NzaOu0uFlRhZA9be/openapi.json