/target/products

POST /api/target/products

Price: 5 credits

Get full Target product details by TCIN (or product URL): title, brand, price, list_price, images, video, rating and per-star breakdown, secondary ratings, review and question counts, specifications, features, breadcrumbs, return policies, color/style variants and shipping.

How to use it

Fetch a single Target product by TCIN (numeric, optionally A-prefixed) or a product URL. Returns one item with title, brand, brand_url, price/list_price/currency, save_percent, is_on_sale, image+images, videos, rating, rating_count, review_count, question_count, recommended_percentage and per-star rating breakdown, secondary_ratings (design/quality/value...), description, specifications (name/value), features, breadcrumbs+category, item_type, department, import_designation, is_free_shipping, badges, return_policies (user_type/day_count) and variants (color/style options, each with its own TCIN, image and price).

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product string required — Target product TCIN or a product URL containing it (examples: "91466170", "A-91466170", "https://www.target.com/p/-/A-91466170"; minLength: 1)

Response

• @type string (default: "TargetProduct")
• id string required
• url string nullable
• alias string nullable
• brand string nullable
• brand_url string nullable
• price number nullable
• list_price number nullable
• currency string nullable
• save_percent number nullable
• is_on_sale boolean nullable
• image string nullable
• images array (default: [])
• videos array (default: [])
  • @type string (default: "TargetProductVideo")
  • url string required
  • poster_image string nullable
• rating number nullable
• rating_count integer nullable
• review_count integer nullable
• question_count integer nullable
• recommended_percentage integer nullable
• rating_five_count integer nullable
• rating_four_count integer nullable
• rating_three_count integer nullable
• rating_two_count integer nullable
• rating_one_count integer nullable
• secondary_ratings array (default: [])
  • @type string (default: "TargetProductSecondaryRating")
  • name string required
  • value number nullable
• description string nullable
• specifications array (default: [])
  • @type string (default: "TargetProductSpecification")
  • name string required
  • value string nullable
• features array (default: [])
• breadcrumbs array (default: [])
• category string nullable
• category_id string nullable
• item_type string nullable
• department string nullable
• import_designation string nullable
• is_free_shipping boolean nullable
• badges array (default: [])
• return_policies array (default: [])
  • @type string (default: "TargetProductReturnPolicy")
  • user_type string nullable
  • day_count integer nullable
• variants array (default: [])
  • @type string (default: "TargetProductVariant")
  • id string required
  • url string nullable
  • image string nullable
  • swatch_image string nullable
  • price number nullable
  • list_price number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — Product not found (well-formed but nonexistent TCIN, or no product data for it) Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.