Etsy Listings Scraper — Prices, Reviews, Shops | from $1.50/1K | No API Key

Built for Etsy sellers doing competitor research, e-commerce analysts tracking pricing trends, and dropshippers validating handmade/supply niches.

Pricing: Pay per listing — $1.50/1K. First results are free to try.

No API key, no setup. Just give a search keyword and/or a shop name — the actor reads the same public listing data that etsy.com shows in search results and on shop pages.

What you get

Field	Description
listing_id	Numeric Etsy listing ID
title	Listing title
url	Full listing URL on etsy.com (tracking params stripped)
price	Current price (float)
original_price	Strikethrough / list price on discounted listings
on_sale	true when the listing is discounted
currency	ISO 4217 currency code (e.g. USD, EUR, GBP)
image_url	Full-resolution listing image
rating	Star rating (0–5)
review_count	Number of reviews
shop_id	Numeric shop ID
shop_name	Shop name (when exposed on the page)
shop_url	Shop page URL
is_ad	Whether the listing is a promoted/ad slot
free_shipping	Free-shipping badge (best-effort)
availability	Stock status (e.g. InStock, when exposed)
position	Rank within the result set
search_query / shop_filter	Which input produced the row
page_number	Result page the row came from
scraped_at	ISO 8601 timestamp of this scrape
parse_confidence	Data-quality score 0–1
warnings	Array of field-level quality warnings

Input

Parameter	Type	Required	Description
searchKeywords	string	No*	Keyword search across all of Etsy (e.g. "handmade soy candle")
shopName	string	No*	Etsy shop name or URL to list one shop's items (e.g. "CitrineAndCo")
maxItems	integer	No	Max listings (default 100, 0 = unlimited)
proxyConfiguration	object	No	Apify Residential proxy (country US recommended)

* At least one of searchKeywords or shopName is required. You can use both.

Example inputs

Search listings:

{
  "searchKeywords": "handmade soy candle",
  "maxItems": 200,
  "proxyConfiguration": { "useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"], "apifyProxyCountry": "US" }
}

List a single shop:

{
  "shopName": "CitrineAndCo",
  "maxItems": 500
}

How it works

• Keyword search: reads etsy.com/search?q=<keywords>, page by page.
• Shop listing: reads etsy.com/shop/<shopName>, page by page.
• Both modes can run together (deduplicated by listing_id).
• Listing data is read from the page's structured listing cards plus the embedded ItemList metadata, so fields stay stable across cosmetic layout changes.

Access & reliability

Etsy is a protected target — it requires a residential proxy for reliable access, and datacenter IPs are not reliable. This actor reaches the site with a resilient browser tier over Apify Residential that handles the site's challenge step automatically, with a managed-access service wired in as a backstop. You do not need any external proxy or browser account — everything runs on your own Apify account.

Every record ships a parse_confidence score (0.0–1.0), so your pipeline detects layout drift early — before buyers complain.

Monetization

Pay-per-result (PPE): charged per listing returned. No charge for failed runs.

Volume	Cost
100 listings	$0.15
1,000 listings	$1.50
10,000 listings	$15.00

Use with AI agents (MCP)

Compatible with Claude, GPT-4o, and other MCP-aware agents:

https://mcp.apify.com/?tools=bovi/etsy-listings

Integrations

The JSON/dataset output drops into the tools you already run, no glue code:

• n8n / Make / Zapier — pipe every new dataset item into 500+ apps: n8n, Make, Zapier.
• Webhooks — fire your own endpoint the moment a run finishes (docs).
• MCP server — expose this actor as a tool to Claude, Cursor, or any MCP client (guide).
• API & SDKs — fetch the dataset as JSON, CSV, or Excel through the Apify REST API or the Python / JS SDKs.

See all Apify integrations.

FAQ

Do I need an Etsy API key? No. Just provide a search keyword and/or shop name — there's nothing to register.

What if a run returns empty? If searchKeywords returns no results, try a broader term. If a shop has no active listings, shopName returns nothing. For the most reliable access, keep the Apify Residential (US) proxy enabled.

What output formats are available? JSON (default), CSV, and Excel — via the Apify dataset export or API.

Not affiliated with Etsy

This actor is an independent tool that collects publicly available listing data. It is not affiliated with, endorsed by, or connected to Etsy, Inc.

More scrapers from our toolkit

Building a data pipeline? These actors pair well with this one — each runs on your own Apify account with the same pay-per-result pricing, no subscription:

• Facebook Marketplace Scraper
• Grailed Listings
• Kleinanzeigen Listings Scraper
• Leboncoin Listings
• Marktplaats Listings Scraper
• Mercadolibre Scraper

Chain any of them together from the Integrations tab (the Run succeeded trigger) to build a multi-step workflow — one actor's output feeds the next.

Usage statistics

This Actor creates a small, content-free summary at the end of each run. It is used only to monitor reliability and improve this Actor. A copy is saved as USAGE_STATS in your own Apify key-value store, so you can see the exact record created for your run.

Set disableUsageStats to true in the input to opt out. Nothing is sent then; your USAGE_STATS record only says that statistics were disabled.

Only these fields are recorded:

• schema version, Actor name and build number;
• UTC start and finish hour (not a precise timestamp);
• run duration, number of results and time to the first result, each as a coarse range;
• whether the result was empty, the end status, and an error type from a fixed list;
• memory setting and counts of charged events;
• names of the input fields you set, never their values;
• the selected option for input fields that offer a fixed list of choices (for example a sort order).

We do not collect input text, search terms, URLs, domains, usernames, email addresses, names, proxy credentials, tokens, scraped records, output items, raw error messages, stack traces, or hashes of any of those values. Records are kept for no longer than 13 months, used only as aggregated operational statistics, and never sold or shared.

Additional fields (Phase 2)

This Actor also records your Apify user ID, whether Apify marks the account as paying, the size range of list inputs, the selected country when the input offers a fixed list of countries, and one category from a fixed Actor taxonomy. We use these fields only for aggregate reliability, repeat-use and cross-Actor analysis; reports suppress any cell with fewer than five distinct users.

The same disableUsageStats: true input flag turns these fields off too. The user ID is removed after 13 months; we do not export, sell, share, or attempt to re-identify this data.

Run-outcome signals (v2)

To learn whether a run did what it was asked to do, the record also holds a few more coarse ranges and yes/no flags. None of them contains content:

• the result limit you asked for (a range, when the input has one) and what share of it was delivered;
• results delivered per input item you listed (a range);
• output quality as ranges: how fully the result fields were filled, the share of rows that look like errors, the share of duplicate rows, and how many different fields appeared. These are counted in memory while results are saved; no result content is kept;
• how the run was started (console, API, schedule, webhook, another Actor);
• how it ended: stopped by you, timed out, reached the requested limit, stopped by the charge limit, and how many times the platform moved the run;
• if this Actor reports it: how many items to process worked or failed (ranges) and one failure reason from a fixed list;
• a short code made from the names of the input fields you set, never their values.

Repeat-run fingerprint (v2)

When your Apify user ID is recorded (see above), the record also holds an 8-character one-way code made from your input (proxy settings left out) and this Actor's name. It only lets us see that the same account ran the same input again soon after an unsatisfying run; we never see the input itself. It is stored only in the database, never published, and reports use it in aggregate with the same five-user minimum. It is the one exception to the statement above that no hashes are collected, and disableUsageStats: true turns it off.