Target API

Get Target product and store data with one API

Name: Target Data API
Brand: SocialCrawl
Availability: InStock

Fetch Target product detail, reviews, categories, taxonomy, and nearby stores as structured JSON with one SocialCrawl API key. Shared commerce schema. Reads are priced in credits.

Read the docs How it works Try live

/v1/target

5 active endpoints. 1 and 5 credit tiers.

GET /v1/target/product
GET /v1/target/reviews
GET /v1/target/category
GET /v1/target/categories
GET /v1/target/stores

What Target endpoints does SocialCrawl ship?

Five live read endpoints for Target. TCIN product detail, reviews, category browse, category taxonomy, and store finder. Data API only.

Product by TCIN

5 credits

/v1/target/product

Full Target product for a TCIN. Title, price, rating, images. Advanced tier (5 credits).

tcin

Product reviews

5 credits

/v1/target/reviews

Reviews for a Target TCIN. Rating, text, author, optional page. Advanced tier (5 credits).

tcin, page

Category browse

5 credits

/v1/target/category

Products in a Target category_id. Optional page. Advanced tier (5 credits).

category_id, page

Category taxonomy

1 credit

/v1/target/categories

Target category taxonomy reference. Use ids here when browsing category products. Standard tier (1 credit).

(none)

Store finder

1 credit

/v1/target/stores

Find Target stores near a location query (zip or place). PlaceList shape. Standard tier (1 credit).

query

Target API5 endpoints supported

View docs

Products

Reviews

Reference

Stores

Returns one Target product by TCIN: title, brand, description, current and regular price, rating with its star breakdown, images, variations, and stock.

Use it when you have a TCIN and need full product detail. Prices are national catalogue prices, not the price at a particular store.

GET/v1/target/product?tcin=92148487

tcin

tcin · Target catalogue id (TCIN), the numeric id at the end of a target.com product URL: target.com/p/<name>/-/A-92148487 is TCIN 92148487. Target rolls a colour or size variant up to its parent product, so the id returned by GET /v1/target/product can differ from the one you sent; the id you asked for is preserved at product.ext.requested_id.

$ curl https://www.socialcrawl.dev/v1/target/product?tcin=92148487 \
    -H "x-api-key: sc_YOUR_API_KEY"

— · idle

// Running this live needs your own API key — hit "Try it" to see an example response

How the Target API works

Target is a normal SocialCrawl data surface. You call GET /v1/target/… with an API key, spend credits on live misses, and get a single JSON envelope back.

Authenticate every call

Send your key in the x-api-key header. No Target OAuth app for public reads. The same key works across SocialCrawl platforms.

GET with query params

All Target routes are GET. Pass tcin, category_id, query, page as query strings. We validate formats before charging.

Pay in credits, not seats

Product, reviews, and category cost 5 credits. Categories taxonomy and stores cost 1 credit. Cache hits cost 0.

Read one JSON envelope

Every response is the same shape: success, data, credits_used, credits_remaining, request_id, cached. Lists also carry pagination when the route pages.

The usual integration chain

Most products discover entities first, then deepen detail and reviews only when needed.

01Taxonomy

GET /v1/target/categories

Category ids and labels

Resolve category_id before browse.

02Browse

GET /v1/target/category?category_id=…

ProductList with TCINs

Assortment without a prior keyword.

03Product

GET /v1/target/product?tcin=…

Full Product for the TCIN

Deepen one SKU.

04Reviews

GET /v1/target/reviews?tcin=…

ReviewList for the TCIN

Customer language for that SKU.

request

GET /v1/target/categories
Host: www.socialcrawl.dev
x-api-key: sc_your_api_key_here

GET /v1/target/product?tcin=92148487
GET /v1/target/reviews?tcin=92148487

response envelope

{
  "success": true,
  "data": {
    "product": {
      "id": "92148487",
      "title": "Example product",
      "price": { "current": 12.99, "currency": "USD" },
      "rating": 4.6
    }
  },
  "credits_used": 5,
  "credits_remaining": 9995,
  "request_id": "req_…",
  "cached": false
}

What lands in data

Field names match the rest of SocialCrawl where archetypes align. Parse once, reuse across platforms.

Productproduct

id (TCIN), title, price, rating, images

ProductListcategory

items[] with tcin, title, price

ReviewListreviews

items[] with rating, text, author

Analytics / PlaceListcategories, stores

taxonomy rows or store places near query

Inside the gateway

Same request lifecycle as every other /v1 platform endpoint. Target is not a sidecar.

Edge receives the call

Next.js catch-all routes into the Hono social API. We mint a request_id, authenticate the key, then enforce rate limit (600/min) and concurrency (50 in flight per key).

Validate, then debit

Registry lookup finds target/product (or reviews, category, stores). Required params and format checks run first. Invalid input returns 400 with no charge. Valid calls debit the tier cost atomically before upstream work.

Cache or fetch

A deterministic cache key is built from platform + resource + params. Hit: return immediately, credits_used = 0. Miss: Target commerce upstream paths run. Retries on 5xx/network with a circuit breaker if the source is unhealthy.

Normalize and return

Upstream JSON is mapped to commerce archetypes (Product, ProductList, ReviewList, SellerList, App, PlaceList as applicable), validated against the canonical Zod schema, then wrapped in the success envelope and logged for billing audit.

Billing rules that matter in production

Product / reviews / category: 5 credits
Categories taxonomy: 1 credit
Stores: 1 credit
Cache hit: 0 credits
Empty / hard fail: auto-refund
Bad params: 400, never charged
No credits: 402, never charged
tcin is the product deepen key
No cart or RedCard tools

How we get the data

Target is public read data. We normalize it into the SocialCrawl schema so your code does not learn a second vendor SDK.

What Target is for this API

Public product, reviews, category taxonomy, and store locations. Read-only.

How SocialCrawl reaches it

Target commerce upstream paths behind the unified /v1 envelope.

What leaves our edge

Product, ProductList, ReviewList, PlaceList, and taxonomy analytics shapes.

What we do not ship live

No cart, Circle, or store inventory writes.

field map sketch

TCIN row→ product.*title, price, rating

review pages→ ReviewListoptional page param

taxonomy / stores→ Analytics / PlaceListcategory ids; store locations

What this API is used for

The jobs this API is most often used for.

5active Target endpoints in the registry

1 / 5credit ladder for taxonomy/stores vs product/reviews/category

Assortment, reviews, and store proximity

Callers concentrate on search or taxonomy, then deepen detail and reviews for shortlisted entities. TCIN product and reviews at 5 credits, taxonomy and stores at 1, one SocialCrawl key.

Live misses are typically a few seconds. Some DFS-backed routes can take longer on cold cache.

Use case examples

Common ways teams put this data to work, and the stack each one tends to run.

Retail merchandisers

Python, BI

categories then category browse, product for TCIN facts.

VoC teams

Node, warehouses

reviews by TCIN for customer language.

Local ops

scripts, maps

stores by zip or place for proximity checks.

Call it in two lines

Product and reviews are 5 credits. Taxonomy and stores are 1. Cache hits are free.

curl "https://www.socialcrawl.dev/v1/target/product?tcin=92148487" \
  -H "x-api-key: sc_your_api_key_here"

curl "https://www.socialcrawl.dev/v1/target/stores?query=10001" \
  -H "x-api-key: sc_your_api_key_here"

Target on SocialCrawl

Same key as the rest of the catalog

Platform docs Get an API key

Endpoints

What data does the Target API return?

Every endpoint returns structured JSON in a unified envelope. Computed fields such as engagement rate and content category are included only where the endpoint supports them and the required source inputs are present.

ProductGet a Target product by TCIN ReviewsGet Target product reviews CategoryBrowse Target products in a category CategoriesList the Target category taxonomy StoresFind Target stores near a location

Comparison

How does SocialCrawl compare to DIY Target.com scraping for Target data?

Same Target data, two very different paths. Auth, rate limits, schema, and cost — side by side.

Feature	SocialCrawl	DIY Target.com scraping
Setup	One GET with an API key	Headless browser, proxy pool, and a parser for Target's GraphQL payload
Product payload	Clean canonical JSON, roughly 3 KB	100 KB of raw GraphQL you filter yourself
Review pagination	Cursor that terminates exactly at the last page	Manual page walking with your own duplicate detection
Blocked requests	Retried upstream, and never billed if they fail	Your problem, and your cost
Cross-retailer parsing	Same shapes as Amazon, Walmart, and Google Shopping	One bespoke parser per retailer

Setup

SocialCrawl

One GET with an API key

DIY Target.com scraping

Headless browser, proxy pool, and a parser for Target's GraphQL payload

Product payload

SocialCrawl

Clean canonical JSON, roughly 3 KB

DIY Target.com scraping

100 KB of raw GraphQL you filter yourself

Review pagination

SocialCrawl

Cursor that terminates exactly at the last page

DIY Target.com scraping

Manual page walking with your own duplicate detection

Blocked requests

SocialCrawl

Retried upstream, and never billed if they fail

DIY Target.com scraping

Your problem, and your cost

Cross-retailer parsing

SocialCrawl

Same shapes as Amazon, Walmart, and Google Shopping

DIY Target.com scraping

One bespoke parser per retailer

FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

What data can I get from the SocialCrawl Target API?

Full product detail (title, brand, description, highlight bullets, current and regular price, average rating with its complete 1-5 star distribution, written-review count, image gallery, colour and size variations, and stock status) plus written customer reviews with text, rating, reviewer nickname, date, helpful votes, verified-purchase flag, and photos.

Where do I find a Target TCIN?

It is the number at the end of any Target product URL. In target.com/p/beats-solo-buds-true-wireless-bluetooth-earbuds/-/A-92148487 the TCIN is 92148487. Pass it as the tcin parameter to either endpoint. Malformed ids are rejected before any credit is deducted.

Is there a Target keyword search endpoint?

No, and that is deliberate. Target's search surface returns at most 24 products, ignores the page parameter, and answers a query that matches nothing with 24 unrelated products, so there is no way to tell a real result from a miss. Shipping it would mean billing you for rows you did not ask for. Bring a TCIN, or use our universal search across sources.

Why did I get back a different TCIN than the one I sent?

Target rolls colour and size variants up to a parent product. Ask for a variant and you get the parent, whose payload describes the whole family. The id field always describes the payload you received, and ext.requested_id carries the id you asked for whenever the two differ, so nothing is lost.

How many reviews come back per call, and do pages overlap?

Ten per page, fixed by Target and not raisable. Pages never repeat a row and the review total is exact, so a full crawl is deterministic: pass the returned cursor back until has_more is false. If you only want the star breakdown, read ext.rating_distribution from the product endpoint instead, which is one call rather than one per ten reviews.

Why are the rating count and the review count different numbers?

They are different populations. The rating count is everyone who left a star rating; the review count is everyone who wrote review text, and it is the same population the reviews endpoint paginates over. On a typical product the first is two to three times the second. Both come straight from Target, and neither is an estimate.

Does Target pricing vary by store?

Not on this endpoint. Target's product surface reports the same price whatever store is queried, so we do not offer a store or ZIP parameter here and you should treat the price as national catalogue pricing. Walmart genuinely does vary by store, and our Walmart endpoints accept ZIP, state, and store id for exactly that reason.

Is scraping Target data legal?

SocialCrawl returns publicly available Target data and does not access private or login-gated content. Whether scraping fits your project depends on your use case and jurisdiction — you are responsible for complying with Target's terms of service and applicable data-protection laws such as GDPR and CCPA. This is general information, not legal advice.

Target scraping API vs the official Target API — what's the difference?

With SocialCrawl there is no app review or approval queue — sign up and call Target endpoints immediately with a single x-api-key. Responses share one unified schema with every other SocialCrawl platform, and credit-based pricing replaces per-platform quotas. Official APIs are still the right choice for posting and other write actions: SocialCrawl is read-only data.

Ask AI about SocialCrawl

Ask ChatGPT Ask Perplexity Ask Gemini Ask Claude Ask Grok

Read the Target API reference in the docs

🤖 AI agent or LLM? Read this page as markdown