Fiverr Scraper - Gigs, Reviews & Seller Profiles
Pricing
from $2.00 / 1,000 results
Fiverr Scraper - Gigs, Reviews & Seller Profiles
Collect public Fiverr gigs through keyword search, categories or gig links. Export prices, ratings, optional reviews and seller profiles, or sitemap URLs. Pay per delivered row plus a start fee.
Pricing
from $2.00 / 1,000 results
Rating
0.0
(0)
Developer
kane liu
Maintained by CommunityActor stats
0
Bookmarked
4
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Security
Limited permissionsShare
Fiverr Scraper
Extract Fiverr gig listings, gig details, optional seller profiles and reviews, or sitemap URLs as rows you can export.
- Search across Fiverr, not just Programming & Tech.
- Select categories, listing paths or individual gig URLs.
- Compare gig prices, ratings and seller information.
- Keep reviews and seller profiles as separate rows.
- Pay $2 per 1,000 delivered rows on every Apify plan, plus a start fee.
What does Fiverr Scraper do?
Fiverr Scraper collects public marketplace data from fiverr.com. Use it to compare services, research categories or build a list of gig URLs. A listing row contains card-level information; a gig-detail row can also contain descriptions and packages.
- Search:
searchQueryreturns gigs matching one keyword or phrase. - Categories and listing paths:
categoriesandsubcategoriesselect areas such asgraphics-design,online-marketing,programming-tech,writing-translation,video-animation,music-audio,business,lifestyle,dataandphotography. - Gig details:
gigPathsselects individual gigs. - Sitemap inventory:
sitemapreturns URLs, not full page details. - Optional rows:
includeReviewsadds review rows for gig details;sellerLimitenables seller profiles after search or category collection. Both are off by default. Each additional row is billed at the same price as a gig row and uses the remaining row allowance.
What data can you extract from Fiverr?
Every row has id, rowType, record_type, source_url and crawled_at. Available fields depend on the selected collection type and what Fiverr shows.
Gig rows: rowType=gig
| Field | Description | Example |
|---|---|---|
record_type | Listing card or full gig detail | gig_listing |
title | Gig title | I will design a minimalist logo |
gig_id | Fiverr gig identifier | 123456789 |
seller_username | Seller handle | example_seller |
seller_level | Seller level shown by Fiverr | level_two_seller |
price | Listed price or first detail-package price | 50 |
currency | Currency when supplied | USD |
delivery_days | Listed delivery time | 3 |
rating | Gig rating, not the seller's overall rating | 4.9 |
reviews_count | Gig review count | 120 |
seller_rating | Seller's overall rating, separately | 4.8 |
listing_path | Category and listing context | graphics-design/logo-design |
sourceSearchQuery | Search phrase for search rows | logo design |
searchRank | Position in collected search results | 1 |
description_html | Description on detail rows | <p>Logo design service</p> |
packages | Package options on detail rows | [] |
Seller rows: rowType=seller
These have record_type=seller_profile and share the gig rows' seller identifiers, rating and source-link fields.
| Field | Description | Example |
|---|---|---|
seller_display_name | Public display name | Jane Doe |
seller_country | Country shown on the profile | United Kingdom |
skills | Listed skills | ["Logo design"] |
description | Public profile biography | Brand identity designer |
hourly_rate_cents | Hourly rate in cents, when present | 5000 |
Review rows: rowType=review
These have record_type=review; gig_id links each review to its gig.
| Field | Description | Example |
|---|---|---|
comment | Review text | Clear communication and delivery. |
value | Review score | 5 |
reviewer_country | Reviewer's displayed country | Canada |
created_at | Source review date or timestamp | 2026-10-01 |
seller_response | Seller response when present | null |
Inventory rows: rowType=inventory
The record_type is sitemap_gig, sitemap_seller, sitemap_category, sitemap_tag or sitemap_logomaker. Titles are null because these rows describe URLs.
| Field | Description | Example |
|---|---|---|
source_url | Canonical URL | https://www.fiverr.com/example_seller/example-gig |
gig_path | Path on gig inventory rows | example_seller/example-gig |
inventory_source | Sitemap group | sitemap_gigs |
lastmod | Published modification timestamp, or empty string | 2026-10-01 |
How to scrape Fiverr
- Open Fiverr Scraper in Apify Console.
- Fill one target field, such as
searchQuery. Clear the example keyword when selecting another collection type. - Set
maxItemsto3for a small first run. - Click Start and wait for completion.
- Open the dataset and download your rows.
Empty input starts an example search for logo design, limited to 3 rows. This is a normal billable run, not a free preview. Filling a target field selects the collection type automatically; there is no mode selector.
Search
Enter one phrase in searchQuery. Search is site-wide; category fields do not filter it. Use maxPages and startPage for pagination within the row allowance.
Categories and listing paths
Enter top-level slugs in categories, or specific paths in subcategories. Display names such as Graphics & Design work; digital-marketing maps to online-marketing. Known leaf names such as website-development resolve to listing paths. A category can expand into many paths; select specific paths and set a cost limit for small runs. When both category fields are supplied, the categories filter the selected paths.
Gig details
Paste Fiverr gig URLs or seller/gig-slug paths into gigPaths. Enable includeReviews for separate review rows. Reviews use the same allowance as gigs, so a limit of 1 leaves no room for reviews.
Sitemap inventory
Choose gigs, users, categories, tags, logomaker or all in sitemap. Set a small inventoryLimit. This returns URL inventory without fetching each page's details.
If different target types are filled together, priority is sitemap, then gigPaths, then searchQuery, then category/listing selection. Use one target type to avoid ambiguity.
What to fill in
| Field | What to enter | Default |
|---|---|---|
searchQuery | One search phrase, up to 200 characters | Empty; example logo design |
gigPaths | Array of gig URLs or paths | Empty |
categories | Array of top-level category names or slugs | Empty |
subcategories | Array of listing paths or known leaves | Selected categories' paths |
maxItems | Row limit per query, listing path or gig URL; 1–5,000 recommended | 70; form prefill 3 |
includeReviews | Include separate gig-detail review rows | false |
sellerLimit | Maximum seller profiles after search/listings, 0–200 | 0 |
sellerFailureLimit | Stop seller collection after this many failures, 1–50 | 5 |
phase2BudgetSeconds | Seller collection time allowance, 30–900 seconds | 240 |
sitemap | One of the inventory groups listed above | Empty |
inventoryLimit | Additional inventory cap, 0–5,000; 0 adds no separate cap | 0 |
sitemapSinceTs | Keep entries newer than an ISO date or timestamp; undated entries are kept | Empty |
sitemapShardState | Previous RUN_SUMMARY.diagnostics.sitemapShardState to skip unchanged sitemap files | {} |
maxPages | Maximum pages per search/listing, 1–20 | 1 |
startPage | First search/listing page, 1–20 | 1 |
Search:
{"searchQuery": "logo design", "maxItems": 3}
Category selection:
{"categories": ["graphics-design"], "maxItems": 3}
Listing-path selection:
{"subcategories": ["graphics-design/logo-design"], "maxItems": 3}
Gig details with reviews; replace the placeholder with a current gig path:
{"gigPaths": ["example_seller/example-gig"], "includeReviews": true, "maxItems": 5}
Inventory:
{"sitemap": "gigs", "inventoryLimit": 3, "maxItems": 3}
maxResults, limit and max_results are aliases for maxItems. Search aliases include query, keyword, keywords, search and q; gigUrls and urls map to gigPaths, listingPaths to subcategories, and category to categories.
Unknown fields do not fail the run: close misspellings are corrected, and other unknown fields are ignored with a note. Normal collection runs write these decisions to INPUT_REPORT in the default key-value store. INPUT_ECHO shows the parsed selection.
Input-resolution errors use INVALID_INPUT: <field> — <how to fix>. Further validation, such as an invalid gig URL or category, can instead return a field-specific message without that prefix. Validation happens before rows are delivered or charged; the start fee still applies. Check ERROR_SUMMARY for failures and RUN_SUMMARY for counts and warnings.
Output example
Illustrative listing row with placeholder seller data:
{"id": "123456789","rowType": "gig","record_type": "gig_listing","gig_id": "123456789","title": "I will design a minimalist logo","seller_username": "example_seller","price": 50,"currency": "USD","rating": 4.9,"reviews_count": 120,"sourceSearchQuery": "logo design","searchRank": 1,"source_url": "https://www.fiverr.com/example_seller/example-gig","source": "fiverr","platform": "fiverr","attribution_url": "https://www.fiverr.com","crawled_at": "2026-10-24T00:00:00Z","raw": {}}
Export the dataset as JSON, CSV, Excel, XML, RSS or an HTML table. Use JSON when you need arrays such as packages or skills intact.
Why use this Fiverr scraper?
- Pay per delivered row: unsuccessful page attempts are not result rows.
- Keep delivered data: rows already written remain in the dataset if a run stops. Available partial results can be delivered; a forced stop before delivery is not a guarantee of saved data.
- Separate ratings: gig ratings and seller ratings are distinct fields.
- No invented contacts: unavailable values stay empty, with contact-field explanations in
leadAbsences. - Several inputs per run: provide multiple gig paths or listing paths;
searchQueryremains one phrase. - No proxy setup: you do not need to set up proxies.
How much does it cost to scrape Fiverr?
Pricing is pay-per-event. The start event costs $0.005 per GB of allocated memory, with at least one event. At the default 512 MB, the start charge is $0.005. Platform usage is included in these prices.
| Apify plan | Start at 512 MB | Price per row | Price per 1,000 rows |
|---|---|---|---|
| Free | $0.005 | $0.002 | $2.00 |
| Starter | $0.005 | $0.002 | $2.00 |
| Scale | $0.005 | $0.002 | $2.00 |
| Business | $0.005 | $0.002 | $2.00 |
maxItemsapplies to each input, defaults to 70, and larger requests are collected in parts of 70. It is a ceiling, not a promise of that many rows.- Gig, review, seller and inventory rows all count toward the allowance at the same price.
- Free Apify plan users have a developer-set limit of 200 rows per run and 10 runs of this Actor. Paid plans remove the 10-run limit.
- The whole run is bounded by Maximum cost per run (
maxTotalChargeUsdin the API run options, not the input). maxItems=0uses the legacy 5,000-row safety cap, not unlimited collection. In detail/inventory collection, a positiveinventoryLimitcan supply that cap instead.
Example: one search delivering 3 rows at 512 MB costs $0.005 + 3 × $0.002 = $0.011 on the Free plan. Optional rows replace part of the allowance; they are not free extras.
What happens when the run timeout is too short
If collection needs longer than the timeout allows, the run can pause and show ABORTED with “Queued on the collection backend; this run will resume automatically when results are ready (about Ns).” Here, N is the estimated number of seconds.
When results are ready, the same run resumes, delivers rows to the same dataset and finishes as SUCCEEDED if collection succeeds. When continuing an existing delivery, it reports “Resumed: delivering N rows.” Already delivered rows are skipped, not delivered or charged twice.
This pause/resume process is limited to 3 attempts. Keep the default timeout of 3,600 seconds to reduce interruptions. Real collection failures can still fail the run.
The synchronous endpoints run-sync and run-sync-get-dataset-items wait at most 300 seconds and can return an empty dataset while the run is paused. For longer requests, start asynchronously and read the dataset after SUCCEEDED, or use an ACTOR.RUN.SUCCEEDED webhook.
Use with AI agents and the API
Apify MCP server
Add this remote tool server to Claude, ChatGPT, Cursor, VS Code or another compatible MCP client:
https://mcp.apify.com?tools=lentic_clockss/fiverr-programming-tech-gigs-scraper
Sign in with Apify through OAuth, or send Authorization: Bearer <YOUR_APIFY_TOKEN>. The tool starts a run and returns run and dataset IDs; read the rows with get-dataset-items.
Clients without remote-server support can use npx @apify/actors-mcp-server --tools lentic_clockss/fiverr-programming-tech-gigs-scraper with APIFY_TOKEN set.
Example prompt: “Find 3 Fiverr gigs for logo design and return their titles, prices, ratings and URLs.”
Apify API
Python:
from apify_client import ApifyClientclient = ApifyClient("<YOUR_APIFY_TOKEN>")run = client.actor("lentic_clockss/fiverr-programming-tech-gigs-scraper").call(run_input={"searchQuery": "logo design", "maxItems": 3})for row in client.dataset(run["defaultDatasetId"]).iterate_items():print(row)
JavaScript:
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });const run = await client.actor('lentic_clockss/fiverr-programming-tech-gigs-scraper').call({ searchQuery: 'logo design', maxItems: 3 });const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items);
For asynchronous HTTP calls, send the input JSON to POST https://api.apify.com/v2/acts/lentic_clockss~fiverr-programming-tech-gigs-scraper/runs with your token in the Authorization: Bearer header. After success, read GET https://api.apify.com/v2/datasets/<datasetId>/items?format=json.
Standby HTTP endpoint
Base URL: https://lentic-clockss--fiverr-programming-tech-gigs-scraper.apify.actor.
| Route | Purpose |
|---|---|
GET / | Readiness |
GET /health | Service status |
GET /input-example | Example input |
GET /openapi.json | OpenAPI document |
These are read-only routes. POST /search appears in the OpenAPI document but is not available in this version. Start a normal Actor run through the Apify API to collect and save rows.
Integrations
Use the Integrations tab to connect results to Google Sheets, Make, Zapier, n8n, Slack, Airtable or a webhook. Use Apify Schedules for recurring runs.
FAQ
Is it legal to scrape Fiverr?
This Actor collects public data. You are responsible for checking Fiverr's terms and applicable data-protection law. Public availability does not remove those obligations; processing personal data requires a lawful basis.
Why did my run end as ABORTED?
It may be the automatic pause described above. Check the status message before restarting: a queued run can resume itself. A manual abort or unrelated failure is not the same condition.
How many results can I get?
Set maxItems per input, up to 5,000. Available results, pagination, optional rows, the 200-row Free-plan cap and your cost limit can reduce delivery.
Why are some fields empty?
Listing cards expose less than detail pages. Seller-only fields need a seller row. Inventory titles are intentionally empty. Missing gig ratings are not replaced with seller ratings.
Is this limited to Programming & Tech?
No. The Actor's identifier retains that name, but search and category selection cover other Fiverr marketplace categories too.
Why did I receive no seller rows?
sellerLimit defaults to 0. Raising it permits profiles after search/category gigs, but only while row allowance remains. If gigs fill the allowance, no seller profiles are collected.
Can I collect seller phone numbers or emails?
This Actor does not supply private contacts. Its contact mapping leaves phones and emails empty; address information is at most country-level. It does not submit messages or contact requests.
Limitations
- Category paths and public pages can change. Complete marketplace coverage is not guaranteed.
- No country or language selector is provided; search words are not automatically translated.
- Reviews are limited to those returned with gig details, not a complete review-history export.
- Sitemap rows identify URLs, not availability, current prices or full profiles. Incremental inventory keeps entries with no modification date.
- Seller collection can stop at its time or failure limit. A fresh collection with no valid rows is reported as a failure, not a successful empty dataset.
Related scrapers
More job board and freelance marketplace scrapers from the same publisher:
- LinkedIn Scraper
- Indeed Scraper
- Upwork Scraper
- Freelancer.com Scraper
- Glassdoor Scraper
- SEEK Scraper
- Bayt Scraper
Browse all of our scrapers at apify.com/lentic_clockss.
Support
Report a problem or request a field through the Issues tab of this Actor's page. Include the run ID and the input you used.