Freelancer.com Jobs and Projects Scraper

how to get the data with our Apify actor freelancer-jobs-projects-scraper

Scrape Freelancer.com job listings by skill: project title, description, average bid and whether it is hourly, bid count, required skills, payment verification status, and project URL.

open freelancer-jobs-projects-scraper on Apify →

on apify: v0iddo/freelancer-jobs-projects-scraper
category: jobs, automation
build: 0.1.2, built 2026-11-07
billing: Apify bills it per result; the price for your plan is on the actor's page.

What you get

Every result is one row in the run's dataset. Download it as JSON, CSV, Excel or HTML, or read it through the Apify API.

The main fields of each row:

title
description
Average Bid (avgBid)
hourly
currency
Bid Count (bidCount)
skills
Payment Verified (paymentVerified)
Days Left (daysLeft)
Project URL (url)

What people use it for

Contractor lead lists: find open projects for a skill, with the average bid, currency and days left to bid.
Competition checks: read the bid count of each project to pick the ones that still have few bidders.
Client vetting: see which projects come from clients with a verified payment method, with description and skills.
Bid pricing: compare the average bid of fixed price and hourly projects for skills such as python or data-entry.

Run it on Apify

Open freelancer-jobs-projects-scraper on Apify and sign in, or make an Apify account.
On the Input tab, fill in the fields listed below. The form opens with example values filled in.
Click Start. Rows appear on the Output tab while the run works.
Export the rows as JSON, CSV, Excel, XML or HTML, or read them through the Apify API.
To run it again on a schedule, save the input as a task and add a schedule in the Apify Console.

What you can set

Skill slugs (skills): One or more skill slugs as they appear in the Freelancer.com URL path, e.g. python, web-scraping, data-entry. Leave empty to browse all job categories.
Pages per skill (maxPages): Number of listing pages to read per skill (about 50 projects each). Default: 2.
Maximum results (maxItems): The run stops after this many result rows. It also caps what one run can cost. Default: 100.
Proxy configuration (proxyConfiguration): Leave as is: the run starts on the cheapest network the site accepts and switches to Apify Proxy automatically when the site blocks it. Pick proxy groups here only to force one specific network.

Example input

This is the input the actor is tested with every day.

example inputjson

{
  "skills": [
    "python"
  ],
  "maxPages": 1,
  "maxItems": 20
}

Run it from Python

The official apify-client package starts the run, waits for it and reads the rows. It needs your own Apify API token.

needs your own Apify tokenpython

# pip install apify-client
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")  # your own API token, from the Apify Console
run_input = {
    "skills": ["python"],
    "maxPages": 1,
    "maxItems": 20,
}
run = client.actor("v0iddo/freelancer-jobs-projects-scraper").call(run_input=run_input)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

Limits

Each listing page shows approximately 50 projects. Pagination is capped at 20 pages per skill to prevent runaway fetches.
Skill slugs must match the Freelancer.com URL format exactly, e.g. web-scraping not Web Scraping. Find slugs in URLs such as freelancer.com/jobs/web-scraping/.
The listing page shows the average bid of each project, not the client's budget: avgBid is that average (per hour when hourly is true). A contest shows its prize instead (prize, with entries as the bid count). The budget range is on the project page only.
Not affiliated with Freelancer.com or Freelancer International Pty Ltd.
Only publicly visible data is collected. No login, no paywalled content, no personal contact details.
The actor reads only pages that the site's robots.txt leaves open to automated access.
Sites change their pages from time to time. The actor is checked automatically and repaired when a check fails.
Each run sends one short usage record to the developer: the Actor and run IDs, the number of results, whether the run succeeded (and if not, the kind of error, such as "blocked" or "input problem"), whether the account is on a paid Apify plan, how the run was started (for example from the Console, the API or a schedule) and a one-way fingerprint of the account (a hash, not the account ID), so that repeat runs of one account count once. It contains nothing from your input or results.

Questions

Do I need an account on Freelancer, cookies or an API key?

No. The actor reads only what every visitor of Freelancer can see, without logging in. You only need an Apify account to start it.

How many results can one run return?

Up to 5,000 rows per run. Without a limit it stops at 100. Set Maximum results to the number you need; large jobs can also be split into several runs or scheduled.

Why did my run return no results?

The status message of the run says why: nothing matched the input, the input was not a page the actor understands, the page is closed to automated access by robots.txt, or the site refused every network the actor tried. Check the input against the example above and run it again with a small limit.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.