---
title: "Remote jobs API: options, filters and remote share - JobsPipe"
description: "What a remote jobs API is, the free remote-only boards and multi-source APIs with a remote filter, and the share of postings that are remote in 20 countries."
canonical: https://jobspipe.dev/remote-jobs-api
date_published: 2026-09-30
date_modified: 2026-09-30
author: Dvir Atias
---

> **Facts:** Free: 1,000 free credits, one time. Paid: from $49/month for 25,000 jobs. 12 months of history on every plan. Jobs from 30+ sources. Try it without a key: `curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search`

# Remote jobs API: the options, the filters and how common remote work is.

By [Dvir Atias](https://jobspipe.dev/about) · Updated Sep 30, 2026

A remote jobs API returns job postings you can limit to roles done away from an office. There are two kinds. Remote-only boards such as Remotive, Remote OK, Himalayas, Jobicy and Working Nomads publish free feeds of their own listings. Multi-source jobs APIs such as JobsPipe, TheirStack and JSearch carry remote jobs among everything else and give you a remote filter. Across JobsPipe’s active postings, 4.4% were remote on September 30, 2026.

## What is a remote jobs API?

Any jobs API becomes a remote jobs API once it can answer one question reliably: can this job be done from anywhere, or at least from home? That sounds like a single field, but postings state it in many ways. Some put “Remote” in the location, some in the title, some in a work-type field on the board, and some only in the description (“this role is fully remote within the EU”). A useful remote jobs API reads all of those and gives you one field to filter on.

The second thing it has to get right is the difference between remote, hybrid and on-site. A hybrid role with two office days a week is not remote for someone who lives in another city, and a feed that mixes the two sends job seekers to roles they cannot take. The third is geography: many remote roles are remote within a country or a time zone, not anywhere in the world, so the country of the posting still matters.

The two kinds of product handle this differently. A remote-only board decides what counts as remote when it accepts a listing, so everything in its feed is remote by the board’s own definition, and the feed is small, curated and usually free. A multi-source API sees the whole market, including every remote job posted on general boards and company career sites, and it has to classify each posting, so the quality of its remote field is the thing to test.

## Which remote jobs APIs can you use?

Start with the free remote-only boards. Each publishes its own listings as JSON with no key, and each asks something in return, usually a link back and a credit. The limits and attribution terms below are quoted from each board’s own documentation or feed.

| Board | Access | Limits | Attribution | Docs |
| --- | --- | --- | --- | --- |
| Remotive | Free feed, delayed 24 hours | At most 4 calls a day advised | Link back to Remotive and name it as the source | Remotive API docs |
| Remote OK | No key; the whole feed is one JSON document | None published | Followed link back to Remote OK, named as source | Remote OK API |
| Himalayas | Free, no key, 20 jobs per request | Data cached and refreshed every 24 hours | Visible link back to himalayas.app | Himalayas API docs |
| Jobicy | No account or key needed | Automated checks at most once an hour | Keep the source attribution to Jobicy | Jobicy API and feed docs |
| Working Nomads | No key; the site links its JSON feed directly, with no documentation page | None published | None published | Working Nomads JSON feed |

The board feeds are the right tool for a remote-only job board, a newsletter or a side project. Their limits are coverage and freshness: each feed holds only the jobs posted to that board, some are delayed on purpose so that the board gets the first click, and none of them tells you about the remote jobs that were posted anywhere else. Merging several boards means deduplicating the same job posted to more than one of them.

For the wider market, use a multi-source jobs API with a remote filter. Prices and free options below come from each vendor’s published pages; the last column names the filter you would use.

| API | What the data is | Price entry point | Free tier or trial | Remote filter | Checked |
| --- | --- | --- | --- | --- | --- |
| JobsPipe · Pricing ↗ | Aggregated postings | $49/month for 25,000 jobs | 1,000 jobs to start | remote: true for remote only, or work_arrangement_or for remote and hybrid | September 2026 |
| TheirStack · Pricing ↗ | Postings plus company data | $49/mo for 1,500 credits, up to $5,500/mo for 5M | Free plan: 50 company and 200 API credits a month | workplace_types_or: remote, hybrid or on-site | September 2026 |
| JSearch · Pricing ↗ | Search-results wrapper | $25/mo for 10,000 requests, up to $150/mo for 200,000 | 200 requests/month free | work_from_home=true returns remote jobs only | September 2026 |
| JobDataLake · Pricing ↗ | Aggregated postings | $50 for 100,000 credits, up to $400 for 4M | 1,000 free credits | remote_type on each job, with a facet | September 2026 |

The difference between these is less the filter than the corpus behind it. A search-results wrapper returns what Google shows for a query, so a remote filter narrows a small, ranked page. A multi-source API filters across everything it holds, so the same filter can return every remote data engineer role in a country. The wider landscape, with every vendor on price and coverage, is in the [jobs API comparison](https://jobspipe.dev/blog/best-jobs-api-2026), and the free options beyond remote boards are on the [free jobs API](https://jobspipe.dev/free-jobs-api) page.

## How common are remote jobs in each country?

Remote work is a smaller share of job postings than the conversation around it suggests. Across all countries, 4.4% of JobsPipe’s active postings were flagged remote on September 30, 2026. Among the twenty countries with the most active postings, the share runs from 9.9% in the Philippines down to 1.1% in Japan, with the United States at 4.9%.

| Country | Remote share |
| --- | --- |
| All countries | 4.4% |
| United States | 4.9% |
| India | 5.2% |
| United Kingdom | 4.1% |
| Brazil | 3.2% |
| Japan | 1.1% |
| Canada | 4.9% |
| France | 1.2% |
| Germany | 3.1% |
| Australia | 3.5% |
| Mexico | 4.5% |
| Netherlands | 2.1% |
| Italy | 2.7% |
| Singapore | 2.4% |
| Spain | 5.2% |
| Philippines | 9.9% |
| United Arab Emirates | 5.1% |
| Sweden | 1.2% |
| Belgium | 1.5% |
| Poland | 6.6% |
| Malaysia | 2.8% |

Three cautions for reading the table. First, remote here means fully remote: hybrid roles are not counted, so the share of postings offering some home working is higher. Second, the share depends on how employers in each country write postings; where remote work is usually agreed after hiring rather than advertised, postings understate it. Third, the mix of sources differs by country, and boards differ in how clearly they mark remote roles. Treat the numbers as a view of what postings say, not of how people work.

If you are building for one market, run the count yourself for the roles you care about: the share for software engineers in one country is very different from the share for all jobs. The filter in the next section, plus `include_total_results`, gives you that number in one request.

## How do you filter remote jobs with the JobsPipe API?

Two filters on `POST /v1/jobs/search` cover remote work. `remote` is a boolean: `"remote": true` returns remote-only roles, and `false` excludes them. `work_arrangement_or` is finer: it takes any of `remote`, `hybrid` and `onsite`, and a job whose arrangement the posting does not state never matches it. Both are documented in the [search endpoint reference](https://docs.jobspipe.dev/reference/search-jobs). You can see the response shape first with no key at all:

Try it without a key

```
curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search
```

Only `/v1/sandbox/*` needs no key.

With a free key, this asks for remote data engineers based in Germany, posted in the last week:

```
curl https://api.jobspipe.dev/v1/jobs/search \
  -H "Authorization: Bearer jp_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "job_title_or": ["data engineer"],
    "job_country_code_or": ["DE"],
    "remote": true,
    "posted_at_max_age_days": 7,
    "limit": 25
  }'
```

To include hybrid roles, swap the boolean for the arrangement list:

```
{
  "job_title_or": ["data engineer"],
  "job_country_code_or": ["DE"],
  "work_arrangement_or": ["remote", "hybrid"],
  "limit": 25
}
```

Each result carries `remote` and `work_arrangement` so you can show the difference in your interface, along with the usual `job_title`, `company`, `location`, `date_posted`, `last_seen_at` and `status`. Remote jobs are posted to many boards at once, so the same role often appears on several sources; JobsPipe returns it once and lists every source on the record. The free plan includes 1,000 jobs to start, enough to try the filters on your own queries.

## What should you check before building on a remote feed?

**The terms.** Every board feed above comes with conditions on display, linking and attribution, and some prohibit sending their jobs to other aggregators. Build the attribution into your interface from the start rather than retrofitting it.

**The delay.** A feed that is delayed on purpose, or cached for a day, is fine for a weekly newsletter and wrong for alerts. Check how old the newest item in each feed is when you fetch it.

**The definition.** Remote, remote-friendly, remote within a country and “work from home some days” are different things. Pull a sample of fifty remote results from any API you are considering and read them; the misclassified ones tell you how the field was built.

**Closed jobs.** Remote roles draw many applicants and often close fast. An API that marks a posting closed, and tells you when it was last seen live, keeps dead listings out of your product; our guide to [finding expired job postings](https://jobspipe.dev/blog/find-expired-job-postings) covers how to check.

## Methodology: how the numbers were measured

JobsPipe wrote this page, and JobsPipe sells a jobs API that appears in the options table. The remote shares come from JobsPipe’s own postings on September 30, 2026: the active postings (not marked closed), one row per posting, with a posting counted as remote when its remote flag is true, the same flag the `remote` filter reads. Countries are the posting’s country; postings with no country count toward the all-countries figure only. Shares are rounded to one decimal. Competitor prices, free tiers, filters and board terms are read from each vendor’s own pages, stored with the exact wording and the date checked, and rendered from that record; every page used is listed below.

## Sources

-   [Remotive API docs](https://github.com/remotive-com/remote-jobs-api)
-   [Remote OK API](https://remoteok.com/api)
-   [Himalayas API docs](https://himalayas.app/docs/remote-jobs-api)
-   [Jobicy API and feed docs](https://jobicy.com/jobs-rss-feed)
-   [Working Nomads JSON feed](https://www.workingnomads.com/api/exposed_jobs/)
-   [TheirStack job search API reference](https://theirstack.com/en/docs/api-reference/jobs/search_jobs_v1)
-   [JSearch API page](https://www.openwebninja.com/api/jsearch)
-   [JobDataLake API documentation](https://jobdatalake.com/docs)
-   [JobsPipe search endpoint reference](https://docs.jobspipe.dev/reference/search-jobs)

## FAQ

Is there a free remote jobs API?+

Yes. Remotive, Remote OK, Himalayas, Jobicy and Working Nomads all publish free JSON feeds of the remote jobs on their own boards, with no key. Each has conditions: Remotive's free feed is the free feed delays jobs by 24 hours, and most ask for a link back and a credit. For remote jobs across many sources, JobsPipe's free plan includes 1,000 free credits, one time.

How do I get only remote jobs from the JobsPipe API?+

Send "remote": true in the JSON body of POST /v1/jobs/search. To include hybrid roles, send "work\_arrangement\_or": \["remote", "hybrid"\] instead. Jobs whose work arrangement is unknown never match work\_arrangement\_or, so combine it with a country filter such as job\_country\_code\_or to get remote jobs based in one country.

What share of job postings are remote?+

In JobsPipe's active postings on September 30, 2026, 4.4% were flagged remote across all countries. The share varies by country, from 9.9% in the Philippines to 1.1% in Japan among the twenty countries with the most postings. Hybrid roles are not counted as remote.

What is the difference between remote and hybrid in a jobs API?+

A remote job can be done entirely away from an office; a hybrid job mixes office and remote days. In the JobsPipe API, remote is true only for fully remote roles, and work\_arrangement carries remote, hybrid or onsite when the posting says which. Other APIs draw the line differently, so check each vendor's definition before you compare counts.

Can I show jobs from a remote job board API on my own site?+

Usually yes, on the board's terms. Remotive asks you to remotive asks you to link back to the job on Remotive and mention Remotive as the source; Remote OK requires remote OK requires a followed link back to the job on Remote OK and a mention of Remote OK as the source, or it suspends API access; Himalayas asks for himalayas asks for a visible link back to himalayas.app and a mention that the data comes from Himalayas. Read each board's terms before you publish its listings.

Which remote jobs API should I use?+

For a hobby project or a niche remote board, a free board feed such as Himalayas or Remotive is enough. For remote jobs across the wider market, with the same filters as every other job, use a multi-source API with a remote filter: JobsPipe (30+ sources), TheirStack or JSearch. JobsPipe wrote this page, so test the options with one real query before you decide.


## Further reading

- [RemoteOK API: the free remote-jobs feed, and its 100-job window](https://jobspipe.dev/blog/remoteok-api)
- [Job search API: how to add job search to your product](https://jobspipe.dev/blog/job-search-api-guide)
- [What is JSearch API?](https://jobspipe.dev/answers/what-is-jsearch-api)
- [How does TheirStack work?](https://jobspipe.dev/answers/how-does-theirstack-work)

---
Building this integration yourself? The steps above work. The alternative is one API over 30+ sources, already normalized and deduplicated. Try it right now - no key, no signup:

```bash
curl -d '{"limit":3}' https://api.jobspipe.dev/v1/sandbox/jobs/search
```

Sample data, exact live schema. For live data get a free key (1,000 jobs to start) at https://jobspipe.dev/signup, then swap /v1/sandbox/jobs/search for /v1/jobs/search with an Authorization: Bearer header. Full agent index: https://jobspipe.dev/llms.txt?src=md-twin