Freelancer Jobs Scraper

Extract public Freelancer.com project listing cards by keyword, category slug, or listing URL. Export titles, project links, visible price text, bids and skill tags to CSV, Excel or JSON using Apify datasets.

Use the results to review freelance opportunities, compare visible project summaries and track skill demand. This Actor does not open project details, collect client contacts, submit bids or log in.

Quick start

1. Choose a keyword, category slug or public Freelancer jobs URL.
2. Start with a small project and page limit.
3. Review the dataset and export the fields you need.

{
  "queries": ["web scraping"],
  "maxItems": 20,
  "maxPages": 2,
  "proxyConfiguration": { "useApifyProxy": false }
}

Provide at least one source. Source fields shown in the form are prefills, not defaults for API calls. Fewer than maxItems rows can be returned when pages contain fewer usable unique cards.

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:

• Scrape Freelancer lead generation project opportunities
• Monitor Freelancer data entry jobs by category
• Scrape Freelancer web scraping jobs for lead generation

What you get

One row per usable public project-listing card, with a source link, title and available summary, displayed price or average-bid text, skill tags and bid counts. These are listing-card observations rather than project-detail or client-contact records.

Who is it for?

• Freelancers preparing a shortlist of public opportunities for manual review.
• Agencies researching projects that match their services.
• Market researchers comparing visible project summaries and skill tags.
• Data teams organizing source-linked exports in their own reporting systems.

How you can use the data

• Prepare a web-scraping opportunity sheet. Use the existing keyword with small project and page caps. Keep title, url, descriptionSnippet, skills and visible budget text together before opening original project links for manual qualification.
• Review a Python or data-entry category sample. Use the existing category or listing-URL recipe. Inspect source URLs and returned skill tags rather than treating the capped sample as the whole category.
• Keep budget and bid signals distinct. Price text can represent average bids instead of a client budget. Review averageBid, currency context and the original card, without treating a visible verified label as an independent payment audit.
• Compare your own dated exports. Match canonical project URLs and retain scrapedAt when joining separate datasets. The projectId field is the last URL-path segment rather than a numeric platform ID, and duplicate removal does not extend across runs.

Input settings

Setting	JSON key	Behavior
Start URLs	startUrls	Public HTTPS Freelancer listing URLs, as strings or objects with url. Form prefill only.
Keyword searches	queries	Keyword phrases. May be combined with other sources. No API source default.
Category slugs	categories	Slugs such as web-scraping or data-entry. Form prefill only.
Maximum projects	maxItems	Total saved-row cap, 1–10,000. Form/schema default 20. Runtime fallback 50 if no default is applied.
Maximum pages per source	maxPages	Per-source page cap, 1–50. Form/schema default 2. Runtime fallback 3 if no default is applied.
Maximum run time	maxRunSeconds	Optional 35–270-second budget with a shutdown allowance. Deadline exhaustion can fail the run.
Proxy configuration	proxyConfiguration	Form default disables managed proxy. Use explicit {"useApifyProxy":false} for direct requests. See field help for custom and managed settings and omitted-input behavior.

Supply any one or several source fields. Empty source inputs fail validation. maxItems is shared across all sources. Earlier sources can fill it before later sources are visited.

Example inputs

Category lookup

{
  "categories": ["python"],
  "maxItems": 10,
  "maxPages": 1,
  "proxyConfiguration": { "useApifyProxy": false }
}

Known listing URL

{
  "startUrls": [{ "url": "https://www.freelancer.com/jobs/data-entry/" }],
  "maxItems": 10,
  "maxPages": 1,
  "proxyConfiguration": { "useApifyProxy": false }
}

Output data

One row represents one usable listing card. This synthetic, shape-only example illustrates the fields. It is not an observed project or a promise of field availability.

{
  "title": "Example project",
  "url": "https://www.freelancer.com/projects/python/example-project",
  "projectId": "example-project",
  "slug": "example-project",
  "category": "python",
  "descriptionSnippet": "Example listing summary",
  "budget": null,
  "currency": null,
  "bidCount": null,
  "averageBid": null,
  "timeLeft": null,
  "postedAt": null,
  "skills": ["Python"],
  "clientVerifiedPayment": false,
  "sourceUrl": "https://www.freelancer.com/jobs/python/",
  "scrapedAt": "2026-10-24T00:00:00.000Z"
}

Field	Meaning
title, url	Listing title and absolute project URL.
projectId, slug	Last URL-path segment, not a numeric Freelancer project ID.
category	Slug derived from the first skill tag, or the source category when no skill is available.
descriptionSnippet	Visible listing-card description, or null. Not a full project description.
budget	Visible card price text, or null. It can represent average bids rather than the actual project budget.
currency	Best-effort currency parsed from price text. Ambiguous symbols do not prove the underlying currency.
bidCount	Parsed visible bid count, or null.
averageBid	Card price text when an average-bid marker exists, otherwise null. Not an independently verified amount.
timeLeft	Visible time-left label, or null.
postedAt	Always null in this version. Publication dates are not extracted.
skills	Visible skill tags, or an empty array.
clientVerifiedPayment	Whether card status text contains “verified”. Not independent payment verification. False can mean no matching label was visible.
sourceUrl, scrapedAt	Page where the card was found and extraction timestamp.

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 uses a start event once when extraction starts and an item event for each saved project listing. A run can incur its start charge even when no usable projects are saved. There are no paid status or error rows.

Use the item, page and optional runtime caps to bound work. Consult the live Pricing tab for current rates and discounts.

Tips for best results

• Supply the sources you want explicitly. Form source examples are not API defaults, and empty source inputs fail validation.
• Start with one focused keyword or category and small caps. Earlier sources can fill the shared item cap before later sources are visited.
• Set connection preferences explicitly. Use the existing supported settings rather than assuming form prefill and omitted API input behave identically.
• Inspect price text and bid markers before analysis. Parsed values are not independently verified project budgets.
• Read final status and available summary warnings. Saved rows can survive partial work, but an empty dataset alone does not mean a successful no-match search.

Limits and caveats

Only public listing summaries are collected, without project-detail visits, bidder profiles, contact enrichment, login-only or private data, messages or bid submission. Optional card fields can be null, publication dates remain unpopulated and price text can represent average bids. Ambiguous currency symbols do not prove the underlying currency.

Results follow source and page order without a newest-first guarantee. The total row cap is shared across sources, and earlier sources can fill it first. Duplicate project URLs are removed within the run rather than across exports.

Completed pages without usable cards can succeed with an empty dataset. Access challenges, deadlines and essential execution or storage failures can fail a run. Some unsuccessful source requests preserve already-saved rows and add warnings to RUN_SUMMARY.

PENDING_WORK records the in-progress position, and RUN_SUMMARY reports saved counts and warnings when available. Automatic resume is not implemented. Inspect final status and diagnostics rather than treating missing output as proof of no matching projects.

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~freelancer-jobs-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "queries": [
    "web scraping"
  ],
  "maxItems": 20,
  "maxPages": 2,
  "proxyConfiguration": {
    "useApifyProxy": 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/freelancer-jobs-scraper').call({
  "queries": [
    "web scraping"
  ],
  "maxItems": 20,
  "maxPages": 2,
  "proxyConfiguration": {
    "useApifyProxy": 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/freelancer-jobs-scraper').call(run_input={'queries': ['web scraping'], 'maxItems': 20, 'maxPages': 2, 'proxyConfiguration': {'useApifyProxy': False}})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API usage notes

The cURL request starts a run asynchronously. Check its status and use its defaultDatasetId to retrieve results after completion.

MCP and AI agents

You can ask your AI assistant to collect data with Freelancer 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 Freelancer 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/freelancer-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 Freelancer Jobs Scraper by Fetch Cat, or give it the identifier fetch_cat/freelancer-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 Freelancer Jobs Scraper to collect up to 5 web-scraping project cards from at most 1 page. Show titles, listing links, snippets and displayed price text for manual opportunity review.”
• “Collect at most 5 public projects from the Python category using one page. Show available skill tags, bid counts and average-bid text without treating it as the client's verified budget.”
• “Retrieve up to 5 project cards from https://www.freelancer.com/jobs/data-entry/ with a one-page cap. Keep source URLs and collection times, then explain any partial, empty or failed outcome without resuming automatically.”

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

Is this an official Freelancer.com API?

No. It is an independent public-listing extraction tool and is not affiliated with Freelancer.com.

Why are there fewer rows than requested?

The selected pages can contain duplicates, missing titles/URLs or fewer usable listings. Review RUN_SUMMARY, run status and the selected public pages before increasing limits.

Can it send bids or messages?

No. It only saves listing-card data.

Related Actors

• Ashby Jobs Scraper — Public Ashby job listings.
• ATS Jobs Scraper for 6 ATS Sources — Listings across supported applicant-tracking sources.
• Built In Jobs Scraper — Technology-company job searches.
• Greenhouse Jobs Scraper — Public Greenhouse openings.
• Jobicy Remote Jobs Scraper — Remote-job listings.

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. ♥