We Work Remotely remote jobs, companies and feeds as JSON
- endpoints
- 20
- credits per call
- 0–3
We Work Remotely publishes RSS feeds but no JSON API.
/weworkremotely/v1
- POST/weworkremotely/v1/search1 credit
- POST/weworkremotely/v1/category-jobs1 credit
- POST/weworkremotely/v1/region-jobs1 credit
- POST/weworkremotely/v1/type-jobs1 credit
- POST/weworkremotely/v1/salary-jobs1 credit
- POST/weworkremotely/v1/keyword-jobs1 credit
- POST/weworkremotely/v1/trending-jobs1 credit
- POST/weworkremotely/v1/latest3 credits
- POST/weworkremotely/v1/job1 credit
- POST/weworkremotely/v1/company1 credit
1 credit per call≈ $1/1,000 calls1,000 free credits, no card
Get a free API keyRun the call yourself, on the real endpoint
Change a parameter and press Try it. The response on the right is what your code will receive.
We Work Remotely API
5 of 20 endpoints, ready to run
Search remote jobs with the site's filters
// Press "Try it" and this pane shows exactly what the // live site returned this second — including an empty // result, if that is the truth. No key, no account.
What We Work Remotely endpoints does ReefAPI ship?
20 live read endpoints. Read-only data API: no writes, no account actions, no dashboard access on the target site.
search
1 crWe Work Remotely's own job search with every filter the site has.
- required
- —
- optional
- keyword, category, country, salary_range, skills, posted_within, job_filter
category-jobs
1 crEvery open job of one We Work Remotely category on one call.
- required
- category
- optional
- category, posted_within, job_filter
region-jobs
1 crJobs open to one region as the site files them (anywhere in the world, USA, North America, Am…
- required
- region
- optional
- region, page
type-jobs
1 crJobs of one engagement type.
- required
- job_type
- optional
- job_type, page
salary-jobs
1 crJobs in one of the site's yearly USD salary bands ($10k-25k … $100k or more), 50 per page.
- required
- salary_range
- optional
- salary_range, page
keyword-jobs
1 crThe site's keyword / skill landing page (/remote-<keyword>-jobs.
- required
- keyword
- optional
- keyword, page
trending-jobs
1 crThe site's 'Top Trending Remote Jobs' list, in the site's order, 50 per page.
- required
- —
- optional
- page
latest
3 crThe site's RSS feeds with the full job text.
- required
- —
- optional
- category, since, limit
job
1 crOne job in full.
- required
- job
- optional
- job
company
1 crA company's We Work Remotely profile.
- required
- company
- optional
- company
company-jobs
1 crEvery active job of one company (the company page lists them all), optionally only one category.
- required
- company
- optional
- company, category
top-companies
1 crThe site's Top 100 Remote Companies, ranked, with all-time jobs posted, 'Actively Hiring' bad…
- required
- —
- optional
- limit
hiring-companies
1 crCompanies the site marks as actively hiring now (25 on 2026-11-19), with Top-100 badge, all-t…
- required
- —
- optional
- —
top-searches
1 crThe site's 50 most searched remote-job keywords, ranked, each with its keyword for keyword-jobs.
- required
- —
- optional
- —
categories
0 crThe site's job categories with their keys, site ids, page and RSS URLs and grouping (programm…
- required
- —
- optional
- —
filters
1 crEvery option of the site's search form, live.
- required
- —
- optional
- —
skills
1 crThe site's skill list (~670, with the numeric ids its search uses), optionally filtered by a…
- required
- —
- optional
- query
countries
1 crThe countries the site's search can filter on (249), optionally filtered by a substring.
- required
- —
- optional
- query
statistics
2 crBoard statistics as the site prints them.
- required
- —
- optional
- —
breakdown
3 crThe whole board counted.
- required
- —
- optional
- top
Every parameter, every allowed value →
Missing a We Work Remotely endpoint, or need a source we don't have yet?Contact us real people · same-day reply.How the We Work Remotely API works
We Work Remotely is a normal ReefAPI surface — the same four rules that hold for every other engine on the key.
No OAuth app, no request signing, no per-site account. One key covers all 694 engines.
Every route is a POST with a JSON body. Parameters are validated against the published schema before anything is charged.
Credits, not seats. Failed and blocked calls are never charged, and nothing is cached: every call reads the source live.
One envelope everywhere. meta carries latency_ms, record_count and the endpoint that answered.
From a remote-job search to the employer behind each listing
Search the board, open the listings you want, then read the company and its other open jobs.
The jobs the site's search returns, with the exact total and the number of matches per category (6 on 2026-11-19).
Every full-stack job posted in the last 7 days in one call (40 on 2026-11-19).
The full listing: description, salary band, regions and countries, skills, dates, apply link and related jobs.
The company's profile, headquarters, website and every active job it has on the board.
The newest design jobs from the RSS feed with their full text.
A list of remote roles with their full listings and the employers behind them.
curl -X POST https://api.reefapi.com/weworkremotely/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"developer"}'{
"ok": true,
"data": { … },
"meta": {
"api": "weworkremotely",
"endpoint": "search",
"mode": "live",
"latency_ms": …,
"record_count": …
},
"error": null
}What a We Work Remotely field actually contains
Fields that read differently from how they look. Each row was measured on live We Work Remotely data on 2026-11-19.
| Field | What it holds |
|---|---|
| salary (job, every list) | The salary band the listing prints, such as "$100,000 or more USD", with its bounds in yearly USD. The site has five bands from $10,000 to $100,000 or more. 160 of 454 open jobs printed one; the rest publish no salary. |
| salary_ld_json (job) | The salary number in the page's structured data. It is the lower bound of the printed band (both ends say 100000 for "$100,000 or more USD"), not a real range. Use salary for the band. |
| first_posted_at (job, latest) | When the job was first posted. A renewed listing keeps this date: one listing first posted on 2024-06-16 showed "Posted on 16 days ago". The RSS date matched it on 17 of 17 jobs. |
| posted_label, posted_days_ago, is_renewed (job) | What the page prints as "Posted on", the same age in days, and whether the listing was renewed after it was first posted. The list cards' age matched the job page on 22 of 22 jobs. |
| regions, countries | The regions the listing is open to (Anywhere in the World, Europe Only, Asia Only…) and the countries it names. 100 of 454 open jobs name neither; 203 are open anywhere in the world. |
| apply_url, apply_requires_account (job) | The link behind the page's Apply button. For most jobs the site shows it only to signed-in job seekers; then apply_url is the site's sign-up page and apply_requires_account is true (17 of 22 jobs checked). |
| company.jobs_posted_all_time, company.jobs_posted_on_profile | On job pages and the Top 100 list, every job the company has posted on the board (Proxify AB: 195). The company profile prints its currently active jobs next to the same label (Proxify AB: 10). |
| is_repeat_on_page | True when the page lists the same job a second time. Sales and Marketing listed 3 of its 133 jobs twice; the rows are kept, not removed. |
search shows at most 25 jobs per category, as the site does, with the number of matches per category; category-jobs returns a whole category. List pages repeat a few jobs between consecutive pages (5 of 50 on full-time pages 1 and 2), so de-duplicate on job_slug.
We Work Remotely coverage, measured
Every number below comes from live calls on 2026-11-19; all 134 calls that ask for existing data answered.
458 open remote jobs in 10 categories (the site also said 43,300 jobs posted in total). category-jobs returned every job of every category: 133 Sales and Marketing, 89 Full-Stack Programming, 58 Customer Support.
Keyword, category, applicant country, salary band, skills, posted within 24 hours, 7 or 14 days, and the hot and boosted tabs each changed the total (of 458: engineer 87, United States 55, $100,000 or more 72, last 24 hours 65, boosted 34).
13 regions (anywhere in the world: 8 pages of 50), full-time and contract jobs, 5 salary bands, keyword pages such as javascript or software-developer, the trending list (9 pages) and the RSS feeds (all jobs: newest 94; one category: the whole category).
22 jobs from 10 lists matched their list cards on 220 of 220 values. The RSS feed matched the job pages on first-posted date, expiry date, headquarters and job type on 17 of 17 jobs.
Company profiles with all active jobs, the ranked Top 100 with all-time jobs posted, and 25 actively hiring companies.
Search shows at most 25 jobs per category, as on the site; use category-jobs for a whole category. 294 of 454 jobs print no salary and 100 name no region or country. For most jobs the employer's apply link is shown only to signed-in job seekers. Consecutive list pages can repeat a few jobs (5 of 50).
What people build with We Work Remotely
The jobs this data is most often used for.
Feed a remote-job board, newsletter or alert bot with new We Work Remotely listings and their full text.
Track which companies hire remotely, in which categories and for which regions or countries.
Collect the salary bands remote employers publish by category and region.
Build lead lists of remote-first employers from the Top 100 and actively-hiring lists.
endpoints
credits per call
What We Work Remotely data costs
The cheapest call here is 0 credits, so $15/mo (Pro) buys 10,000 of them — $1.50 per 1,000 credits. Credits roll over and never expire, and failed or blocked calls are not charged.
- 1,000 free credits on signup, no card
- One key, all 694 APIs, one credit pool
- Failed and blocked calls are never charged
- Credits roll over and never expire
Call it in two lines
Sign up, get 1,000 credits and one key that works on every engine. Then this is the whole protocol.
curl -X POST https://api.reefapi.com/weworkremotely/v1/search \
-H "x-api-key: $REEF_KEY" \
-H "content-type: application/json" \
-d '{"keyword":"developer"}'import os
import requests
REEF_KEY = os.environ["REEF_KEY"]
r = requests.post(
"https://api.reefapi.com/weworkremotely/v1/search",
headers={"x-api-key": REEF_KEY},
json={
"keyword": "developer"
},
timeout=90,
)
print(r.json()["data"])Have a question? We got answers.
The questions people actually ask before wiring up We Work Remotely.
Is there an official We Work Remotely API?▾
We Work Remotely publishes RSS feeds but no JSON API. This API returns its jobs, search, company profiles and lists as JSON; no We Work Remotely account is needed.
Which search filters work?▾
Each was checked against the unfiltered total on 2026-11-19 (458 jobs): keyword engineer 87, category full-stack programming 89, all programming 103, country United States 55, Germany 5, salary $100,000 or more 72, posted in the last 24 hours 65, last 7 days 181, last 14 days 278, hot jobs 367, boosted jobs 34. Several values of one filter mean any of them: United States or Canada 62.
How many results does a search return?▾
The site's search shows at most 25 jobs per category and has no further pages. The API returns the same rows, the exact total the site prints, and the number of matches in each category. To get a whole category, use category-jobs: it returned all 133 Sales and Marketing jobs in one call, and it takes the posted-within and hot or boosted filters.
How accurate is the data?▾
22 jobs opened from 10 different lists matched their list cards on 220 of 220 values: title, company, category, job type, regions, countries, salary band, listing id and posted age. The RSS feed matched the job pages on first-posted date, expiry date, headquarters and job type on 17 of 17 jobs.
Does it return salaries?▾
When the listing prints one: the salary band, such as "$75,000 - $99,999 USD", with its bounds in yearly USD. 160 of 454 open jobs had one on 2026-11-19. salary-jobs lists the jobs in one band and search filters by one or more bands.
Can I get the employer's apply link?▾
When the site shows it publicly, yes. For most listings the site shows the employer's apply link only to signed-in job seekers; the API then returns the site's sign-up link and apply_requires_account true. The job page link and the company's website are always returned.
What company data is there?▾
company returns the profile: name, logo, headquarters, website, Top 100 badge, about text, culture, benefits and hiring process when the company filled them in, and every active job. top-companies returns the site's ranked Top 100 with all-time jobs posted (Lumenalta 573, Contra 466, Toptal 387); hiring-companies returns the 25 companies marked as actively hiring.
What do statistics and breakdown return?▾
statistics returns the numbers the home page prints: 458 open jobs, the open jobs per category and the 43,300 jobs posted in total. breakdown reads every category and counts the 454 unique open jobs by category, job type (391 full-time, 63 contract), region, applicant country, salary band, posted age and flags, plus the companies with the most open jobs.
What is the We Work Remotely API?▾
We Work Remotely API is a ReefAPI endpoint group for remote job listings, search, companies and rss feeds from we work remotely. It returns live JSON through POST requests under /weworkremotely/v1.
Is the We Work Remotely API free to try?▾
Yes. ReefAPI starts with 1,000 free credits, no card required. We Work Remotely calls use the same shared credit balance as every other ReefAPI engine.
Do I need a We Work Remotely login or account?▾
No login to We Work Remotely is needed for the API response. You call ReefAPI with your x-api-key header, and the playground can run live examples before you create a production key.
How fresh is the We Work Remotely data?▾
The page example is captured from a live search call, and production requests fetch live data through ReefAPI rather than a static sample.
How many credits does the We Work Remotely API use?▾
We Work Remotely actions currently cost 1-3 credits per successful call. Failed or blocked calls are free. All APIs draw from one credit pool.
Can I call We Work Remotely from an AI assistant or MCP client?▾
Yes. Connect ReefAPI once through MCP and your assistant can call weworkremotely actions with the same key, credit pool and JSON envelope used by normal REST requests.
32 Jobs & Hiring APIs on the same key
One key, one credit pool, one response envelope. If you are pulling We Work Remotely, you are one call away from the rest of the category — no second contract, no second integration.
Need something this API does not do?
Name the endpoint, the field, or a source we do not carry yet. We ship new APIs every week and you would be first to get the key. Real people read every message and reply the same day.
Try it on your own data before you pay anything
The call above is the real endpoint, not a recording. A free key gives you 1,000 credits, the other 693 APIs, and the same envelope everywhere.
Endpoints, parameters and credit costs on this page are read from the live catalog and cannot drift from what the API accepts. Field notes were captured on 2026-11-19.