Jobicy Remote Jobs Scraper

Collect fresh remote job listings from Jobicy and export clean job data to CSV, JSON, Excel, Google Sheets, or your own database.

Use this actor to monitor remote hiring by keyword, industry, region, and job type without building a custom integration. It returns structured listings with company details, job URLs, categories, seniority, publish dates, excerpts, and optional full descriptions.

At a glance

• Extracts: remote job titles, companies, logos, industries, job types, region labels, seniority, publish dates, excerpts, descriptions, and apply URLs.
• Inputs: keyword tags, Jobicy category slug, geo/region slug, job type filters, result limit, and description toggle.
• Best for: remote job boards, recruiting research, hiring-signal lead generation, job alerts, and labor-market monitoring.
• Exports: Apify dataset rows downloadable as CSV, JSON, Excel, XML, RSS, or available through the API.
• Login: no Jobicy account is required for public listings.

Ready-to-run examples

Use these saved Store examples as starting points. Open any example to prefill the Actor input, then adjust URLs, keywords, limits, or filters for your own run.

• Export remote jobs with full descriptions
• Scrape remote sales jobs in LATAM
• Find remote design jobs on Jobicy
• Scrape remote contract jobs from Jobicy
• Scrape remote data science jobs
• Find remote marketing jobs in Europe
• View all ready-to-run examples (8 examples)

What can it do?

• Find public remote jobs: collect fresh listings from Jobicy by keyword, category, region, and job type.
• Capture company context: save company names, logos, job titles, industries, levels, regions, and apply URLs.
• Control depth: include full HTML descriptions only when your workflow needs richer job text.
• Export clean rows: send results to CSV, JSON, Excel, XML, RSS, dashboards, or API workflows.
• Schedule monitoring: run recurring searches for job-market tracking or hiring-signal alerts.

Who is it for?

• Recruiters: track fresh remote openings in a niche.
• Job boards and aggregators: fill a remote-work feed from public listings.
• Lead generation teams: find companies actively hiring.
• Labor-market researchers: compare roles by region or industry.
• Career coaches and job seekers: build alerts from remote listings.

Why use this actor?

• No login: the actor reads public Jobicy listings.
• Simple filters: add tags, category, region, job type, and a result limit.
• Normalized output: join, filter, and deduplicate rows without custom parsing.
• Source URLs included: every row keeps Jobicy URLs and apply URLs for review or application workflows.

What data can you extract?

Each dataset row is one remote job listing. The default view highlights the fields most useful for sourcing and analysis. Turn on full descriptions only when you need rich job text.

Output fields

Field	Description
id	Jobicy job ID
url	Original Jobicy job URL
jobSlug	Jobicy slug
title	Job title
companyName	Hiring company
companyLogo	Company logo URL when available
industries	Jobicy industry labels
jobTypes	Job type labels such as Full-Time or Contract
geo	Region or location label
level	Seniority label when available
excerpt	Short job summary
description	Optional full HTML description
publishedAt	Published date from Jobicy
applyUrl	Source URL to use for application links
source	Source marker
scrapedAt	Timestamp when the actor saved the item

Pricing

This actor uses pay-per-event pricing. A $0.005 start event is charged once per run, and an item event is charged for each Jobicy job listing saved to the dataset.

Current BRONZE pricing is $0.000024997 per saved job, about $0.025 per 1,000 saved jobs, with lower per-job prices on higher Apify tiers.

The prefilled input is intentionally small so the first test run stays inexpensive. For large recurring monitoring, set maxItems to the smallest number that satisfies your workflow.

How to scrape Jobicy remote jobs

1. Open the actor on Apify.
2. Add one or more keyword tags such as python, react, or seo.
3. Optionally add an industry category slug and region slug.
4. Set the maximum number of jobs to save.
5. Run the actor and download the dataset in your preferred format.

Input configuration

Setting	JSON key	Description
Keywords / tags	keywords	Jobicy tag keywords such as python, react, seo, or sales. Leave empty for newest remote jobs.
Industry category slug	category	Optional Jobicy industry slug such as dev, marketing, data-science, business, or supporting. Legacy software-engineering maps to dev.
Region / geo slug	geo	Optional region filter such as usa, europe, emea, apac, latam, or worldwide.
Job types	jobTypes	Optional client-side job type filters such as Full-Time, Part-Time, Contract, Freelance, or Internship.
Maximum jobs	maxItems	Maximum number of job listings saved to the dataset.
Include full descriptions	includeDescription	Include full HTML job descriptions when available. Turn off for lighter exports.

Example input

{
  "keywords": ["python"],
  "category": "dev",
  "geo": "usa",
  "jobTypes": ["Full-Time"],
  "maxItems": 25,
  "includeDescription": false
}

Example output

{
  "id": 147705,
  "url": "https://jobicy.com/jobs/147705-cpq-architect",
  "title": "CPQ Architect",
  "companyName": "Autodesk",
  "industries": ["Software Engineering"],
  "jobTypes": ["Full-Time"],
  "geo": "APAC, Australia",
  "level": "Senior",
  "source": "jobicy"
}

Tips for best results

Start broad, then narrow by industry or region. Use multiple keyword runs when you want independent monitoring streams. Keep includeDescription off for faster lightweight exports. Use Apify schedules to refresh results daily or weekly. Deduplicate downstream by id or url.

Integrations

Send new jobs to Google Sheets for recruiter review. Pipe dataset items into Airtable or Notion for sourcing workflows. Connect webhooks to Slack alerts when matching jobs appear. Export JSON to a job board backend or search index. Use the Apify API from your data warehouse ingestion job.

API usage with Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/jobicy-remote-jobs-scraper').call({
  keywords: ['python'],
  category: 'dev',
  geo: 'usa',
  maxItems: 25,
});
console.log(run.defaultDatasetId);

API usage with Python

from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("fetch_cat/jobicy-remote-jobs-scraper").call(run_input={
    "keywords": ["python"],
    "category": "dev",
    "geo": "usa",
    "maxItems": 25,
})
print(run["defaultDatasetId"])

API usage with cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~jobicy-remote-jobs-scraper/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["python"],"category":"dev","geo":"usa","maxItems":20}'

MCP and AI agents

Use Apify MCP to run this actor from Claude Code, Claude Desktop, or other MCP-compatible tools. MCP URL: https://mcp.apify.com/?tools=fetch_cat/jobicy-remote-jobs-scraper

Claude Code quick add:

$claude mcp add apify-jobicy-remote-jobs --url "https://mcp.apify.com/?tools=fetch_cat/jobicy-remote-jobs-scraper"

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-jobicy-remote-jobs": {
      "url": "https://mcp.apify.com/?tools=fetch_cat/jobicy-remote-jobs-scraper"
    }
  }
}

Example prompts:

• "Run the Jobicy scraper for Python jobs in the USA and summarize the companies hiring."
• "Find remote marketing jobs and export the dataset URL."
• "Schedule a weekly scrape for full-time data science roles."

Legality and responsible use

This actor extracts publicly available job listing data. Respect Jobicy attribution expectations by keeping source links in your product or workflow. Do not misrepresent job listings, companies, or application links. Review your own compliance requirements before storing or republishing data.

Troubleshooting

If you receive fewer results than requested, the selected filters may have limited current listings. If a category returns broad results, verify that you used a Jobicy industry slug rather than a display label. If descriptions are large, turn off includeDescription for lighter exports. If scheduled runs repeat rows, deduplicate by id in your destination system.

Related actors

• Ashby Jobs Scraper
• ATS Jobs Scraper
• Remote.com Jobs Scraper
• RemoteOK Jobs Scraper
• Reed.co.uk Jobs Scraper

FAQ

Can I scrape Jobicy without an account?

Yes. This actor uses public Jobicy listings and does not ask for your Jobicy login.

Can I filter by region?

Yes. Use the geo input with region slugs such as usa, europe, emea, apac, or latam.

Can I get full job descriptions?

Yes. Enable includeDescription to include full HTML descriptions when available.

Can I run this every day?

Yes. Use Apify schedules and then send new rows to your preferred destination.

What should I use as a unique key?

Use id first, with url as a secondary unique key.

Support

If a run fails, returns no data, or a field looks wrong, open an issue from the Actor page.

Please include the Apify run ID or run URL, input JSON, one example public URL, query, or input item, what you expected, and what the dataset returned. Small reproducible inputs make parsing or site-layout issues much faster to fix.

Changelog

• 2026-07-04 - Feature: Launched Jobicy Remote Jobs Scraper on Apify Store (APIA-1222)
  • This actor is now publicly available at https://apify.com/fetch_cat/jobicy-remote-jobs-scraper.

0.1

• Initial version for public Jobicy remote job listings with keyword, category, region, job type, and optional description inputs.

Quick filter examples

Python jobs in the USA

keywords=python, category=dev, geo=usa Use a small maxItems value for the first run, then increase it once the filter matches your needs.

SEO jobs worldwide

keywords=seo, category=marketing Use a small maxItems value for the first run, then increase it once the filter matches your needs.

Data science in Europe

keywords=data, category=data-science, geo=europe Use a small maxItems value for the first run, then increase it once the filter matches your needs.

Customer support in LATAM

category=supporting, geo=latam Use a small maxItems value for the first run, then increase it once the filter matches your needs.

Design roles in APAC

category=dev, geo=apac Use a small maxItems value for the first run, then increase it once the filter matches your needs.