Nexscope

Ozon Keyword Back Search

Reverse-lookup Ozon and Wildberries search terms for up to 20 SKUs, with volume, rank, exposure, competition, and conversion. Available via REST API or MCP.

CostRecent 47 credits / call
Try online
POST · https://api.nexscope.ai/sr/ozon/keywordBackSearchMCP · nexscope_ozon_keyword_back_search

Choose an integration method

Ozon Intelligence SR

What this API does

Reverse-lookup Ozon and Wildberries search terms for up to 20 SKUs, with volume, rank, exposure, competition, and conversion. The request accepts skuIds, hasVariant, page, page.page, page.pageSize. Its documented result includes advert, avgPrice, ca, categories, cnTitlePath, competingProducts, conversion, conversionSharing.

Ozon Keyword Back Search API use cases

Build a keyword shortlist

To build a keyword shortlist, a marketplace analyst submits skuIds and hasVariant to Ozon Keyword Back Search. The returned advert, avgPrice, ca help choose candidate search terms for further investigation.

Compare search demand signals

A marketplace analyst uses Ozon Keyword Back Search with skuIds and hasVariant to compare search demand signals. The returned advert, avgPrice, ca help compare keyword demand within the requested market scope.

Plan a content or advertising test

For this workflow, a marketplace analyst calls Ozon Keyword Back Search with skuIds and hasVariant to plan a content or advertising test. The result helps select terms for a content or advertising experiment.

Ozon Keyword Back Search API FAQ

What does the Ozon Keyword Back Search API return?

Reverse-lookup Ozon and Wildberries search terms for up to 20 SKUs, with volume, rank, exposure, competition, and conversion. The documented output includes advert, avgPrice, ca, categories, cnTitlePath, competingProducts, conversion, conversionSharing. It corresponds to the supplied skuIds, hasVariant, page, page.page, page.pageSize. 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 Keyword Back Search API cost?

The current documented cost is Recent 47 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 Keyword Back Search API from my app or an MCP client?

Send a POST request to https://api.nexscope.ai/sr/ozon/keywordBackSearch 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_ozon_keyword_back_search. Use the MCP arguments shown in the MCP guide, or switch Online test to MCP to review its request before adding it to your app.

View plans and creditsConnect this API with MCP

Try this API
Endpoint
https://api.nexscope.ai/sr/ozon/keywordBackSearch
MCP method
nexscope_ozon_keyword_back_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/keywordBackSearch

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/keywordBackSearch' \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "hasVariant": 0,
  "page": {
    "orders": [
      {
        "direction": "DESC",
        "field": "searchVolume"
      }
    ],
    "page": 1,
    "pageSize": 5
  },
  "skuIds": [
    "4380710124"
  ]
}'

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

CodeDescription
200Default HTTP response for both success and many business errors. Only outer JSON code 0 indicates success or asynchronous acceptance; inspect data for the result.
429Execution admission rate limit; honor Retry-After when present.
503Execution admission is temporarily unavailable; honor Retry-After when present.
Opt-inX-Nexscope-Http-Status: semantic maps controller-handled business errors to HTTP status on run and task routes. Pre-authentication failures, such as a missing API key (code 11209), may still return HTTP 200 before this mapping. Always check the outer JSON code; malformed requests and infrastructure failures may also return non-200 HTTP responses.
All categories/ Ozon Intelligence SR

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_ozon_keyword_back_search",
    "arguments": {
      "hasVariant": 1,
      "historyDate": "2026-02",
      "matchType": 1,
      "page": {
        "page": 1,
        "pageSize": 20
      },
      "skuIds": [
        175924376
      ],
      "type": [
        "0"
      ]
    }
  }
}

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/keywordBackSearch
MCP method
nexscope_ozon_keyword_back_search
cURL
curl -X POST \
  https://api.nexscope.ai/sr/ozon/keywordBackSearch \
  -H "Authorization: Bearer nk-..." \
  -H "Content-Type: application/json" \
  -d '{ "hasVariant": 0, "page": { "orders": [ { "direction": "DESC", "field": "searchVolume" } ], "page": 1, "pageSize": 5 }, "skuIds": [ "4380710124" ] }'
Response
No response yet. Run the request to see the response here.

Related APIs