Jobicy Jobs Scraper - Best Remote Salary Data avatar

Jobicy Jobs Scraper - Best Remote Salary Data

Pricing

from $2.00 / 1,000 job returneds

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

Jobicy Jobs Scraper - Best Remote Salary Data

Scrape Jobicy remote jobs into a clean JSON or CSV job dataset. The best structured salary data of any board here - min, max, currency and period - which makes it the one to use for compensation data and salary benchmarking. Plus regions, seniority and ghost-job scoring.

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

17 hours ago

Last modified

Share

Jobicy Jobs Scraper

Scrape Jobicy remote jobs into a clean JSON or CSV job dataset. The best structured salary data of any board here - min, max, currency and period - which makes it the one to use for compensation data and salary benchmarking. Plus regions, seniority and ghost-job scoring.

Why this board is worth scraping for salary

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.


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

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

{
"query": ["golang", "backend"],
"regions": ["usa"],
"seniority": ["senior", "lead"],
"maxAgeDays": 21,
"maxGhostRisk": "low",
"maxItems": 200
}

Everything is optional — run it empty and you get the whole board, 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.

Output

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.

Common uses

  • 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 it fetches

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 every job Jobicy currently lists, 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.

How much does it cost to scrape Jobicy?

You pay per job returned, on Apify's pay-per-event model: $0.006 per job on the Free and Bronze plans, $0.003 on Silver, $0.002 on Gold and above, with no platform usage charged on top. A run that returns nothing costs nothing. Jobicy serves at most 100 jobs per run, so a full pull is at most $0.60. Set maxItems to cap a run: 200 jobs cost at most $1.20, and Apify's free plan includes a monthly usage credit, so a first run costs nothing out of pocket.

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

Does Jobicy have an official API, and is it allowed to scrape it? 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 often does Jobicy post new jobs, and how often should I run this? New listings appear every day. A daily schedule keeps the dataset current, and because id is stable across runs, diffing today's dataset against yesterday's yields only the genuinely new Jobicy jobs, not a reshuffle.

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 salaries? 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.

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.