1688 product detail API: compare SKU prices, MOQ and shipping

A 1688 product detail API helps answer a question that search results leave open: what does this exact offer say about the variant and quantity you want to buy? Nexscope documents product, SKU, pricing, shipping and seller fields for a supplied offer identifier. Begin with the API capability map if you still need to choose a research task.

Quick answer: Nexscope’s 1688 Product Detail API retrieves a selected offer using a string offerId. Inspect skuList, saleInfo, shippingInfo and seller fields together. Keep single-piece prices, wholesale tiers, currencies and weight units separate. The result supports an offer comparison; it does not confirm a purchase quote or certify a supplier.

What do you need before requesting product details?

You need the offer identifier, not a screenshot or a loosely similar product name. Keep offerId from 1688 product search or an eligible listing URL. For visual discovery, use the 1688 image-search workflow first, then inspect the shortlisted offers individually.

The current request requires offerId as a positive-integer string. Preserve it from input through storage and export. Converting long IDs into floating-point numbers can change the identifier. A spreadsheet should also treat the field as text.

How do you call the 1688 Product Detail API?

The current reference documents this REST operation with bearer authentication:

POST https://api.nexscope.ai/alibaba1688/productDetail

The following is a request template, using an identifier from the documentation, not a fresh test or a supplier recommendation. Replace it with the offer you intend to inspect.

curl -X POST 'https://api.nexscope.ai/alibaba1688/productDetail' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"offerId":"1040473674152","currency":"USD"}'

For MCP, inspect the nexscope_1688_product_detail tool and its own input schema. Do not assume an SDK method or response nesting from another provider. Keep your API key in a server-side secret store, inspect both HTTP and business status, and retain a redacted error and trace identifier if returned. HTTP 200 alone does not prove usable product data.

How should you read SKU prices and quantity tiers?

Choose the exact variant and intended order size before comparing any price. The contract separates skuList from product-level saleInfo. A product headline price, a SKU price and a one-piece price can describe different purchase conditions.

The documented newer pricing model distinguishes a one-piece retail price from a wholesale SKU price for quantities of at least two. Older offers still require their own tier interpretation. Check the selected offer rather than applying that newer rule to every response.

For a proposed 50-unit test, save the exact SKU, pack size, applicable quantity threshold and currency in the same row. If the requested tier is absent, mark the price pending supplier confirmation. This comparison procedure is an example, not an executed order or a measured sourcing result.

Which shipping fields need special care?

Shipping weights do not all share one unit. The current contract documents product-level weight and officialWeight in kilograms, skuShippingInfoList weights in grams, and skuShippingDetails weight fields in kilograms. Keep the field path and unit with each value before converting it for a freight estimate.

Retain the dispatch location, delivery-time information and available SKU dimensions. Missing dimensions or packaging information should remain unknown. Do not derive a binding international shipping quote from a bare product weight; packaging, route, destination and carrier rules still matter.

What can supplier fields establish?

companyName, sellerOpenId and sellerDataInfo provide identity and service signals where available. They help organize follow-up questions. A trading medal, service score or certificate image is not an independent audit of the business or product.

Ask finalists to confirm the SKU, material, quantity, price tier, production role, sample process and dispatch terms. Preserve replies alongside the API observation date. If the decision depends on a product certificate, verify its scope and relevance rather than treating the presence of a returned field as approval.

For each shortlisted offer, keep one comparison row: source URL, observation date, string offer ID, SKU, intended quantity, applicable price, currency, MOQ, weight source and unresolved questions. Keep estimated landed costs in separate columns with your assumptions. The API does not negotiate, place an order or calculate your final margin.

Evidence, cost and next steps

Reviewed October 26, 2026 against the public Product Detail reference and its published request and response contracts. This is a vendor-authored documentation guide. No paid detail request, supplier verification, latency benchmark or purchase was performed for this article.

Check current pricing and access before execution. Search, detail and any separate analysis request can be separate actions; an upstream costToken field is not a substitute for your account’s actual credit record.

Continue with the 1688 search and filtering tutorial to find alternatives, or the dated image-search evidence to see the limits of one observed visual search.

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