RemoteOK Scraper | $1.50/1K — Official API, Salary Min/Max

For remote-first companies tracking competitor hiring, job aggregators building remote-only boards, and data teams studying the remote job market — RemoteOK's official API is the authoritative source.

Pricing: $1.50/1,000 jobs ($0.0015 each — you pay only for results returned)

Scrape remote job listings from RemoteOK via the official public JSON API. Give it a tag (or leave blank for all listings) — get back clean, enriched job data in seconds. No login, no API key, no browser, no proxy required.

Get started instantly: use the pre-filled "python" tag example or enter any RemoteOK tag. Try it free — Apify's $5/month free tier covers thousands of runs.

What this RemoteOK scraper does

• Fetches all open remote jobs from remoteok.com/api — the official public JSON endpoint.
• Filters by tag (e.g. "python", "react", "senior") using RemoteOK's native tag system.
• Returns a clean flat schema — identical fields every run, no parsing surprises.
• Enriches each job with seniority (intern / entry / mid / senior / lead / staff / principal / manager / director / vp / executive) from RemoteOK tags first, then title.
• Returns salary range (min/max USD) when RemoteOK discloses it.
• Returns full job descriptions as both plain text and HTML (togglable).
• Includes a parse_confidence score (0–1.0) and warnings list in every record.
• Supports multi-tag batch runs — enter comma-separated tags for a single API call.
• maxItems cap (default 100) prevents surprise bills on first runs.
• All jobs are remote by definition — remote: true on every record.

What data you get

One flat row per job — 17 structured fields:

{
  "job_id": "1132574",
  "title": "Entry Level Junior Trader",
  "company": "Infiniti Group",
  "location": "Anywhere",
  "tags": ["other", "finance", "analyst", "entry level"],
  "salary_min": 50000,
  "salary_max": 60000,
  "remote": true,
  "seniority": "entry",
  "posted_at": "2026-05-30T08:26:26+00:00",
  "url": "https://remoteOK.com/remote-jobs/...",
  "apply_url": "https://remoteOK.com/remote-jobs/...",
  "description_text": "We are looking for a Junior Trader...",
  "description_html": "<p>We are looking for a <strong>Junior Trader</strong>...</p>",
  "parse_confidence": 1.0,
  "warnings": [],
  "scraped_at": "2026-05-31T12:00:00+00:00"
}

Field notes:

• salary_min / salary_max are null when not disclosed (most listings). Annual USD.
• seniority is inferred from RemoteOK tags first (cleaner), then job title.
• remote is always true — every job on RemoteOK is remote by definition.
• parse_confidence is 1.0 for a fully-populated job; small deductions for missing optional fields. Check warnings for the reason codes.

Input schema

Field	Type	Default	Description
searchTags	string	"python"	RemoteOK tag filter. Comma-separate for multi-tag: "python,django". Leave blank for all jobs.
keywords	string	—	Case-insensitive title keyword filter (applied client-side)
maxItems	integer	100	Cap on total jobs returned (0 = unlimited)
includeDescriptions	boolean	true	Include description_text + description_html

Common tags

Technology: python, javascript, typescript, react, node, go, rust, devops, aws, kubernetes, django, rails, vue, flutter, ios, android

Function: design, marketing, finance, sales, hr, legal, medical, customer support

Seniority: senior, exec, lead, entry level, intern

Type: saas, b2b, startup, non tech, digital nomad

Pricing example

Run	Jobs returned	Cost
Quick trial (1 tag, 100-cap default)	~100	$0.15
1,000 jobs (10 tags)	1,000	$1.50
All listings (no tag, unlimited)	~200–400	$0.30–$0.60

Pay-per-result: $1.50 / 1,000 jobs ($0.0015 each). You pay only for jobs returned. RemoteOK's public API is free — your compute cost is just Apify's platform usage, which the buyer pays.

FAQ

Do I need an API key or proxy? No. RemoteOK's /api endpoint is officially public — no credentials, no proxy, no browser.

What formats can I export? JSON, CSV, Excel, or JSONL — from the Apify dataset UI or via REST API.

How many jobs are available? RemoteOK typically has 200–400 active listings at any time. With a tag filter you get the subset matching that tag.

What if a tag returns 0 results? The actor skips that tag cleanly and continues — no crash, no charge.

Reliability

RemoteOK's /api endpoint is a stable, officially public JSON feed with no authentication and no rate limiting under normal usage. This actor uses zero browser, zero proxy — just direct HTTP to the official endpoint with a realistic User-Agent. Parse confidence is consistently 1.0 on complete listings.

Typical run: 100 jobs in under 3 seconds.

Use cases

• Job aggregation — build a searchable board of remote jobs by technology stack.
• Hiring intelligence — track which companies are hiring for specific skills remotely.
• AI agent input — feed job data to an LLM for matching, summarizing or alerting.
• Lead generation — identify fast-growing companies hiring remote engineers.
• Salary research — collect salary ranges for remote roles by tag/function.
• Career monitoring — set up alerts for new remote roles matching your skills.

Use with AI agents (MCP)

This actor is available via Apify's MCP server. Connect it to any MCP-compatible agent (Claude, n8n, Make) to pull live remote job data on demand — no code required.

https://mcp.apify.com/?tools=bovi/remoteok-scraper

Alternatives and comparison

Feature	This scraper	Generic job scrapers
parse_confidence score	Yes	No
Seniority enrichment	Yes (tags + title, 11 levels)	Rarely
Salary min/max (integer fields)	Yes (when disclosed)	String only or missing
Tag-based filtering	Yes (native API)	No
Multi-tag batch	Yes	No
Official API (not HTML scrape)	Yes	Rarely
Zero proxy	Yes	Often needs proxy
Price	$1.50/1K	Varies

Every record includes parse_confidence (1.0 for complete listings). Check warnings for the specific reason code when it drops. RemoteOK's API is stable — 1.0 is the norm.

Attribution

RemoteOK's API Terms of Service require linking back to RemoteOK with a follow link and crediting RemoteOK as the source in any published use of the data. Please ensure your downstream application attributes RemoteOK appropriately.

This actor is not affiliated with, endorsed by, or partnered with RemoteOK or its parent company. It uses the freely accessible public JSON API at remoteok.com/api.

Integrations

Built for remote-first hiring teams and job aggregators monitoring the remote job market by tag and salary — the JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — trigger a run or pipe every new dataset item into 500+ apps (Google Sheets, Airtable, Slack, HubSpot, your database) with no code: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes, to push results straight into your pipeline (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client so an AI agent can pull this data mid-conversation (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.