# Etsy Products Scraper — robots-allowed, no CAPTCHA (`diopside/etsy-products`) Actor

Drop-in compatible with crawlerbros/etsy-scraper — cheaper and reliable. Etsy keyword results as JSON: listing id, title, price, sale price, discount, rating, reviews, image, shop id, ad flag, position. Reads only the routes Etsy's own robots.txt allows, never the search URLs it disallows.

- **URL**: https://apify.com/diopside/etsy-products.md
- **Developed by:** [DIOPSIDE AI](https://apify.com/diopside) (community)
- **Categories:** E-commerce, Other, Agents
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 etsy listings

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Etsy Products Scraper

**Drop-in compatible with `crawlerbros/etsy-scraper` — cheaper, and it only touches the Etsy routes
Etsy's own `robots.txt` allows.** Give it keywords, get back Etsy product listings as JSON: listing
id, title, price, sale price, discount, rating, review count, image, shop id, sponsored flag,
position and page. No login, no CAPTCHA solver, no browser.

### Why this one

**1. It uses the surface Etsy sanctions.** Etsy's `robots.txt` disallows the keyword search path
outright for every user agent:

```
Disallow: /search?*q=
Disallow: /search/?*q=
Disallow: /*?order=*      Disallow: /*min=*      Disallow: /*max=*
```

and in the same file explicitly **allows** the two routes this actor reads:

```
Allow: /api/v3/ajax/bespoke/public/neu/specs/
Allow: /api/v3/ajax/bespoke/member/neu/specs/
```

`/market/<keyword>` — Etsy's own keyword results page — carries no `Disallow` rule at all. This
actor fetches `/market/<keyword>` and replays Etsy's own `market_async_listings` call to load the
rest of the grid. It paginates with `?page=N` and nothing else, so it never constructs a URL
`robots.txt` forbids. That is also why there is no `sort` or price-filter input: every one of those
query parameters is on Etsy's disallow list.

**2. The proxy requirement is measured, not guessed.** Etsy is behind DataDome. We probed it on the
platform, 2 attempts × 6 surfaces per IP tier:

| Surface | No proxy (Apify IP) | Apify datacenter US | Apify RESIDENTIAL US |
|---|---|---|---|
| `/` (homepage) | 200 | 200 | 200 |
| **`/market/<keyword>`** | 403 DataDome | 403 DataDome | **200 OK** |
| `/search?q=` | 403 DataDome | 403 DataDome | 403 DataDome |
| `/c/<category>` | 403 DataDome | 403 DataDome | 403 DataDome |
| `/shop/<name>` | 403 DataDome | 403 DataDome | 403 DataDome |
| `/listing/<id>` | 403 DataDome | 403 DataDome | 403 DataDome |

Residential is the entry fee, not an escalation, so it is the default here and the actor says so up
front instead of failing halfway through your run. TLS fingerprint matters on top of the IP: plain
`curl`/`httpx` are challenged even on the homepage, so every request goes out with a real Chrome
fingerprint.

**3. ~48 listings per page request.** A market page server-renders only ~8 cards and defers the rest
to an async call. This actor makes that call, so one page request yields ~48 records instead of 8.

**4. Sponsored listings are flagged from Etsy's own ad list**, not guessed from the card label, so
`isAd` is right even when Etsy drops the visible "Ad from Etsy seller" text.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `searchQueries` | string\[] | — | Keywords to look up, e.g. `["leather wallet"]`. Same name as `crawlerbros/etsy-scraper`. |
| `startUrls` | URL\[] | — | Etsy market / search / category URLs. The keyword is read out and fetched from `/market/`. |
| `maxItems` | integer | 100 | Max listings per keyword. `0` = everything Etsy will paginate through. |
| `maxPages` | integer | 25 | Max market pages per keyword (~48 listings each). |
| `includeAds` | boolean | `true` | Keep Etsy's promoted listings (flagged with `isAd`) or drop them. |
| `dedupeAcrossQueries` | boolean | `true` | Return each listing id at most once for the whole run. You are billed per pushed listing, so this also stops overlapping keywords billing twice. |
| `country` | string | `US` | Residential exit country. |
| `proxyConfiguration` | object | RESIDENTIAL / US | See the table above — anything else returns nothing. |
| `queries`, `maxResults` | | | Aliases accepted for `yumitori/etsy-listings-scraper` inputs. |
| `includeDetails` | boolean | `false` | Accepted for compatibility, **no effect** — see Limits. |

```json
{
  "searchQueries": ["leather wallet", "ceramic mug"],
  "maxItems": 120,
  "maxPages": 3,
  "includeAds": false
}
```

### Output

```json
{
  "listingId": "733018869",
  "shopId": "20986259",
  "url": "https://www.etsy.com/listing/733018869/slim-leather-wallet-date-night",
  "title": "Slim Leather Wallet, DATE NIGHT, Personalized Bifold Wallet, Handmade Wallet for Men",
  "price": "16.33",
  "originalPrice": "49.49",
  "currency": "$",
  "discountPercent": "67",
  "imageUrl": "https://i.etsystatic.com/20986259/r/il/efbe9e/1992954590/il_300x300.1992954590_gjtc.jpg",
  "shopName": "LifetimeLeatherCo",
  "shopUrl": "https://www.etsy.com/shop/LifetimeLeatherCo",
  "rating": "4.87",
  "reviewCount": 15200,
  "badges": {
    "starSeller": false,
    "freeShipping": true,
    "bestseller": false,
    "etsyChoice": false,
    "ad": false
  },
  "scrapedAt": "2026-09-20T05:47:27+00:00",

  "isAd": false,
  "priceValue": 16.33,
  "originalPriceValue": 49.49,
  "onSale": true,
  "searchQuery": "leather wallet",
  "page": 1,
  "position": 5,
  "marketUrl": "https://www.etsy.com/market/leather_wallet",
  "totalResults": 279429
}
```

Every field above the blank line has the same name and shape as `crawlerbros/etsy-scraper`. The
fields below it are additions — your existing code ignores them.

### Sizes and cost

Measured on the platform, residential US:

| Run | Records | Pages | Time | Platform cost |
|---|---|---|---|---|
| 1 keyword, 1 page | 40 | 1 | 12 s | $0.0030 |
| 2 keywords, 3 pages each | 222 | 6 | 31 s | $0.0105 |

Billing is $0.00005 per run start + **$0.0015 per listing**. A 100-listing run costs $0.15;
the same run on `crawlerbros/etsy-scraper` ($0.01 start + $0.002/result) costs $0.21, and on
`yumitori/etsy-listings-scraper` ($0.008/listing) $0.80.

### Limits — what this actor does *not* do

Stated up front so you can tell before you spend anything:

- **No product-detail fields.** No description, materials, variations, tags, stock or shipping
  estimate. Etsy's `/listing/<id>` pages are 403 DataDome on every IP tier we measured, residential
  included. `includeDetails` is accepted so `crawlerbros` inputs run unchanged, but it logs a
  warning and changes nothing.
- **No shop-page or category-page mode.** `/shop/<name>` and `/c/<category>` are 403 on every tier
  too. Category URLs in `startUrls` are converted to their keyword and run through `/market/`.
- **`shopName` / `shopUrl` are partial** (~7 per page). Etsy's grid cards carry only the numeric
  `shopId`; the shop *name* appears solely in the page's structured data, which covers the handful
  of server-rendered listings. `shopId` is on every record.
- **No sort or price filters.** Every one of those query parameters is on Etsy's robots disallow
  list, so this actor will not emit them.
- `rating` / `reviewCount` are the **seller's**, as Etsy shows them on the card. Etsy abbreviates
  the count (`15.2k`), so it is expanded to `15200` — Etsy's own precision, not ours.

### Switching from `crawlerbros/etsy-scraper`

Change the actor id. Your `searchQueries`, `startUrls`, `maxItems` and `country` work as-is and the
output field names are unchanged. Two things to know: `includeDetails` has no effect (see Limits),
and `shopName` is populated for fewer records.

### Use cases

- Price and discount tracking across a keyword, on a schedule.
- Competitive research: who ranks for a keyword, at what price, with what rating.
- Sponsored-vs-organic share of a keyword's first pages (`isAd` plus `position`).
- Feeding an agent or a dashboard with Etsy pricing without running a browser.

# Actor input Schema

## `searchQueries` (type: `array`):

Keywords to look up on Etsy, e.g. `leather wallet`. Same field name and shape as `crawlerbros/etsy-scraper`, so an existing input works unchanged.

## `startUrls` (type: `array`):

Etsy market, search or category URLs. The keyword is read out of the URL and fetched from `/market/<keyword>`: a `/search?q=` URL is accepted for compatibility but is never requested, because Etsy's robots.txt disallows that path. Same field name as `crawlerbros/etsy-scraper`.

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

Maximum listings to return per keyword. 0 = every result Etsy will paginate through. Same field name as `crawlerbros/etsy-scraper`.

## `maxPages` (type: `integer`):

Stop after this many market pages per keyword (~48 listings per page). Whichever of this and `maxItems` is reached first wins. Same field name as `yumitori/etsy-listings-scraper`.

## `includeAds` (type: `boolean`):

Etsy mixes promoted listings into the grid. Keep them (they are flagged with `isAd` / `badges.ad`) or drop them. Same field name as `yumitori/etsy-listings-scraper`.

## `dedupeAcrossQueries` (type: `boolean`):

Return each listing id at most once across the whole run, instead of once per keyword. You are charged per pushed listing, so leaving this on is also what keeps overlapping keywords from billing twice.

## `proxyConfiguration` (type: `object`):

Etsy is behind DataDome. In our platform probe, raw Apify IPs and the Apify datacenter pool were 403-blocked on 12/12 market-page requests while RESIDENTIAL passed, so RESIDENTIAL is the default. Turning the proxy off will almost certainly return nothing.

## `queries` (type: `array`):

Alias of `searchQueries`, accepted for drop-in compatibility with `yumitori/etsy-listings-scraper`.

## `maxResults` (type: `integer`):

Alias of `maxItems`, accepted for drop-in compatibility with `yumitori/etsy-listings-scraper`.

## `country` (type: `string`):

Proxy exit country for the run. Etsy prices are returned in USD from the US storefront; this only changes which residential IPs are used. Same field name as `crawlerbros/etsy-scraper`.

## `includeDetails` (type: `boolean`):

Accepted so `crawlerbros/etsy-scraper` inputs run unchanged, but it has NO effect: Etsy's `/listing/<id>` detail pages returned 403 DataDome on every proxy tier we measured, residential included. Setting it logs a warning rather than silently pretending. See the README for what this actor returns instead.

## Actor input object example

```json
{
  "searchQueries": [
    "leather wallet"
  ],
  "maxItems": 100,
  "maxPages": 25,
  "includeAds": true,
  "dedupeAcrossQueries": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  },
  "country": "US",
  "includeDetails": false
}
```

# Actor output Schema

## `listings` (type: `string`):

All listing records. Append ?format=csv for CSV.

## `datasetUrl` (type: `string`):

The default dataset.

# 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 = {
    "searchQueries": [
        "leather wallet"
    ],
    "maxItems": 100,
    "maxPages": 25,
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ],
        "apifyProxyCountry": "US"
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("diopside/etsy-products").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 = {
    "searchQueries": ["leather wallet"],
    "maxItems": 100,
    "maxPages": 25,
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
        "apifyProxyCountry": "US",
    },
}

# Run the Actor and wait for it to finish
run = client.actor("diopside/etsy-products").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 '{
  "searchQueries": [
    "leather wallet"
  ],
  "maxItems": 100,
  "maxPages": 25,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ],
    "apifyProxyCountry": "US"
  }
}' |
apify call diopside/etsy-products --silent --output-dataset

```

## MCP server setup

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

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/3TZPxwHC4xsSpg5zF/builds/seWVBCfZvc88iMtyh/openapi.json