Target reference
Every Target operation, from the registry
6 operations wired in the registry, 6 of them proven by real traffic.
Choose a Target operation
Start with the object your task needs. The groups below use the current catalogue; open an endpoint to check accepted identifiers, filters, price and availability before retrieving.
Products and categories
- Target categories — Target's top-level category tree with node ids for target/category.
- Target category products — Products in a Target category at one store, 24 per page.
- Target product — One Target product: title, brand, price, rating and review statistics, description and bullets, images and videos, category breadcrumbs, variations and return policy.
Reviews and offers
- Target product reviews — Reviews of a Target product, ten per page, with the rating distribution, recommendation rate and photo counts.
Search and discovery
- Target product search — Products matching a keyword at one Target store, 24 per page, with price, rating, images and variations.
Other operations
- Target stores near a place — Target stores near a place with store ids, distance, phone, address and today's hours.
Check fields and collection limits
Use the endpoint’s declared parameters and returned continuation. Filters from another platform do not automatically apply here. Preserve source identifiers, URLs and warnings; a successful page does not establish complete history. Published response schemas identify whether they come from a reviewed shaper or observed response shapes.
Agents can use get_endpoint for the current contract and get_docs with topic platforms/target to read this page. The coverage guide explains nulls and partial results, and the production guide covers budgets and recovery.
Operations
Target
Each row is a registry operation: expand it for parameters, a curl built from the registry's own examples, and a Markdown copy of the whole entry. The badge on the right is the operation's state, read at request time — we publish all three rather than rounding up. Recorded proof is historical, not a guarantee of current availability.
- live · proven
- a real upstream response has been served through this API and recorded
- wired · unproven
- a real-data route is registered, but qualifying proof is absent; permission or capacity restrictions may apply
- sample · free
- no live upstream — /v1 refuses it, /sandbox returns a marked sample
Target
6 operationsElsewhere
The same registry, other shapes
- Target overview — supported data categories and use cases for this platform.
- Full endpoint reference — every platform on one page.
/openapi.jsonor/openapi.yaml— the machine-readable contract, for Postman, Insomnia or a client generator.GET /v1/utility/endpoints?platform=target— the same rows to your code at runtime, for 0 credits.