Working Nomads APIworkingnomads.com ↗
Search and filter remote job listings from Working Nomads. Access job titles, companies, categories, regions, and tags via a single paginated endpoint.
What is the Working Nomads API?
The Working Nomads API exposes one endpoint — search_jobs — that returns up to 100 remote job listings per page from workingnomads.com, a curated board focused on location-independent roles. Each job object includes title, company, category, region, tags, description, and featured/premium status, giving developers structured access to a continuously updated feed of remote positions across disciplines and geographies.
curl -X GET 'https://api.parse.bot/scraper/837c64f6-44c3-4462-8213-7d81ca05db78/search_jobs?query=python®ion=Europe&category=Development' \ -H 'X-API-Key: $PARSE_API_KEY'
Search remote job listings with optional filters for keyword, category, and region. Returns paginated results sorted by featured/premium status first, then by publication date descending. Each page returns up to 100 jobs.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination (1-indexed). |
| limit | integer | Number of results per page. Must be between 1 and 100. |
| query | string | Free-text search query matched against job title, tags, company, and description (e.g. 'python', 'react developer'). |
| region | string | Filter by geographic region. Matches jobs that list the specified region in their locations. Omitting returns all regions. |
| category | string | Filter by job category. Omitting returns all categories. |
{
"type": "object",
"fields": {
"jobs": "array of job listing objects",
"page": "current page number",
"limit": "results per page",
"total": "total number of matching jobs",
"has_more": "whether more pages are available"
},
"sample": {
"data": {
"jobs": [
{
"id": 1800514,
"slug": "senior-react-native-developer-lemonio-1800514",
"tags": [
"react native",
"react",
"nodejs",
"javascript",
"english"
],
"title": "Senior React Native Developer",
"company": "Lemon.io",
"premium": true,
"category": "Development",
"pub_date": "2026-08-18T14:55:22+00:00",
"locations": [
"Europe",
"North America",
"Latin America",
"APAC"
],
"company_slug": "lemonio",
"salary_range": null,
"location_base": "Europe, North America, Latin America, APAC",
"position_type": "ft",
"experience_level": "SENIOR_LEVEL"
}
],
"page": 1,
"limit": 5,
"total": 56,
"has_more": true
},
"status": "success"
}
}About the Working Nomads API
What the API Returns
The search_jobs endpoint returns an array of remote job listing objects alongside pagination metadata: page, limit, total, and has_more. Each job in the jobs array carries fields such as job title, company name, category, region, tags, and description. Results are sorted by featured/premium status first, then by publication date descending, so the freshest promoted listings always appear at the top.
Filtering and Pagination
The endpoint accepts four optional filter parameters. query performs free-text matching against job title, tags, company, and description — useful for searching specific technologies like python or react. category narrows results to a single job category (for example, engineering or design), while region filters to jobs that list a specific geographic region in their locations. Combine all three to get highly targeted slices of the listing feed. Pagination is controlled via page (1-indexed) and limit (1–100), making it straightforward to walk through large result sets or retrieve a single page snapshot.
Coverage and Freshness
Working Nomads focuses on remote-first and digital-nomad-friendly roles. The total field in each response reflects the live count of matching listings at the time of the request. Because results are sorted by publication date after featured items, high-page responses contain older listings, and iterating through all pages captures the full historical depth of the board.
The Working Nomads API is a managed, monitored endpoint for workingnomads.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when workingnomads.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official workingnomads.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Aggregate remote job feeds filtered by programming language or framework using the
queryparameter - Build a region-specific remote job alert system using the
regionfilter andhas_morepagination flag - Track hiring velocity for specific companies by querying company name and monitoring the
totalcount over time - Power a job board widget that surfaces only featured/premium listings from the first page of results
- Classify remote job market trends by iterating over category-filtered responses and analyzing tag frequency
- Sync a talent database with fresh remote listings by polling
search_jobssorted by publication date
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Working Nomads have an official developer API?+
What does each job object in the `jobs` array include?+
How does the `region` filter behave — does it support multiple regions in one request?+
region parameter matches jobs that list the specified region in their locations field and accepts a single value per request. It is not possible to pass multiple regions in one call. You can retrieve results for each region in separate requests and merge them client-side.Does the API expose individual job detail pages or application links?+
search_jobs endpoint returns listing-level fields — title, company, category, region, tags, and description — but does not return a dedicated structured field for the external application URL or a full job detail view. You can fork this API on Parse and revise it to add an endpoint that retrieves the full detail for a specific job listing.Can I filter jobs by salary or experience level?+
query, category, and region, but salary range and experience level are not available as filter parameters. You can fork this API on Parse and revise it to add salary or seniority filtering if the underlying data includes those fields.