Etsy Product details API

POST

API health

24h health: Normal
24h average time: —

Healthy / normal
Available
Limited
Mostly down

Normal

Last 24 hours

Last 30 days

Get one Etsy product from its listing url, with description, current and original price, visible stock quantity, rating, variants and tags. in_stock_quantity is the count shown on the page, not an audited inventory, and nothing is reserved.

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 Product details endpoint (etsy/product_detail).

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 product_detail, 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: id, url, name, text, price, original_price, currency, in_stock_quantity, rating, rating_scale, review_count, shop_id; 15 fields in total, full list at https://api.everyinfra.com/api/v1/social/catalog?platform=etsy.
- Example request body:
{
"platform": "etsy",
"action": "product_detail",
"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	`product_detail`	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": "product_detail",
  "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": "product_detail",
  "results": {
    "id": …,
    "url": …,
    "name": …,
    "text": …,
    "price": …,
    "original_price": …,
    "currency": …,
    "in_stock_quantity": …,
    "rating": …,
    "rating_scale": …,
    "review_count": …,
    "shop_id": …,
    "variants": …,
    "tags": …,
    "image_url": …,
    "platform": …
  },
  "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
`id`	The record's unique ID on the platform. Unique only within one platform; IDs can repeat across platforms.
`url`	Link to the record on the platform.
`name`	Name of the object itself, for account, product and business capabilities.
`text`	Body text with HTML removed, returned in full and never cut short (on a few platforms the list results themselves carry only an excerpt; the platform's field notes say so).
`price`	Price as a number without a currency symbol; see currency.
`original_price`	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.
`in_stock_quantity`	Keeps the platform's own meaning
`rating`	Rating. The scale varies by platform: rating_scale on the same row gives the maximum (usually 5; Booking, Douban, iQIYI and NAVER use 10). Convert with rating_scale before comparing across platforms, or the comparison can come out backwards.
`rating_scale`	Maximum of rating in the same row: 5 for five-star scales, 10 for ten-point scales. Present only when the row has a rating.
`review_count`	Number of reviews, for product and business capabilities. null means not disclosed, not 0.
`shop_id`	Keeps the platform's own meaning
`variants`	Keeps the platform's own meaning
`tags`	Array of tags. An empty array, not null, when there are none.
`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).

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