How to Scrape Etsy Product Data

Get the framing right before you write code, because "the data is public" answers only one of two separate legal questions.

In the United States, the Ninth Circuit's ruling in hiQ Labs v. LinkedIn (2022) held that scraping data that's publicly accessible, meaning no login and no authentication wall, generally does not violate the Computer Fraud and Abuse Act. That decision is about unauthorized access, not a license to do anything with the data. Etsy's Terms of Use separately prohibit automated collection, so scraping public pages can still be a breach of contract even where it isn't a CFAA violation. Those are two different questions, and the second one doesn't disappear because the first one is settled.

Guardrails that keep a project defensible:

• Collect public listing data only: title, price, shop name, rating, review count, tags. Never anything behind a login, and never personal data about buyers or the makers themselves.
• Rate-limit yourself and back off on errors. Etsy shops are small businesses, and hammering their pages is both rude and a fast way to get flagged.
• Don't republish copyrighted assets. Product photos on Etsy belong to the sellers, so treat image URLs as references, not content to redistribute.
• If the data feeds a commercial product, run it past a lawyer. This is engineering guidance, not legal advice.

Price monitoring, category research, and competitive intelligence are common, legitimate uses of public marketplace data. For the business context around that, we cover it in How E-commerce Companies Use Proxies for Competitive Intelligence.

Etsy publishes a real developer API, the Etsy Open API v3, and it should be your first stop. It's the sanctioned path, it returns clean structured JSON, and it won't fight you with bot challenges. The catch is what it's for.

The Open API is built to let apps manage a shop the owner controls, or a shop that has authorized your app over OAuth 2.0. Private data and write actions require an OAuth token with the right scope. A few read endpoints work with only your app's API key, and the useful one for public product data is getListing, which returns a single active listing by its numeric id:

import requests

listing_id = 1234567890
r = requests.get(
    f"https://openapi.etsy.com/v3/application/listings/{listing_id}",
    headers={"x-api-key": "YOUR_ETSY_APP_KEY"},
    params={"includes": "Images,Inventory"},
    timeout=30,
)
listing = r.json()   # title, price, currency_code, quantity, tags, ...

That's the cleanest possible read for a listing you already have an id for. The friction shows up at scale: Etsy applies per-app rate quotas and its API Terms limit how long you may cache and how you may reuse what you pull. There's no public endpoint that dumps a competitor's whole catalog, and building a rival marketplace from API data is expressly against those terms. So the official API is excellent for your own shop and for authorized integrations, and it's a poor fit for broad market research across thousands of shops you don't control.

That gap is where scraping public pages earns its place. Here's the honest comparison:

Use the API when the shop is yours or has authorized you. Reach for scraping when you need public, cross-shop data the API deliberately doesn't hand out. If you're deciding between a managed scraper and running your own proxy pool for that second job, Web Scraping API vs Self-Managed Proxies lays out the tradeoff.

A public Etsy listing lives at https://www.etsy.com/listing//, and the numeric listing_id is the anchor for everything. Store it as your primary key and every other field hangs off it. The important thing to know up front: Etsy embeds a