Jobicy Remote Jobs Scraper

Collect Jobicy remote jobs by keyword, industry and region, with company details, job types, seniority, published dates and salaries when available. Export the dataset to CSV, JSON or Excel for recruiting research, job boards and hiring analysis. No Jobicy login is needed.

Each keyword search returns a limited recent feed, not Jobicy's full historical archive. Additional filters can reduce the number of jobs saved.

Quick start

1. Open the Actor and start with a small search:

{
  "keywords": ["python"],
  "maxItems": 10,
  "includeDescription": false
}

2. Optionally add an industry or region in the input form, then click Start.
3. Open the dataset to review listings or download CSV, JSON or Excel.

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

Choose a public example to see its settings before starting a run:

• Export remote jobs with full descriptions
• Scrape remote software engineering jobs in the USA
• Scrape remote Python jobs from Jobicy

What you get

One public remote-job row with its ID, Jobicy URL, employer and available employment, industry, region, seniority and date fields. Salary values are included only when published, and full HTML descriptions are optional. This is a limited recent feed rather than Jobicy's historical archive.

Who is it for?

• Recruitment researchers reviewing companies advertising roles for selected tags.
• Job-board teams importing source-linked public listing samples.
• Workforce analysts comparing Jobicy's published industry, region and level labels.
• Text-analysis developers working with optional descriptions in their own pipelines.

How you can use the data

• Review a small Python-jobs sample. Use the existing python keyword with ten saved jobs and descriptions off. Retain ID, Jobicy URL, company and available labels, with missing salary values left unknown.
• Explore a source-labeled industry and region. Use the existing dev and usa examples with a small cap. These filters follow Jobicy's source behavior rather than strict local geographic checks, so inspect returned geo and industry values before comparing markets.
• Choose descriptions for a text-analysis export. Enable full descriptions for a bounded query and retain the original listing URL. Apply job-type, seniority or date filters to the returned feed without assuming the Actor keeps fetching until a historical interval is complete.
• Compare your own repeated searches. Join saved IDs or URLs and collection times in your destination. A published-date filter does not remember prior runs, applyUrl is the same Jobicy listing link rather than a guaranteed external application form, and the Actor does not score jobs or offer a custom sort.

Input settings

All fields are optional. An omitted API input searches without keyword, industry or region restrictions. The form's example values are Python, USA and dev. The default limit is 20 jobs and full descriptions are off.

Setting	JSON key	Meaning
Keywords / tags	keywords	List of Jobicy search tags. Leave empty for recent jobs across tags.
Industry category slug	category	Optional industry, such as dev, marketing or data-science.
Region / geo slug	geo	Optional region, such as usa, europe or latam.
Job types	jobTypes	Keep matching job types, such as Full-Time or Contract.
Seniority levels	jobLevels	Keep matching levels, such as Senior.
Maximum jobs	maxItems	Total saved-job limit, from 1 to 1000. Default 20.
Include full descriptions	includeDescription	Include the optional description field. Default false.
Published on or after	postedSince	Optional ISO date or timestamp for the earliest published date to keep.
Allow an empty result (legacy)	allowEmptyResults	Accepted for compatibility; completed searches with no matches succeed regardless of this value.

Use the input-field help for supported values. Job-type, seniority and published-date filters apply to the returned feed, so they can leave fewer results than requested. Category and region matching depend on Jobicy's own search behavior, not strict local checks.

Example inputs

Use the Quick start input as a small first run. Adjust the fields described above for your own data.

Output data

One dataset row represents one job listing. This abbreviated listing appeared in the existing documentation. It illustrates the returned fields, not a currently open vacancy:

{
  "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"
}

Field	Description
id	Numeric Jobicy job ID. Useful as a unique key.
url / jobSlug	Original Jobicy listing URL and slug.
title	Job title.
companyName / companyLogo	Company name and nullable logo URL.
industries / jobTypes	Lists of source-supplied industry and employment labels.
geo / level	Region and seniority labels, or null when unavailable.
excerpt	Short summary, or null when unavailable.
description	Full HTML description, present only when requested. May be null.
publishedAt	Source-supplied publish date, or null.
applyUrl	The same Jobicy listing URL as url, not a guaranteed external application link.
salaryMin / salaryMax	Numeric salary bounds, or null when not published.
salaryCurrency / salaryPeriod	Salary currency and period, or null.
source / scrapedAt	Source marker jobicy and the time the row was saved.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

Pay-per-event pricing charges start once after input validation and item for each saved job listing. Status or error rows are not intentionally emitted as paid listings.

See the live Pricing tab for current rates and discounts. Apify platform usage may also apply.

Tips for best results

• Start with one tag and a small saved-job cap. Each query exposes at most one hundred recent results rather than historical pages.
• Inspect returned labels for category and region comparisons. Source matching is not a strict local validation of geography.
• Request descriptions when their text is needed. Full HTML increases export size and can be absent.
• Check empty-result reasons. Completed searches with no matches succeed with an empty dataset. Request failures are not treated as no matches.
• Keep ID or URL and collection time when comparing exports. Overlapping keyword feeds can reduce unique coverage.

Limits and caveats

At most twenty-five keywords are accepted, and Jobicy exposes at most one hundred results per keyword query. A larger shared cap does not retrieve historical pages. Multiple tags can overlap, and job-type, seniority and date filters narrow the returned feed rather than guaranteeing a filled date interval.

Completed searches with no matching jobs succeed with an empty dataset and truthful per-query emptyReason values in RUN_SUMMARY, without requiring allowEmptyResults. That legacy setting remains accepted but no longer changes the outcome. Failed requests and unfinished queries are not successful no-match evidence. Useful rows from completed searches can remain when another query fails or the run approaches its time limit. RUN_SUMMARY reports saved counts, per-query outcomes and pending work.

Only public job listings are returned, with no Jobicy login or API key required. Candidate profiles, contact lists, job scoring and custom sorting are outside scope. Category and region matching depend on Jobicy rather than strict local checks.

Optional descriptions, salaries, dates, logos and other fields can be null. Keep salary currency and period when comparing compensation. The application URL is the Jobicy listing link, and a historical example does not establish a vacancy remains open. Repeat-run comparisons and downstream analysis require your own workflow.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST 'https://api.apify.com/v2/acts/fetch_cat~jobicy-remote-jobs-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "keywords": [
    "python"
  ],
  "maxItems": 10,
  "includeDescription": false
}
JSON

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"
  ],
  "maxItems": 10,
  "includeDescription": false
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/jobicy-remote-jobs-scraper').call(run_input={'keywords': ['python'], 'maxItems': 10, 'includeDescription': False})
print(client.dataset(run['defaultDatasetId']).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Jobicy Remote Jobs Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Jobicy Remote Jobs Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

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

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Jobicy Remote Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/jobicy-remote-jobs-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Use Fetch Cat’s Jobicy Remote Jobs Scraper to collect up to 5 Python jobs with descriptions off. Show source job IDs, companies and available region and seniority labels without assuming all matching history is included.”
• “Collect up to 5 Python jobs using category dev and geo usa with descriptions enabled. Keep Jobicy's returned industry and region labels for review rather than treating the filters as verified geographic eligibility.”
• “Retrieve up to 5 Python jobs at Senior level with descriptions enabled and empty results allowed. Keep published salary currency and period, and check query errors separately from legitimate no matches.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does Jobicy have a remote jobs API?

Jobicy provides a public jobs feed. This Actor packages listings into an Apify dataset with export and integration options. It is not an official Jobicy product.

Can I export Jobicy jobs to CSV or JSON?

Yes. Open the completed run's dataset to download CSV, JSON or Excel, or retrieve it through the Apify API.

Why did I get fewer jobs than requested?

The recent feed may contain fewer matching listings. Job-type, level and date filters narrow the fetched results, and several keyword searches can overlap. Increasing the limit does not guarantee more jobs.

Do I need a Jobicy account?

No Jobicy login or Jobicy API key is required. Running it through Apify requires your Apify account and, for API/MCP calls, authentication.

Why are salaries missing?

Many listings do not disclose compensation. Salary fields are null when unavailable. Inspect salaryPeriod before comparing published values.

Related Actors

• Ashby Jobs Scraper — Company career-board listings.
• ATS Jobs Scraper — Jobs from supported applicant-tracking systems.
• Remote.com Jobs Scraper — Another remote-jobs source.
• RemoteOK Jobs Scraper — RemoteOK listings.
• Reed.co.uk Jobs Scraper — UK-focused job searches.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥