Keyword & Search Demand

Ozon Market Keyword Search

Nexscope Ozon market hot keyword search: filters Ozon (and Wildberries) market keywords by multi-dimensional metrics including search volume, growth, product count, seller count, competitor count, price, sales, conversion concentration, etc. Each keyword carries monthly search volume, growth, market space, competitor/seller counts, average price, cart-add conversion, top products, and market profile. Use for Ozon keyword selection, blue-ocean keyword mining, and market opportunity analysis. Trigger when the user mentions Ozon hot keywords, Ozon keyword market analysis, Ozon keyword selection, Ozon blue-ocean keywords, Ozon search volume, Wildberries keywords, Nexscope Ozon, Ozon market keyword search, Ozon keyword research, blue ocean keywords Ozon. Also trigger when the intent is to filter Ozon market keywords by metrics and view market profiles, even without explicitly mentioning Nexscope.

post/api/skill-api/v1/skills/ozon-market-keyword-search/run

Request

  • Base URL: https://api.nexscope.ai
  • URL: https://api.nexscope.ai/api/skill-api/v1/skills/ozon-market-keyword-search/run
  • Auth: HTTP bearer

Headers

X-Nexscope-Http-Status'legacy' | 'semantic'

Use semantic for HTTP error statuses on run and task-result requests. Without this header v1 retains legacy status behavior. The JSON envelope is unchanged; code 0 means success or acceptance, not asynchronous completion.

Request body

keywordsstring[]

Keyword array (max 1000), used with matchType

matchTypeinteger

Keyword match mode: 0 exact, 1 fuzzy

searchDatestring

Query date yyyy-MM-dd (e.g., 2026-04-01); defaults to last 30 days if omitted; passing 2026-04-01 queries March 2026 data

uIdstring

User ID

memberIdstring

Member ID (a unique member identifier; data is attributed to memberId)

Example request

{
  "searchDate": "2026-01-01",
  "page": {
    "page": 1,
    "pageSize": 10
  },
  "keywords": [
    "phone case"
  ],
  "uId": "example-id",
  "matchType": 1,
  "categories": []
}

Response

Successful response.

codeinteger required

0 means accepted or successful; nonzero is a platform error.

msgstring nullable required
tsstring required

Epoch milliseconds.

timestring required

Server local time: yyyy-MM-dd HH:mm:ss.

coststring required

Elapsed milliseconds, never credits; -1 outside web requests.

traceIdstring nullable required

Example response

{
  "data": {
    "total": 1,
    "data": [],
    "costTime": 1,
    "costToken": 1
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.