Ozon Intelligence SR: ozon/product Detail Search API

Use Ozon Intelligence SR: ozon/product Detail Search API through Nexscope with documented parameters, structured results and API key authentication.

CostRecent Avg. 10 · Range 10–25 credits / call

Try online

POST · https://api.nexscope.ai/sr/ozon/productDetailSearchMCP · nexscope_data_sr_ozon_product_detail_search

Ozon Intelligence SR

What this API does

Use Ozon Intelligence SR: ozon/product Detail Search API through Nexscope with documented parameters, structured results and API key authentication. The request accepts sku, dateRange, uId, memberId. Its documented result includes errcode, errmsg, totalSales, dailySales, totalRevenue, stock, startDate, endDate.

Ozon Intelligence SR: ozon/product Detail Search API API use cases

Find products matching a sourcing brief

To find products matching a sourcing brief, a marketplace analyst submits sku and dateRange to Ozon Intelligence SR: ozon/product Detail Search API. The returned errcode, errmsg, totalSales help identify products matching the requested search criteria.

Compare a product search shortlist

A marketplace analyst uses Ozon Intelligence SR: ozon/product Detail Search API with sku and dateRange to compare a product search shortlist. The returned errcode, errmsg, totalSales help compare candidates before requesting individual product details.

Collect candidates for a market review

For this workflow, a marketplace analyst calls Ozon Intelligence SR: ozon/product Detail Search API with sku and dateRange to collect candidates for a market review. The result helps choose products for a supplier or competitor review.

Ozon Intelligence SR: ozon/product Detail Search API API FAQ

What does the Ozon Intelligence SR: ozon/product Detail Search API API return?

Use Ozon Intelligence SR: ozon/product Detail Search API through Nexscope with documented parameters, structured results and API key authentication. The documented output includes errcode, errmsg, totalSales, dailySales, totalRevenue, stock, startDate, endDate. It corresponds to the supplied sku, dateRange, uId, memberId. Optional fields can be absent; a missing value should not be interpreted as a measured zero. Example values illustrate the response shape, rather than live account results.

How many credits does the Ozon Intelligence SR: ozon/product Detail Search API API cost?

The current documented cost is Recent Avg. 10 · Range 10–25 credits / call. This is the same cost shown at the top of this page. If a range or estimate is displayed, the final charge depends on the request. Review your available credits and the pricing page before calling the API, and check API usage records for the actual charge.

How do I call the Ozon Intelligence SR: ozon/product Detail Search API API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/sr/ozon/productDetailSearch with your API key as a Bearer token and the JSON inputs shown in API integration. In a compatible MCP client such as Claude or Cursor, connect Nexscope and call nexscope_data_sr_ozon_product_detail_search. The same documented request parameters apply; use Online test to review a request before adding it to your app.

View plans and credits Connect this API with MCP

Try this API

Endpoint

https://api.nexscope.ai/sr/ozon/productDetailSearch

MCP method

nexscope_data_sr_ozon_product_detail_search

Step 1 of 3 · Authenticate

Authentication

All run endpoints require a user API key. Send it as a bearer token in the Authorization header.

Authorization: Bearer nk-xxxxxxxxxxxxxxxxx

Missing or invalid API keys return an authentication error. Manage keys from .

Step 2 of 3 · Send a request

POSThttps://api.nexscope.ai/sr/ozon/productDetailSearch

Run an API

Send a JSON request body using the parameters described below.

Example request

Replace YOUR_API_KEY, then run this command in your terminal.

curl -X POST 'https://api.nexscope.ai/sr/ozon/productDetailSearch' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dateRange": "past_30_days",
  "sku": "175924376"
}'

Step 3 of 3 · Inspect the result

Check the response

Read code for the request status and data for the result. Open the parameter and response reference for the full field definitions.

HTTP status codes

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

View parameters & response Try online

All categories/ Ozon Intelligence SR

POSThttps://api.nexscope.ai/sr/ozon/productDetailSearch

Run this API

Send a JSON request to execute this API and receive the documented response payload.

Open tester

Endpoint

Method	`POST`
Path	`https://api.nexscope.ai/sr/ozon/productDetailSearch`
Auth	`Bearer API key`
Content-Type	`application/json`

Request parameters

Name	Type	Required	Description
`sku`	`string`	required	Product SKU, only one SKU can be queried at a time.
`dateRange`	`string`	optional	Sales volume/metric statistics window: `past_7_days`, `past_30_days`, `past_60_days`, `past_90_days`, `past_180_days`, `past_365_days`. Example: past_30_days
`uId`	`string`	optional	User ID, up to 1000.
`memberId`	`string`	optional	Member ID; a member's unique identifier, the data belongs to this member, the maximum number is 1000.

Code example

{
  "dateRange": "past_30_days",
  "sku": "175924376"
}

Response example

Platform response envelope. code 0 indicates success or acceptance; data contains the business result.

{
  "code": 0,
  "cost": "-1",
  "data": {},
  "msg": null,
  "time": "2026-01-01 00:00:00",
  "traceId": null,
  "ts": "0"
}

Response fields

Response field reference (71 fields)

Name	Type	Required	Description
`code`	`string`	optional	Return code, `"200"` indicates success; returned when successful.
`errcode`	`integer`	optional	Error code, `200` indicates success; only this field may be returned when there is a business error.
`msg`	`string`	optional	Message; Success was `ok`.
`errmsg`	`string`	optional	Error message; success is `ok`, business error is a reason description.
`total`	`integer`	optional	Returns the number of records, 1 for a hit and 0 for a miss.
`totalSales`	`integer`	optional	Total sales within the statistics window.
`dailySales`	`number`	optional	Average sales per day.
`totalRevenue`	`number`	optional	Sales volume within the statistical window, in rubles.
`stock`	`integer`	optional	Inventory.
`startDate`	`string`	optional	Statistics window start date.
`endDate`	`string`	optional	Statistics window end date.
`salesTrendVOList`	`array`	optional	Daily sales data series, the element fields are shown in the table below.
`categoryRanks`	`array`	optional	Product category ranking history, element fields are shown in the table below.
`products`	`array`	optional	List of product details; usually 1 on hit.
`data`	`array`	optional	Return data, the content is exactly the same as `products`.
`columns`	`array`	optional	Column definition, elements containing `field`, `title`, `cellType`, `sortable`, `filterable`.
`type`	`string`	optional	Response display type, such as `productWorkbenches`.
`costTime`	`integer`	optional	The interface consumes time in milliseconds.
`costToken`	`integer`	optional	The number of tokens consumed.
`sku`	`integer`	optional	Product SKU.
`productId`	`integer`	optional	Unified product ID, mapped from `sku`.
`title`	`string`	optional	Product title.
`price`	`number`	optional	Commodity price in rubles.
`currency`	`string`	optional	Currency, fixed to `₽`.
`reviewRating`	`number`	optional	Product ratings.
`rating`	`number`	optional	Unified scoring, mapped from `reviewRating`.
`reviewCount`	`integer`	optional	Number of comments.
`questionsAndAnswers`	`integer`	optional	QA quantity.
`brandName`	`string`	optional	Brand name.
`brand`	`string`	optional	Unified brand, mapped from `brandName`.
`brandId`	`integer`	optional	Brand ID.
`brandUrl`	`string`	optional	Brand link.
`sellerName`	`string`	optional	Seller name.
`sellerId`	`integer`	optional	Seller ID; a negative value indicates a self-operated seller on the Ozon platform.
`fulfillment`	`array`	optional	Product shipping methods, such as `["FBO"]` or `["OZON"]`, may contain multiple values.
`upTime`	`integer`	optional	Shelf time, millisecond timestamp.
`upDays`	`integer`	optional	Number of days on shelf.
`upMonths`	`integer`	optional	Number of months on shelves.
`imageUrl`	`string`	optional	Unified main image URL, mapped from the first image of `imageUrls`.
`imageUrls`	`array`	optional	List of product image URLs.
`productUrl`	`string`	optional	Product URL.
`productPageUrl`	`string`	optional	Unified product page URL, mapped from `productUrl`.
`categoryInfo`	`object`	optional	Product category information and structure are shown in the table below.
`monthlySalesUnits`	`integer`	optional	The unified monthly sales volume is actually equal to `totalSales` in the current statistical window.
`monthlySalesRevenue`	`number`	optional	Unified monthly sales, actually equal to `totalRevenue` in the current statistical window.
`sourceType`	`string`	optional	Data source, fixed to `ozon`.
`weight`	`number`	optional	Product weight in grams; digital/service items may not be returned.
`grossMargin`	`number`	optional	Gross profit margin; some items may not be returned.
`date`	`string`	optional	date.
`sales`	`integer`	optional	Sales volume on the day, `0` indicates no sales volume on the day.
`revenue`	`number`	optional	Sales volume for the day, in rubles.
`price`	`number`	optional	Today's price in rubles.
`stock`	`integer`	optional	Inventory of the day.
`reviewCount`	`integer`	optional	The number of comments as of that day, cumulative value.
`reviewRating`	`number`	optional	Rating as of today.
`date`	`string`	optional	Month or specific day of the month.
`rank`	`integer`	optional	Category ranking.
`count`	`integer`	optional	Statistical count, the caliber is subject to the actual return from the gateway.
`cnTitlePath`	`string`	optional	Chinese category path.
`enTitlePath`	`string`	optional	English category path.
`titlePath`	`string`	optional	Category original path.
`category`	`object`	optional	The final category object, the fields are shown in the table below.
`fullCategoryId`	`array`	optional	Full category ID path, array of strings.
`cnTitle`	`string`	optional	Category Chinese name.
`enTitle`	`string`	optional	Category English name.
`title`	`string`	optional	Category original title.
`level`	`integer`	optional	Category level.
`id`	`string`	optional	Category ID.
`pid`	`string`	optional	Parent category ID.
`crossBorderSellable`	`boolean`	optional	Whether to support cross-border sales.
`disabled`	`boolean`	optional	Whether to deactivate.

Responses

Code	Description
200	HTTP request completed. Check JSON code; only 0 indicates business success or acceptance.
400	Request JSON or required API parameters are invalid.
401	API key is missing, invalid, or cannot be matched to a user.
5xx	API execution or upstream service failed.

Data source, freshness, and limitations

Source, freshness, coverage, rate limits, and estimation notes are not specified in this API definition unless they appear in the request or response field documentation above. Do not assume official marketplace data or real-time freshness when it is not explicitly documented.

Step 1 of 2 · Connect your MCP client

MCP

V2 recommended

Connect remote agents through the standard MCP 2025-11-25 Streamable HTTP endpoint. Use OAuth 2.1 Authorization Code with PKCE, or an API key for compatibility.

POST https://api.nexscope.ai/mcp
MCP-Protocol-Version: 2025-11-25
Content-Type: application/json

Authentication

OAuth clients request the mcp:tools scope. The endpoint's 401 response advertises protected-resource metadata for authorization discovery.

Step 2 of 2 · Call the tool

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_data_sr_ozon_product_detail_search",
    "arguments": {
      "dateRange": "past_30_days",
      "sku": "175924376"
    }
  }
}

Legacy MCP v1

Existing API-key clients can continue using the compatibility endpoint. New integrations should use MCP v2.

GET / POST /mcp/legacy

Online test

Execute the current API with your API key and JSON payload. Online tests use this site's configured API environment; the Endpoint and copyable examples use the public integration address.

17 credits / callAPI usage records

Try it

Send a real request with the same contract shown in the reference.

Endpoint

/sr/ozon/productDetailSearch

MCP method

nexscope_data_sr_ozon_product_detail_search

API key*

JSON payload*

cURL

curl -X POST \
  https://api.nexscope.ai/sr/ozon/productDetailSearch \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "dateRange": "past_30_days", "sku": "175924376" }'

Response

No response yet. Run the request to see the response here.

Use Ozon Intelligence SR: ozon/category Search API through Nexscope with documented parameters, structured results and API key authentication.

Ozon Intelligence SR: ozon/keyword Back Search API

Use Ozon Intelligence SR: ozon/keyword Back Search API through Nexscope with documented parameters, structured results and API key authentication.

Ozon Intelligence SR: ozon/keyword Mining API

Use Ozon Intelligence SR: ozon/keyword Mining API through Nexscope with documented parameters, structured results and API key authentication.

Ozon Intelligence SR: ozon/market Keyword Search API

Use Ozon Intelligence SR: ozon/market Keyword Search API through Nexscope with documented parameters, structured results and API key authentication.

What this API does

Ozon Intelligence SR: ozon/product Detail Search API API use cases

Find products matching a sourcing brief

Compare a product search shortlist

Collect candidates for a market review

Ozon Intelligence SR: ozon/product Detail Search API API FAQ

What does the Ozon Intelligence SR: ozon/product Detail Search API API return?

How many credits does the Ozon Intelligence SR: ozon/product Detail Search API API cost?

How do I call the Ozon Intelligence SR: ozon/product Detail Search API API from my app or an MCP client?

Authentication

Run an API

Example request

Check the response

HTTP status codes

Run this API

Endpoint

Request parameters

Code example

Response example

Response fields

Responses

Data source, freshness, and limitations

MCP

Call a tool

Legacy MCP v1

Online test

Try it

Related APIs