Etsy Details API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Fetch the full record of one Etsy product from its listing url: description, materials, price range, variants, review highlights and the shop behind it. Despite the action name, profile covers a product, not a buyer account or the shop's full page.

Etsy Details reads one Etsy listing from its link and returns the product record: listing ID, title, description, category, materials, price or price range with the currency, variants, review count, ship-from country and images, plus the shop behind it with its ID, name, review count and years in operation. It describes a product, not a user account. Sellers, trend researchers and buyers sourcing handmade goods use it to study successful listings, compare materials and prices, and judge how established a shop is.

Pass the full listing link with the /listing/<ID>/ path. materials is the tag set shoppers use to filter handmade goods, so keep it for every listing you compare. ships_from_country tells you where an order travels from, which matters for delivery times. shop_years and shop_review_count describe the shop as a whole. A null review_count says Etsy is not publishing that number, not that there are no reviews.

Price $1.39 per 1,000 requests ($0.001389 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Etsy Details endpoint (etsy/profile).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to etsy and action to profile, and put the parameters inside params.
- Required parameters:
- url: Accepts a full Etsy listing URL in the format /listing/<ID>/ for profile and product_detail actions to fetch single item product details. Note that profile targets item details rather than user profiles.
- Returns one object. Main fields: listing_id, title, url, description, materials, category, price, price_min, price_max, currency, review_count, shop_id; 21 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=etsy.
- Example request body:
{
"platform": "etsy",
"action": "profile",
"params": {
"url": "https://www.etsy.com/listing/1710567856/its-okay-to-make-some-mistakes-shirt"
}
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Name	In	Type	Required	Default	Description
`Authorization`	header	`string`	Yes	-	Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository.
`platform`	body	`string`	Yes	`etsy`	Platform identifier, fixed value.
`action`	body	`string`	Yes	`profile`	Capability identifier, fixed value.
`url`	body.params	Not declared	Yes	-	Accepts a full Etsy listing URL in the format /listing/<ID>/ for profile and product_detail actions to fetch single item product details. Note that profile targets item details rather than user profiles. It cannot replace the required shop parameter when querying shop endpoints.

Code samples

bash

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "etsy",
  "action": "profile",
  "params": {
    "url": "https://www.etsy.com/listing/1710567856/its-okay-to-make-some-mistakes-shirt"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

Field preview

There is no real sample for these example parameters yet: this shows the response shape and fields from the contract, with … as placeholders. It is not the result of a real call.

json

{
  "id": "req_…",
  "platform": "etsy",
  "action": "profile",
  "results": {
    "listing_id": …,
    "title": …,
    "url": …,
    "description": …,
    "materials": …,
    "category": …,
    "price": …,
    "price_min": …,
    "price_max": …,
    "currency": …,
    "review_count": …,
    "shop_id": …,
    "shop_name": …,
    "shop_review_count": …,
    "shop_years": …,
    "ships_from_country": …,
    "image_url": …,
    "platform": …,
    "images": …,
    "review_highlights": …,
    "review_tags": …,
    "variants": …
  },
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

Field	Meaning
`listing_id`	Keeps the platform's own meaning
`title`	Title. null when the platform has no titles (for example text-only posts).
`url`	Link to the record on the platform.
`description`	Summary or description, usually shorter than text.
`materials`	Keeps the platform's own meaning
`category`	Category name in the platform's own taxonomy, not normalized across platforms.
`price`	Price as a number without a currency symbol; see currency.
`price_min`	Keeps the platform's own meaning
`price_max`	Keeps the platform's own meaning
`currency`	Currency code of the price (for example CNY, USD). If price is present but currency is null, do not assume a currency.
`review_count`	Number of reviews, for product and business capabilities. null means not disclosed, not 0.
`shop_id`	Keeps the platform's own meaning
`shop_name`	Keeps the platform's own meaning
`shop_review_count`	Keeps the platform's own meaning
`shop_years`	Keeps the platform's own meaning
`ships_from_country`	Keeps the platform's own meaning
`image_url`	Image link. Capabilities with several images may return an image_urls array.
`platform`	Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok).
`images`	Array of image links in the platform's display order; absent when there are no images.
`review_highlights`	Keeps the platform's own meaning
`review_tags`	Keeps the platform's own meaning
`variants`	Keeps the platform's own meaning

FAQ

Is Etsy Details a shop or user profile?

No. Details reads a product listing, the item behind a /listing/ link. For the seller's shop, use Etsy Shop with the shop's short name or its /shop/ link; for what buyers say, Etsy Reviews returns reviews across the whole shop rather than for one listing.

Which link format does `url` need?

The full listing link with the numeric listing ID after /listing/, shaped like https://www.etsy.com/listing/1710567856/its-okay-to-make-some-mistakes-shirt. Shop pages and search results are not listings and do not work here. The ID comes back in listing_id, a good key for de-duplicating the listings you store.

Why is there a price range instead of one price?

Listings with several variants, such as sizes or colors, can be priced per variant, so price_min and price_max give the low and high ends of the range, in the code given by currency. When you compare listings, compare like with like, for example the low end of each range, and check variants to see what each option is.

Errors and billing

401: Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.
422: Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.
402: Insufficient balance. Top up first.
429: The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.
503: Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.
200 empty: The request completed without data and is not charged (billing.reason = empty_result_refunded).