Collect Freelancer.com Job Postings via API
Freelancer.com pages mix project listings, bidder activity, freelancer ratings, and skill tags.
Pulling those fields reliably usually means running headless browsers, rotating proxies, and patching anti-bot logic. This page explains how an HTTP API replaces that stack: you pass a Freelancer.com URL, the service renders the page, and you get back HTML, structured JSON, or Markdown. Below you will find the request controls, credit costs, output fields, and a short checklist for matching the API to a hiring-trends or skill-demand pipeline.
What you can collect from Freelancer.com
A single request returns the fields most hiring and market-research pipelines need. Project pages expose the project title, budget range, required skills, and bidder count. Freelancer profile pages expose rating and reviews, hourly rate, and location. The same call can return job postings, salary ranges, company reviews, and skills required without any HTML parsing on your side.
Three collection patterns cover most use cases:
- Project details — title, budget, skills, and bidder count for tracking demand and pricing.
- Freelancer ratings — rating, review count, hourly rate, and location for quality benchmarking.
- Skill data — the skill tags attached to projects and profiles for mapping demand trends.
If your downstream tool is an LLM, request Markdown instead of HTML. The page arrives as clean text ready for hiring-trends analysis or skill-mapping workflows.
Request controls and what they unlock
The API exposes a small set of controls that change how a Freelancer.com page is fetched and what comes back. Use this map to pick only the controls your pipeline needs, since each one affects credit cost.
- render_js — renders JavaScript before returning the page. Needed for pages whose content is injected client-side. Costs 5 credits per successful request.
- stealth_proxy — routes through a stealth proxy for tougher anti-bot challenges. Costs 75 credits per request.
- premium_proxy — routes through premium proxies. Costs 10 credits with JS rendering disabled, or 25 credits with JS rendering enabled.
- country_code — routes the request through a residential IP in the specified country. Useful when Freelancer.com content varies by geography.
- extract_rules — maps CSS selectors to field names and returns parsed JSON.
- ai_extract_rules — accepts a natural-language specification and returns parsed JSON.
- screenshot — captures a full-page screenshot for visual verification.
- js_scenario — simulates clicks, scrolling, and waits before the page is captured.
All prices are exclusive of VAT. Credit costs are per successful request and are drawn from the plan's monthly credit allowance.
Choosing an output format
The API can return three output shapes from the same URL. Pick based on what consumes the data next.
- HTML — best when you already have a parser and want full fidelity. You handle the extraction logic.
- Structured JSON — best when you want named fields without writing selectors. Use
extract_rulesfor CSS-based mapping orai_extract_rulesfor a natural-language spec. The response arrives as parsed JSON. - Markdown — best when the next consumer is an LLM or a text search index. Project and freelancer pages arrive as clean Markdown ready for hiring-trends or skill-mapping analysis.
A practical pattern is to prototype with JSON extraction in the dashboard request builder, confirm the field names match your schema, then move the generated snippet into your codebase.
Worked example: a skill-demand snapshot
Suppose you want a weekly snapshot of which skills appear most often in new Freelancer.com projects. A minimal pipeline looks like this:
- Collect a list of project URLs from a Freelancer.com listing page.
- For each URL, send a request with
extract_rulesmapping the project title, budget range, required skills, and bidder count to your field names. - Store the parsed JSON rows in a table keyed by project URL and collection date.
- Aggregate skill tags by week to see which skills are rising or falling.
If the listing page itself is JavaScript-heavy, add render_js to the listing request. If the project pages are behind a tougher challenge, add stealth_proxy. Keep the two controls separate so you only pay the higher credit cost where it is actually needed. The same pattern works for freelancer ratings: swap the field map to rating, review count, hourly rate, and location.
Concurrency limits versus target throttling
Two different limits can slow a Freelancer.com pipeline, and they need different responses.
- API concurrency limits are set per plan. They cap how many requests you can have in flight at once. If you hit this limit, requests queue or fail until a slot frees up. The fix is to raise your plan's concurrency or reduce parallel workers.
- Target throttling happens when Freelancer.com itself slows or blocks aggressive request patterns. The API does not impose a per-target rate limit, so this is a property of the destination site. The fix is to space out requests or use multiple sessions.
If you see failures, check which limit you hit before changing anything. Raising concurrency will not help if the target is throttling, and spacing requests will not help if your own plan's concurrency is the bottleneck.
Plans and credit costs
New accounts receive 1,000 free credits with no card required. Paid plans start at $19 per month for higher volume and concurrency. The plan table below lists every tier with its monthly credit allowance, concurrent request limit, and feature availability. All prices are exclusive of VAT.
Credit cost per request depends on the options you enable: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy. Base requests start at 1 credit each. API credits are valid for one month and do not roll over.
Setup path
The workflow is the same across languages:
- Create an account to get an API key and the 1,000 free credits.
- Install the SDK for your stack — Python, Node.js, Go, PHP, Ruby, or Java — or use plain cURL.
- Pass a Freelancer.com URL and your API key to the endpoint. The service handles rendering and bot bypass.
- Add advanced parameters only when the page needs them:
render_js,stealth_proxy,country_code, orai_extract_rules.
Working code samples exist for each supported language. Test in the dashboard request builder first, then drop the generated snippet into your codebase. Documentation and a knowledge base cover the most common use cases with code samples.
| Plan | Price | API Credits | Concurrent requests | JavaScript rendering | Rotating & Premium Proxies | Geotargeting | Screenshots & Extraction Rules | Priority Email Support | Dedicated Account Manager | Team Management |
|---|---|---|---|---|---|---|---|---|---|---|
| Hobby | $19 /mo | 75,000 | 25 | Included | Included | Included | Included | Not included | Not included | Not included |
| Freelance | $49 /mo | 250,000 | 50 | Included | Included | Included | Included | Not included | Not included | Not included |
| Startup (Recommended) | $99 /mo | 1,000,000 | 100 | Included | Included | Included | Included | Not included | Not included | Not included |
| Business | $249 /mo | 3,000,000 | 200 | Included | Included | Included | Included | Included | Included | Included |
| Business + | $599 /mo | 8,000,000 | 400 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 14 | $999 /mo | 14,000,000 | 500 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 24 | $1,599 /mo | 24,000,000 | 600 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 41 (Recommended) | $2,399 /mo | 41,000,000 | 700 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 69 | $3,599 /mo | 69,000,000 | 800 | Included | Included | Included | Included | Included | Included | Included |
| Enterprise 120 | $5,799 /mo | 120,000,000 | 900 | Included | Included | Included | Included | Included | Included | Included |
All prices are exclusive of VAT. API credits are valid for one month and do not roll over. Requests start at 1 credit each. Plan prices and credit allowances are captured reference figures; check current pricing before purchasing.
Frequently asked questions
Do I need an account to scrape Freelancer.com?
No external Freelancer.com account is required. You sign up for one API key (1,000 free credits, no card), send the URL, and the service handles rendering and bot bypass.
Can I scrape Freelancer.com from a specific country?
Yes. Pass country_code on the request to route through a residential IP in that country. This is useful when Freelancer.com content varies by geography.
What's the rate limit for scraping Freelancer.com?
The API has concurrency limits per plan, not per-target rate limits. If Freelancer.com throttles aggressive request patterns, space out requests or use multiple sessions.
How do I get structured JSON from Freelancer.com?
You have two routes to parsed JSON. With extract_rules, you pair each CSS selector with the field name it should populate. With ai_extract_rules, you describe the fields you want in plain language instead of writing selectors. Either way, the response body is already parsed JSON rather than raw HTML.
Which programming languages can I use to scrape Freelancer.com?
Any. SDKs are published for Python, Node.js, Go, PHP, Ruby, and Java. Plain cURL works too. Pick whatever your stack already uses.
How much does it cost to scrape Freelancer.com?
New accounts get 1,000 free credits with no card required. Paid plans start at $19 per month for higher volume and concurrency. Credit cost per request depends on options: 5 credits for JS rendering, 25 for premium_proxy with JS, and 75 for stealth_proxy.