# Fiverr Gig Scraper - Price, Level & Delivery (`usestring/fiverr-gigs`) Actor

Scrape Fiverr gig search results for any keyword. Every gig comes back with its title and URL, the starting price as a number in USD, star rating and review count, the seller's name and level badge, the delivery time in days and the cover image. 48 gigs per search term, one request each.

- **URL**: https://apify.com/usestring/fiverr-gigs.md
- **Developed by:** [String](https://apify.com/usestring) (community)
- **Categories:** Business, E-commerce, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.75 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Fiverr Gig Scraper — exact USD price, seller level and delivery time

This Actor scrapes Fiverr gig search results. Give it a search term such as `logo design` and the
Fiverr Gig Scraper returns **48 gigs** with the **exact starting price as a number in USD**, the
seller's level badge, the delivery time in days, and the rating with its review count — not the
rounded strings the page displays.

No Fiverr account, login or cookies are used — this reads what a logged-out visitor sees. **48 gigs
per search term, one Fiverr request each**.

### What it returns

| Field | Type | Notes |
| --- | --- | --- |
| `gigId` | string | Fiverr's own gig ID — stable across runs, use it to de-duplicate |
| `title` | string | The gig title |
| `startingPrice` | number | `20`, not `"$20"` — the gig's base package price |
| `currency` | string | Always `USD`; see the note below |
| `rating` | number | Stars out of 5, e.g. `4.9`. Empty when the gig has no reviews |
| `reviewCount` | number | `16482`, not `"16k"` |
| `sellerName` | string | The seller's Fiverr username |
| `sellerLevel` | string | `Top Rated`, `Level 2`, `Level 1`, or empty for an unranked seller |
| `deliveryDays` | number | Delivery time of the recommended package, in days |
| `imageUrl` | string | The gig's cover image |
| `gigUrl` | string | Absolute link to the gig on Fiverr |
| `searchTerm`, `sourceUrl`, `collectedAt` | string | Provenance for every row |

`startingPrice` is Fiverr's own base USD amount, which is the same number wherever the request exits
from. Fiverr ships a separate display currency and conversion rate that the page applies in the
browser; reporting that instead would misstate every non-US run by the conversion rate, so it is not
used.

### Input

```json
{ "searches": ["logo design", "video editing"], "maxItems": 1000 }
```

| Field | Description |
| --- | --- |
| `searches` | Search terms, e.g. `"logo design"`. Required, 1–50. |
| `maxItems` | Cap on dataset items. Default 1000. Free plans stop at 250 requests and 250 results — see below. |
| `concurrency` | Search terms fetched in parallel. Default 5, maximum 10. |

One request per search term, so a run's request count equals the number of unique terms you supply.
Ten terms return roughly 480 gigs for ten requests.

### Use cases

- Freelance market pricing research — what a category actually starts at, in numbers
- Benchmarking your own gig against the first page competitors for a keyword
- Sourcing freelancers filtered on `sellerLevel`, `rating` and `deliveryDays`
- Tracking how starting prices and delivery times move for a keyword over time
- Feeding a category dashboard on a schedule, keyed on `gigId`

### Reliability

Gigs are read from the JSON payload Fiverr ships inside the search page rather than from the rendered
cards, so `startingPrice`, `rating`, `reviewCount` and `deliveryDays` are exact values instead of the
formatted strings the DOM shows (`"$20"`, `"4.9 (16k)"`). A gig with no reviews reports a zero
rating on Fiverr, which is an absence of scoring rather than a bad score, so `rating` comes back
empty and `reviewCount` is `0`.

Fiverr answers a declined request with an anti-bot interstitial rather than an error status. That is
detected and recorded in the run's `SUMMARY` under `failures` for that search term instead of being
written out as an empty success, and a run where every term failed exits with an error.

There are no retries by design: the String Unblocker owns proxy rotation and anti-bot solver
selection, so a retry loop here would only re-roll the same block.

### Frequently asked questions

**How do I scrape Fiverr gigs?** Run the Fiverr Gig Scraper with one or more search terms, then
export the dataset as CSV, JSON or Excel. Every row carries the gig ID, title, starting price, seller
name, seller level, rating, review count and delivery days.

**How many Fiverr gigs does it return per search term?** 48 — one Fiverr search request per term.
Ten terms therefore return roughly 480 rows.

**Does it page through all the gigs for a keyword?** No. The Fiverr Gig Scraper reads the first page
of search results per term, so 48 gigs per term is what a run returns. Use narrower or additional
search terms to cover more of a category.

**Do I need a Fiverr account, API key or cookies?** No. Only public, logged-out search results are
read.

**Is the price in my own currency?** No — `startingPrice` is always Fiverr's base USD amount and
`currency` is always `USD`, so prices are comparable across runs regardless of where the request
exits from.

**Can I scrape an individual gig or seller profile?** No. This Actor reads search results only; it
does not open gig detail pages, seller profiles, packages beyond the recommended one, or reviews.

### Limitations

One page of search results per term, and search terms are the only input — there is no category,
price, delivery-time or seller-level filter. Gig detail pages, seller profiles, review text and the
full package ladder are out of scope: `startingPrice` is the gig's base price and `deliveryDays` is
the recommended package's delivery time, with no other package returned.

### Free plan limit

Runs started from an Apify **free plan** stop at **250 requests and 250 results**, and the run
reports that it reached the limit. Any paid plan runs the full input and `maxItems` you set.

The limit exists because this Actor fetches through our own infrastructure, which Apify does not
cover for free-plan runs. It binds on requests as well as results so that a large input list cannot
spend those fetches for rows the run will not return.

# Actor input Schema

## `searches` (type: `array`):

What to search Fiverr for.

## `maxItems` (type: `integer`):

Global cap on dataset items. Runs started from an Apify free plan stop at 250 requests and 250 results; any paid plan runs the full amount.

## `concurrency` (type: `integer`):

Targets fetched in parallel.

## Actor input object example

```json
{
  "searches": [
    "logo design"
  ],
  "maxItems": 1000,
  "concurrency": 5
}
```

# Actor output Schema

## `results` (type: `string`):

Collect 48 Fiverr gigs per search term - exact USD starting price, rating, seller level and delivery days.

## `summary` (type: `string`):

Item count, failure count and every target that failed, with its error.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searches": [
        "logo design"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("usestring/fiverr-gigs").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "searches": ["logo design"] }

# Run the Actor and wait for it to finish
run = client.actor("usestring/fiverr-gigs").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searches": [
    "logo design"
  ]
}' |
apify call usestring/fiverr-gigs --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,usestring/fiverr-gigs"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/rcybceNIYI2h4L38G/builds/2GfpuowTF1i9fBoT5/openapi.json