# We Work Remotely Jobs — Search & Export (`jpmarketdata/weworkremotely-job-search-export`) Actor

Export We Work Remotely jobs by category or keyword with full descriptions, salary bands, applicant countries and original links. Deduplicate scheduled exports. Unofficial.

- **URL**: https://apify.com/jpmarketdata/weworkremotely-job-search-export.md
- **Developed by:** [h ichi](https://apify.com/jpmarketdata) (community)
- **Categories:** Jobs, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.50 / 1,000 job exporteds

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

## We Work Remotely Job Search Export

> **Unofficial** — independent tool, **not affiliated with, endorsed by, or sponsored by We Work Remotely**. It reads only publicly visible pages. Support, reliability guarantees and the full disclaimer are at the bottom of this page.

Export We Work Remotely jobs across a category watchlist or keyword searches. Get one deduplicated record per public posting with company, description, original job link and published applicant country restrictions.

### Input

`categories` defaults to an empty list, meaning the public main job list. Choose up to 10 category slugs: design, full-stack-programming, front-end-programming, back-end-programming, devops-sysadmin, product, customer-support, sales-and-marketing, management-and-finance, all-other. `keywords` accepts up to 5 search phrases; each search is fetched separately and deduplicated. When both lists are present, union the selected category and search results; do not pretend WWR combines category and text server-side. `maxJobs` defaults to 100, maximum 500. `includeDetails` defaults to true.

### Output

One `job` row per canonical public posting URL, with source category, title, employer, published country eligibility, exact dates and public salary when supplied, full clean description and the original public job link and a separately labelled source employer URL. An unknown field remains empty or null inside the salary object; 0/0 salary placeholders are treated as undisclosed. Equal positive JSON-LD values are source salary brackets, not verified exact salary: preserve the minimum and leave the maximum null. `sourceRank`, `reportedTotal`, `coverageComplete` and `outputLimited` show the chosen listing scope. An uncharged key-value SUMMARY records each category/search count, request count, scanned and emitted jobs, caps and source order. No claims of worldwide eligibility are inferred from the board name.

### Limits

Public HTML listing/search pages and public JobPosting JSON-LD detail pages only. Walk a real source next-page link while it exists; never silently stop at page 1. At most 10 categories plus 5 keywords, 500 unique jobs, 600 requests including robots and retries, 300 seconds, 256 MB, 4 MiB per response. At most 4 concurrent requests and 0.5 second spacing per host. A user cap returns a declared sample with outputLimited=true. Missing listing markers, malformed JobPosting, challenges, HTTP 401/403/429, timeout, or incomplete hard-budget traversal fail without charged rows. No proxy, browser, login, paid service or external company-page crawl. A completely verified zero-match query fails as no-matching-jobs with an uncharged SUMMARY, and is not sold as a negative brief.

### Privacy

Only public vacancy and employer organisation data. No job seekers, recruiter profiles, contacts, resumes, application forms, login or account pages. Strip email/phone contacts from descriptions and never open external application destinations. Preserve We Work Remotely attribution and original job links when displaying results. Independent tool, unaffiliated with the source or employer.

### Charging

One primary `job-exported` event at $0.0005 per delivered unique job, including the description and published detail fields. No start, request, detail, summary, webhook or failed-result fee. Before source requests, charge allowance must cover the requested maxJobs; reject insufficient allowance without silently lowering coverage. Every requested list/search is inspected and appears in SUMMARY even after the output cap. Pricing is an initial hypothesis to test against paid reuse and actual runtime cost.

### If something goes wrong

- **Wrong number or a failed run?** Open a ticket on the **Issues** tab. I read every one and reply within 2 business days (Japan time).
- **You never get a fake "empty" result.** If the site can't be read, the run fails and says so.
- **Delivered rows only.** One validated unique row is one billable event. Duplicates, summaries, failed acquisition and undelivered rows are not charged.
- **Checked every week.** An automatic test runs this tool weekly; if the site changes, I fix it.
- **Public source data only.** No login or member/applicant records. Contact patterns are screened before delivery; prose may still name people.

### More tools by the same author

- [RemoteOK Jobs — Multi-Tag Feed Export](https://apify.com/jpmarketdata/remoteok-multi-tag-job-feed-export)

All tools (Japan marketplaces, real estate, jobs, racing, prediction markets): <https://apify.com/jpmarketdata>

### Disclaimer

Unofficial, independent tool — **not affiliated with, endorsed by, or sponsored by We Work Remotely**. Product names and logos belong to their owners and only say where the data comes from. Data is read from public pages, for market research; check before you act on it.

# Actor input Schema

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

Union of selected category feeds. Empty selects the public main list if keywords are also empty.

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

Up to five public keyword searches. Combine matching jobs and remove duplicates.

## `maxJobs` (type: `integer`):

Global unique output cap, 1–500.

## `includeDetails` (type: `boolean`):

Read public JobPosting JSON-LD to include description, dates, pay and original apply URL.

## Actor input object example

```json
{
  "categories": [],
  "keywords": [],
  "maxJobs": 100,
  "includeDetails": true
}
```

# Actor output Schema

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

Validated job descriptions, salary facts and source coverage.

# 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("jpmarketdata/weworkremotely-job-search-export").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("jpmarketdata/weworkremotely-job-search-export").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 jpmarketdata/weworkremotely-job-search-export --silent --output-dataset

```

## MCP server setup

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

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/MNZdNNxMbgzfJ5SRZ/builds/RDQ5lhwES1kFC5Y9P/openapi.json