Nexscope logo

Ozon Keyword Back Search API

REST API and MCP service documentation generated from server-side API definitions. Responses shown here are the direct payload returned by each API execution.

API selector
Keyword & Search Demand

API overview

Seerfar Ozon keyword reverse lookup: reverse-looks up Ozon (and Wildberries) search keywords by a list of product SKUs (up to 20), returning which search terms those products appear under (organic/ad search terms), with multi-dimensional filtering by search volume, growth, product count, seller count, competitor count, natural rank, ad rank, exposure, conversion, cart-add conversion, etc. Each keyword carries monthly search volume, growth, market space, competitor/seller counts, average price, cart-add conversion, top products, and organic/ad channel, rank, exposure, and conversion (dimension) market profiles. Use for Ozon keyword reverse lookup, listing keyword optimization, competitor traffic word mining, and ad keyword analysis.

Try this API
Endpoint
https://claw-callback.nexscope.ai/api/skill-api/v1/skills/ozon-keyword-back-search/run
MCP method
nexscope_ozon_keyword_back_search

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 .
POSThttps://claw-callback.nexscope.ai/api/skill-api/v1/skills/ozon-keyword-back-search/run

Run an API

Request parameters documented by ecommerce.ozon-keyword-back-search.

Slugozon-keyword-back-search
HeadersAuthorization: Bearer nk_...
Content-Type: application/json
Request bodyAPI-specific JSON object.
Response bodyDirect API response payload. No data/result wrapper is added.

Status codes

CodeDescription
200API executed successfully. Body is the direct response payload.
400Request JSON or required API parameters are invalid.
401API key is missing, invalid, or cannot be matched to a user.
5xxAPI execution or upstream service failed.

Example request

curl -X POST https://api.nexscope.ai/api/skill-api/v1/skills/ozon-keyword-back-search/run \
  -H "Authorization: Bearer nk_xxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{   "type": [],   "matchType": 1,   "hasVariant": 1,   "page": {     "pageSize": 10,     "page": 1   },   "skuIds": [     "175924376"   ],   "historyDate": "2026-01-01" }'
All categories/ Keyword & Search Demand

Related APIs

MCP

Use the MCP endpoint when an agent needs to discover and call API tools with JSON-RPC.

GET /api/skill-api/v1/mcp
POST /api/skill-api/v1/mcp
Authorization: Bearer nk_xxxxxxxxxxxxxxxxx
Content-Type: application/json

Call a tool

{
  "jsonrpc": "2.0",
  "id": "tool-call-1",
  "method": "tools/call",
  "params": {
    "name": "nexscope_ozon_keyword_back_search",
    "arguments": {
      "type": [],
      "matchType": 1,
      "hasVariant": 1,
      "page": {
        "pageSize": 10,
        "page": 1
      },
      "skuIds": [
        "175924376"
      ],
      "historyDate": "2026-01-01"
    }
  }
}

Online test

Execute the current API with your API key and JSON payload.

Try it

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

Endpoint
https://claw-callback.nexscope.ai/api/skill-api/v1/skills/ozon-keyword-back-search/run
MCP method
nexscope_ozon_keyword_back_search
cURL
curl -X POST \
  https://claw-callback.nexscope.ai/api/skill-api/v1/skills/ozon-keyword-back-search/run \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "type": [], "matchType": 1, "hasVariant": 1, "page": { "pageSize": 10, "page": 1 }, "skuIds": [ "175924376" ], "historyDate": "2026-01-01" }'
Response
No response yet. Run the request to see the response here.