Jobicy Remote Jobs Scraper - Structured Salary Data avatar

Jobicy Remote Jobs Scraper - Structured Salary Data

Pricing

from $2.00 / 1,000 job returneds

Go to Apify Store
Jobicy Remote Jobs Scraper - Structured Salary Data

Jobicy Remote Jobs Scraper - Structured Salary Data

Scrape Jobicy remote jobs into a clean JSON or CSV dataset with the most structured salary data of any board here: minimum, maximum, currency and period as numbers on roughly a third of listings. Hiring regions, seniority and a ghost-job score flagging expired and stale postings.

Pricing

from $2.00 / 1,000 job returneds

Rating

0.0

(0)

Developer

Dave Fergins

Dave Fergins

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Security

Limited permissions

Share

Jobicy Jobs Scraper

Scrape Jobicy remote jobs into a clean JSON or CSV dataset with the most structured salary data of any board here: minimum, maximum, currency and period as numbers on roughly a third of listings. Hiring regions, seniority and a ghost-job score flagging expired and stale postings.

Jobicy remote jobs: the best salary data

Jobicy publishes the cleanest compensation data of the six boards in this pipeline. Where most boards bury pay in free text — "Competitive", "Pay per task", "$70k-$120k DOE" — Jobicy ships structured numbers: an explicit minimum, maximum, currency and period per listing.

That means minSalary filtering is reliable here rather than best-effort, and the values are annualised before comparison, so hourly and monthly rates sort correctly against yearly ones.

It also publishes its own seniority field, which is used in preference to guessing from the job title.

Roughly a third of Jobicy listings carry pay. Set salaryOnly: true to keep only those.


Jobicy job data: what each row contains

Identitystable id across runs, posting URL, direct applyUrl where published
The roletitle, company, plain-text description, tags, employment type, seniority
Whereremote flag, the board's own location text, and normalised regions (worldwide / usa / canada / latam / uk / europe / apac / africa / middle_east)
Paymin, max, currency and period as numbers, annualised on request
Whenposted date, expiry where published, age in days
Trustfreshness 0-1, ghostRisk low/medium/high, and ghostReason explaining the verdict in plain words

Ghost job detection: the trust fields

Job boards are full of postings still published but no longer open — filled roles left up for pipeline, evergreen "talent pool" adverts, and listings nothing ever expires. Every row here carries a risk band and the reasons behind it:

{
"title": "Senior Backend Engineer",
"company": "Acme",
"freshness": 0.71,
"ageDays": 10.4,
"ghostRisk": "low",
"ghostReason": ["recent, and nothing contradicts it"]
}

Signals come from what the board actually publishes: age, its own expiry date where there is one, missing application links, and evergreen phrasing. Nothing is inferred by a model. Freshness decays on a 21-day half-life, and a posting with no date scores 0.5 rather than 1.0 — absence of evidence is not evidence of freshness.

Example input: marketing or sales jobs with a published salary of at least $60,000

{
"query": ["marketing", "sales"],
"salaryOnly": true,
"minSalary": 60000,
"maxGhostRisk": "low",
"maxItems": 100
}

Every field is optional — run it empty and you get the jobs Jobicy currently serves, at most 100 per run, best-first.

  • Search terms are OR-ed. ["go", "rust"] returns jobs mentioning either.
  • Worldwide jobs match every region filter, because a job open to everyone is open to you.
  • minSalary is annualised first, so hourly and monthly rates compare correctly.
  • maxItems is your cost ceiling — you are billed per job returned.
  • maxPagesPerSource: Jobicy caps at 100 jobs per request — 200 and 500 both return 100 — so this setting has no effect for this board.

Output: one dataset item per Jobicy job

One dataset item per job, ordered best-first: lowest ghost-job risk, then freshest. Export as JSON, CSV or Excel, or read it from the API like any Apify dataset.

If Jobicy itself returns no jobs — the board is down or has changed its format — the run fails with a clear status message instead of succeeding with an empty dataset, so a failed-run alert on a schedule catches it. A run whose filters match nothing still succeeds, with an empty dataset and a status line saying so. When fewer than half of the rows carry a company or a posted date, the run log prints a WARNING.

Jobicy jobs scraper pricing: a worked cost example

You pay per job returned, on Apify's pay-per-event model, and nothing for platform usage on top: $0.006 per job on the Free and Bronze plans, $0.003 on Silver, $0.002 on Gold, Platinum and Diamond. Rows dropped by your filters are never billed, and a run that returns nothing costs nothing.

RunJobs returnedFree / BronzeSilverGold and above
A full run: the 100 jobs Jobicy serves at most100$0.60$0.30$0.20
The same run with salaryOnly: true (roughly a third carry pay)33$0.20$0.10$0.07
A run whose filters match nothing0$0.00$0.00$0.00

maxItems is the hard ceiling: maxItems: 200 can never cost more than $1.20 on the Free plan. Apify's free plan includes a monthly usage credit, so a first run costs nothing out of pocket.

Use cases for Jobicy job data

  • Salary benchmarking and compensation data. This is the board to use for it. salaryMin, salaryMax, salaryCurrency and salaryPeriod are numbers, not strings, and minSalary annualises before comparing.
  • Pay-range research. Because the salary coverage here is denser than the other boards in this pipeline, it is the most useful single source for remote pay ranges by role and seniority.
  • Filtering out expired and stale job postings. ghostRisk, ghostReason and freshness say which listings are probably no longer open, so you can drop them before anyone wastes an application.
  • Job market and hiring data. Run it on a schedule and track how hiring, salary ranges, seniority mix and regions move over time.
  • Building a job board, job feed or job alerts. id is stable across runs, so diffing today's dataset against yesterday's gives you genuinely new jobs rather than a board reshuffle.
  • Recruitment and talent research. Company, title, tags, seniority, employment type and normalised regions on every row.

Export as JSON, CSV or Excel, or read the dataset straight from the Apify API.

How this Jobicy scraper fetches jobs

Jobicy publishes a public, documented, unauthenticated JSON feed and this Actor reads it — paced, budgeted, with an honest user agent. No HTML scraping, no bot-check evasion, no personal data. Job adverts only.

How to scrape Jobicy jobs with this Actor

  1. Open the Actor and press Start. With no input it returns the jobs Jobicy currently serves, at most 100 per run, best-first.
  2. Narrow it when you need to: search terms, hiring regions, seniority, a minimum salary, a maximum ghost-job risk, and maxItems as a hard cost ceiling.
  3. Export the dataset as JSON, CSV or Excel, read it through the Apify API, or schedule the run and attach a webhook or an integration (Google Sheets, Make, Zapier, Slack) so new Jobicy jobs arrive on their own.

All eight share one schema, one ghost-job model and one set of filters, so a query written for this board runs unchanged against any of the others.

FAQ: scraping Jobicy jobs

Does Jobicy have an official API, and is it legal to scrape Jobicy jobs? Jobicy publishes a public, documented, unauthenticated JSON feed and this Actor reads it — paced, budgeted, with an honest user agent. No HTML scraping, no bot-check evasion, no personal data. Job adverts only.

How many Jobicy jobs can one run return? At most 100. Jobicy caps every request at 100 jobs — asking for 200 or 500 still returns 100 — so maxPagesPerSource has no effect here and a full pull is never more than 100 rows.

How often should I run this Jobicy scraper, and can I get only the new jobs? A daily schedule keeps the dataset current. id is stable across runs, so diffing today's dataset against yesterday's yields only the genuinely new Jobicy jobs, not a reshuffle; maxAgeDays set to 1 or 2 is the cheaper version of the same idea.

How do I get only fresh, still-open Jobicy jobs? Set maxGhostRisk to low and maxAgeDays to 14 or 21. Every row also carries ghostReason, the plain-language grounds for its rating, so you can apply your own rule instead.

What is a ghost job? A posting that is still published but no longer open: a filled role left up for pipeline, an evergreen "talent pool" advert, or a listing on a board that never expires anything. The ghostRisk band and freshness score flag them from what the board itself publishes — age, expiry dates, missing application links, evergreen phrasing — never from a model's guess.

Does it include salary data? Yes, and this is the board to use for it: Jobicy publishes a structured minimum, maximum, currency and period on roughly a third of listings, parsed straight into salaryMin, salaryMax, salaryCurrency and salaryPeriod. Set salaryOnly to keep only those.

Do I need proxies, a login or an API key? No. Jobicy is read the way it asks to be read, and Apify runs the Actor for you; nothing to install and no credentials to manage.

Can I export Jobicy jobs to CSV, Excel or Google Sheets? Yes. Every run's dataset downloads as JSON, CSV or Excel from the Apify Console or API, and the Google Sheets integration writes rows straight into a sheet.

Is this a remote job scraper I can run as an API? Yes. Apify runs every Actor from its API as well as the Console: start a run over HTTP with the same JSON input shown above, or put it on a schedule, then read the finished dataset as JSON, CSV or Excel. The dataset is the output; there is no separate query endpoint, so a scheduled run plus a dataset read is the API.

Can an AI agent use this Jobicy scraper? Yes, through Apify's own MCP server, which exposes Store Actors as tools to Claude and other MCP clients. Nothing here is agent-specific: the agent sends the same JSON input and reads the same dataset.

How do I drop expired job listings? Set maxGhostRisk to low or medium and they are dropped before they are returned, so you do not pay for them. Every row that is returned carries ghostRisk (low, medium or high), ghostReason (the plain-language grounds, such as "board's own expiry date passed 3 days ago" or "posted 64 days ago") and freshness (0-1, decaying on a 21-day half-life, 0 once a published expiry date has passed), so you can apply your own rule after export instead. maxAgeDays drops anything older than N days, including rows with no posted date.

What does a Jobicy job row not contain? No visa-sponsorship flag, no applicant counts, no recruiter emails or any personal data, and no company size — Jobicy does not publish them in its feed, so they are not invented here. A blank seniority means the board never said; a blank salary means unpublished, not zero.

Want more than one board?

Remote Jobs Aggregator runs this same pipeline across six boards at once — Remote OK, Remotive, Himalayas, Arbeitnow, We Work Remotely and Jobicy — folding duplicates and recording which boards carry each job.

Measured while building it: those six boards barely overlap. Only 1 of 1,513 company+title pairs appeared on more than one. The aggregator is not about removing duplication — there is almost none — it is about getting six boards' worth of distinct jobs from one call.