Shopee product research API: search, compare and inspect details

A Shopee product research API helps you compare products within a chosen marketplace before deciding which listings deserve closer investigation. Nexscope provides product search with research filters and a separate product-detail lookup. This guide follows a bounded search-to-detail workflow; see the API capability map to compare tasks across platforms.

Quick answer: Start Nexscope’s Shopee Product Search with a supported station, a relevant keyword and a small page. Compare like-for-like products in local currency, keeping reported 30-day units, estimated units and historical units separate. Pass an eligible product URL to Product Detail for closer inspection; these research calls do not manage a seller account.

Which Shopee API should you start with?

Use search when you need candidates and detail when you have one eligible listing. The interfaces do not accept an identical input object. Search requires station; detail requires a validated productUrl.

The last article covers selling decisions. This tutorial concentrates on request fields, comparable records and integration boundaries. Neither public research call establishes permission to edit listings or retrieve a seller’s private orders.

How do you search products in one Shopee market?

Choose the station before interpreting price or demand. The current reference accepts supported site names or codes; the example below uses SG. Repeating the same price band in another station does not create a currency-adjusted or economically equivalent comparison.

This is an illustrative request body, not a live search result. Its keyword and ten-result page define a small first check, not a recommended niche.

{
  "station": "SG",
  "keyword": "storage box",
  "keywordType": 2,
  "orderBy": "sold",
  "orderByType": "DESC",
  "page": 1,
  "pageSize": 10
}

The current REST reference documents this operation with a Nexscope bearer API key and JSON:

POST https://api.nexscope.ai/yy/shopee/getProductInfos

For MCP, inspect nexscope_shopee_product_search and its input schema. Keep credentials server-side and record the station, query, filters, sorting, page and observation date with the response.

keywordType documents 1 for exact phrase, 2 for multi-word AND and 3 for multi-word OR. The example requires both words. If it yields too little useful evidence, change one condition at a time rather than combining a new market, keyword and price range in the same comparison.

Which filters make products comparable?

Start with product function, size and bundle, then apply supported numerical filters. A cheap accessory and a full product can share a keyword. A large result count does not establish a coherent competitor set.

The response documents products, total and totalSize. Here, total is the current returned count and totalSize is the overall result count. Preserve that distinction before deciding whether you collected the whole query result. Pagination uses page starting at 1, with pageSize in the documented range of 1–1000; a small page is more useful for an initial contract check than immediately requesting the maximum.

How do you move from search to product details?

Retain pid, product links, shop identifiers and station from the search result. Product Detail currently takes productUrl, not a bare search pid. Check the returned URL against the detail reference before making the next call.

The documented URL must use HTTPS on a supported Shopee host and have a path ending in -i.<shopId>.<itemId>. Supported hosts listed in that contract include shopee.sg, shopee.co.id, shopee.com.my, shopee.ph, shopee.co.th, shopee.tw, shopee.vn and shopee.com.br; the accepted port is omitted or 443. Do not assume a short link, unrelated host or a search-results URL is accepted.

Open the Product Detail Playground, substitute your eligible listing URL and inspect the current schema. Its documented upstream success payload contains one product in a data array and total: 1. Read the selected route’s envelope and business status rather than assuming that every Nexscope search and detail response nests product rows the same way.

How should sales, price and missing values be interpreted?

Keep sold, estimateSold and historicalSold in separate columns. The contract describes them as previous-30-day units, estimated previous-30-day units and historical units respectively. They are source research signals, not your authorized seller-account sales report or proof of future demand.

Compare price, minPrice and maxPrice with the actual variation and pack size. Preserve the local currency and collection date. A product’s lowest variant price can describe a small accessory, and an estimate can differ from another field without proving that either is a measured merchant figure.

For a storage-box study, retain capacity, dimensions, bundle count, station, price range, reported and estimated activity, rating, rating count and unresolved questions. Missing attributes remain unknown. Do not have an AI fill missing dimensions or substitute a Google search-volume number for a Shopee sales metric.

Evidence, access and the next research step

Reviewed October 26, 2026 against the public search and detail contracts. This vendor-authored guide contains request templates, not fresh API results, an independent accuracy benchmark or customer testimonials. No paid search or detail call was executed for it.

Inspect current pricing and access, and budget search pages and selected detail requests separately. Check HTTP and business errors before retrying, and keep actual charged credits with the pilot record.

After marketplace research, investigate sourcing separately through 1688 product search. Compare another marketplace with the Temu research guide or Ozon research guide. A visual or keyword match across platforms is a lead to inspect, not proof of an identical product or achievable margin.

Last reviewed: 2026-10-26 · Maintained by the official Nexscope team · Editorial & evidence policy.