Scavio Etsy

Etsy via Scavio

Search Etsy listings, pull one listing in full with its variations and reviews, open a shop's profile and catalogue, and page through a shop's reviews. All endpoints return structured JSON.

When to trigger

Use this skill when the user asks to:

• Search Etsy for a product, with price, on-sale and free-shipping filters, sorted by relevance, price or newest
• Pull one listing in full - description, price, availability, material, category path, ship-from, all images, buyer-selectable variations, aggregate rating and its first page of reviews
• Read a shop's profile: location, year opened, sales and admirer counts, rating, review and listing counts, star-seller flag, announcement and sections
• List a shop's own listings
• Page through a shop's reviews across all its listings
• Do handmade/craft market research, competitor shop analysis or price comparison on Etsy

Setup

Get a free API key at scavio.dev (50 free credits to get started, no card required):

export SCAVIO_API_KEY=sk_live_your_key

Every request is a POST with a JSON body and:

Authorization: Bearer $SCAVIO_API_KEY

Endpoints

Base URL: https://api.scavio.dev. Every Etsy endpoint costs 2 credits.

Which endpoint has the reviews

A listing's own first-page reviews ride the product endpoint. The reviews endpoint returns a shop's reviews pooled across all its listings. Use product for one item, reviews for the whole shop.

Parameters

Search (/search)

Product (/product)

Shop (/shop), Shop Products (/shop/products), Reviews (/reviews)

Examples

import requests

BASE = "https://api.scavio.dev"
# Your key from https://scavio.dev. Load it from your environment or secret
# store in real code - keep it out of source control.
API_KEY = "sk_your_key_here"
HEADERS = {"Authorization": f"Bearer {API_KEY}"}

# 1. Search, newest first, on sale only
found = requests.post(f"{BASE}/api/v1/etsy/search", headers=HEADERS,
    json={"query": "ceramic mug", "sort": "most_recent", "on_sale": True,
          "max_price": 40}).json()

row = found["data"]["items"][0]
listing_id, shop = row["listing_id"], row["shop"]

# 2. One listing in full - variations, aggregate rating, first reviews
listing = requests.post(f"{BASE}/api/v1/etsy/product", headers=HEADERS,
    json={"listing": listing_id}).json()

# 3. The shop's profile, then its reviews
shop_profile = requests.post(f"{BASE}/api/v1/etsy/shop", headers=HEADERS,
    json={"shop": shop}).json()
reviews = requests.post(f"{BASE}/api/v1/etsy/reviews", headers=HEADERS,
    json={"shop": shop, "page": 1}).json()

curl:

curl -s https://api.scavio.dev/api/v1/etsy/search \
  -H "Authorization: Bearer $SCAVIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query":"linen apron","sort":"lowest_price"}'

Response shape

Every response uses the envelope { data, response_time, credits_used, credits_remaining }. data carries the listings/shop/reviews payload plus count on the paginated endpoints.

Guardrails

• Every Etsy call is 2 credits, including one that comes back empty.
• Use product for one listing's reviews, reviews for the whole shop's reviews.
• Shop-grid cards (search and shop/products) carry no per-card rating; get the aggregate rating from product or shop.
• Never invent a sort value; unrecognised values are rejected before the request runs.
• Never fabricate prices, ratings, shop details or review text. Only return what the API returned.
• Review text is written by real buyers. Summarise; do not build profiles of individuals.

Failure handling

• 400 means an invalid or missing parameter. Fix and retry.
• 401 means the API key is invalid or missing. Check SCAVIO_API_KEY.
• 404 means the listing or shop could not be resolved.
• 429 means rate or usage limit exceeded. Wait before retrying. See rate limits.
• 502 / 503 mean the source is temporarily unavailable - wait a few seconds and retry.
• An empty result set is usually the filters - widen the price range or drop on_sale / free_shipping.
• If SCAVIO_API_KEY is not set, prompt the user to export it before continuing.