Catalog and category discovery
Use Target endpoints to turn catalog and category discovery into repeatable API requests with documented inputs and JSON responses.
Browse Target's public catalog from all categories into paginated product listings, discover valid filters for each result set, and enrich products with detail, reviews, and customer questions.
Extract Target categories, search and category listings, product detail, reviews, questions, and dynamic filter options as structured JSON.
Endpoint families
6
Documented params
29
Examples
7
Live catalog snapshot
Active endpoints
7
Methods
GET
Required params
12
Schema refs
7
{
"platform": "Target",
"endpoint": "target-search",
"method": "GET",
"path": "/target/search",
"auth": "apiKey"
}Use cases
Extract Target categories, search and category listings, product detail, reviews, questions, and dynamic filter options as structured JSON.
Use Target endpoints to turn catalog and category discovery into repeatable API requests with documented inputs and JSON responses.
Use Target endpoints to turn product and price research into repeatable API requests with documented inputs and JSON responses.
Use Target endpoints to turn review and question analysis into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Target endpoint catalog — 7 endpoints, 29 documented request parameters, and 7 published response schemas — the same catalog Docs and Playground run against.
7 documented Target endpoints, grouped into 7 request families — Categories, Category Products and Filter Options, plus 4 more.
29 request parameters are documented across those Target endpoints, 12 of them required — the full input contract is public before you write any integration code.
7 of the 7 Target endpoints ship a recorded example response, and 7 carry a documented response schema — you can code against the real JSON before the first request.
Target endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
7 hosted MCP tools back the Target endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
These cards are generated from the active endpoint catalog, so the landing page reflects the same API surface used by Docs and Playground.
/target/categories
/target/category-products
/target/filter-options
/target/product
/target/questions
/target/reviews
Endpoint catalog
/target/searchSearches Target products and returns normalized products plus every filter group and option available for the current result set. Pass option ids back through filter_ids as a comma-separated list. A zero total with an empty products list is a valid no-results response. The sort enum accepts `relevance`, `featured`, `price-low`, `price-high`, `rating`, `bestselling`, and `newest`.
MCP tool target_search
/target/categoriesReturns Target's current top-level category menu and the complete grouped shop-all directory, including category ids and canonical URLs.
MCP tool target_categories
/target/category-productsReturns paginated products for any category id from target-categories. Each response also contains every available dynamic filter group and option. Pass selected option ids through filter_ids as a comma-separated list. The sort enum accepts `relevance`, `featured`, `price-low`, `price-high`, `rating`, `bestselling`, and `newest`.
MCP tool target_category_products
/target/filter-optionsReturns every dynamic filter group and option for either a product query or category. Provide exactly one of q or category_id. Pass currently selected option ids through filter_ids to obtain the remaining context-aware options.
MCP tool target_filter_options
/target/productReturns normalized product details for one Target item, including product content, images, price, rating, category, and availability flags for the selected store.
MCP tool target_product
/target/reviewsReturns paginated written reviews for a Target item. Pagination is zero-based and page 50 is the upstream maximum.
MCP tool target_reviews
/target/questionsReturns paginated product questions with their nested answers.
MCP tool target_questions
Related APIs
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
Marketplaces & Retail
Turn public Shop.app product and merchant pages into structured JSON for e-commerce product intelligence, price research, shop monitoring, and marketplace discovery workflows.
Company coverage
Target Corporation · TGT
Target is operated by Target Corporation (TGT). Crawlora's SEC endpoints take the same company's CIK, so filings, financials, insider transactions and 13F holdings come from the same API key as the Target endpoints above.
SEC filings & financials API →How to scrape Target
Target's public catalog spans department categories and category-specific filters such as price, brand, size, rating, discount, fulfillment, and availability. Crawlora returns both the products and the valid filter identifiers exposed for each result set.
Start from the complete category directory or a keyword search, with optional store and sort inputs.
Call the filter-options route for the current query or category to receive the department-specific filter groups and identifiers.
Pass selected filter identifiers to search or category-products and increment page to collect deeper catalog results.
Retrieve product detail, reviews, and customer questions for selected Target product identifiers.
FAQ
Yes. The categories endpoint exposes Target's public category directory, and category-products retrieves paginated products for a selected category identifier.
Call filter-options for a keyword or category to discover the valid department, price, discount, size, brand, rating, fulfillment, and availability options. Send the returned filter identifiers through filter_ids on search or category-products.
Yes. Dedicated product, reviews, and questions endpoints return supported public product detail and customer-generated content as structured JSON.
No. Crawlora is not affiliated with Target and provides structured extraction for supported public Target pages. Use Target-owned products when you require an official account-scoped or licensed integration.
Not for general developers. Target's developer network primarily serves existing retail partners and vendors — outside developers don't get open self-serve registration for product-catalog access, only a working-relationship-gated application process. Crawlora's Target endpoints return category, search, product detail, reviews, and question data as structured JSON with a single API key, no partner relationship required.