Naver Shopping Insight Category API
Returns a click-share time series for up to 3 Naver Shopping categories as results[].data[] {period, ratio} pairs. breakdown splits one category by device, gender, or age.
GET /v1/naver/shopping-insight/categoryLast updated November 2026Maintained by the SocialCrawl team
When to use the Naver Shopping Insight Category API
Use it for Korean shopping demand trends by category. It partly covers the gap left by Naver retiring its Shopping search corpus, though it gives trends, not product listings or prices.
From the API reference
Returns a relative click-share time series for up to 3 Naver Shopping categories under data.results[].data[] as {period, ratio} pairs. Set breakdown to split one category by device, gender, or age instead of comparing categories. Partly fills the gap left by Naver retiring its Shopping SEARCH corpus on 2026-07-31: this gives demand and click TRENDS for a category, though not individual product listings or prices, which no Naver API offers any more. ratio is a relative index within the requested window, not an absolute count. Shopping Insight history starts 2017-08-01 (later than search-trend's 2016-01-01); an earlier start_date is clamped up to it. An unknown category id returns no data points and is not charged.
Searching 69 platforms in parallel
What can you do with the Shopping Insight Category API?
The Shopping Insight Category endpoint gives you structured Naver data with computed fields in a single request. No scraping infrastructure to build or maintain.
Example Request
# GET /v1/naver/shopping-insight/category: 5 credits per call. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
# --max-time 60: the API's own time limit for this endpoint.
# --retry 3: retries timeouts, 429 and 5xx, honoring Retry-After.
# -o response.json keeps only the final attempt's body.
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
IDEMPOTENCY_KEY=$(od -An -N16 -tx1 /dev/urandom | tr -d ' \n')
curl -sS --max-time 60 --retry 3 -o response.json \
-H "x-api-key: YOUR_API_KEY" \
-H "Idempotency-Key: $IDEMPOTENCY_KEY" \
"https://www.socialcrawl.dev/v1/naver/shopping-insight/category?category_code=50000000&time_unit=month" && cat response.json# GET /v1/naver/shopping-insight/category: 5 credits per call. Cache hits are free and failed calls are refunded.
# Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
import os
import random
import time
import uuid
import requests
API_KEY = os.environ.get("SOCIALCRAWL_API_KEY", "YOUR_API_KEY")
TIMEOUT_S = 60 # the API's own time limit for this endpoint.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/naver/shopping-insight/category"
def backoff(attempt):
# Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
return 2 ** attempt * (0.5 + random.random() / 2)
def socialcrawl(params):
# One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
idempotency_key = str(uuid.uuid4())
for attempt in range(MAX_RETRIES + 1):
try:
res = requests.get(
URL,
params=params,
headers={"x-api-key": API_KEY, "Idempotency-Key": idempotency_key},
timeout=TIMEOUT_S,
)
body = res.json()
except (requests.RequestException, ValueError):
# A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if attempt == MAX_RETRIES:
raise
time.sleep(backoff(attempt))
continue
if body["success"]:
return body
error = body["error"]
# Branch on error["type"], never on the message text.
if error["type"] == "RESOURCE_NOT_FOUND":
return None # refunded: nothing to read
retry_after = res.headers.get("Retry-After")
# SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
permanent = error["type"] == "SERVICE_UNAVAILABLE" and retry_after is None
if not error.get("retryable") or permanent or attempt == MAX_RETRIES:
raise RuntimeError(f"{error['type']}: {error['message']} (request_id {body['request_id']})")
# Retry-After (seconds) wins; otherwise back off.
time.sleep(float(retry_after) if retry_after else backoff(attempt))
params = {
"category_code": "50000000",
"time_unit": "month",
}
body = socialcrawl(params)
if body is not None:
print(body["data"])// GET /v1/naver/shopping-insight/category: 5 credits per call. Cache hits are free and failed calls are refunded.
// Check the price first for 0 credits: add dry_run=1 to the query. Nothing is fetched or charged.
const API_KEY = process.env.SOCIALCRAWL_API_KEY ?? "YOUR_API_KEY";
const TIMEOUT_MS = 60_000; // the API's own time limit for this endpoint.
const MAX_RETRIES = 3;
type Page = { next_cursor: string | null; has_more: boolean };
type SocialCrawlResponse =
| { success: true; data: any; pagination?: Page; credits_used: number; request_id: string }
| { success: false; error: { type: string; message: string; retryable: boolean }; request_id: string };
const sleep = (ms: number) => new Promise((resolve) => setTimeout(resolve, ms));
// Exponential backoff with jitter: about 1 s, 2 s, then 4 s.
const backoffMs = (attempt: number) => 2 ** attempt * 1000 * (0.5 + Math.random() / 2);
async function socialcrawl(url: URL) {
// One Idempotency-Key per request, reused on every retry, so a retried call is never charged twice.
const idempotencyKey = crypto.randomUUID();
for (let attempt = 0; ; attempt++) {
let res: Response;
let body: SocialCrawlResponse;
try {
res = await fetch(url, {
headers: {
"x-api-key": API_KEY,
"Idempotency-Key": idempotencyKey,
},
signal: AbortSignal.timeout(TIMEOUT_MS),
});
body = (await res.json()) as SocialCrawlResponse;
} catch (error) {
// A timeout, a dropped connection or a non-JSON gateway page: retry with the same key.
if (attempt >= MAX_RETRIES) throw error;
await sleep(backoffMs(attempt));
continue;
}
if (body.success) return body;
// Branch on error.type, never on the message text.
if (body.error.type === "RESOURCE_NOT_FOUND") return null; // refunded: nothing to read
const retryAfter = res.headers.get("Retry-After");
// SERVICE_UNAVAILABLE without Retry-After is a withdrawn endpoint: permanent.
const permanent = body.error.type === "SERVICE_UNAVAILABLE" && retryAfter === null;
if (!body.error.retryable || permanent || attempt >= MAX_RETRIES) {
throw new Error(`${body.error.type}: ${body.error.message} (request_id ${body.request_id})`);
}
// Retry-After (seconds) wins; otherwise back off.
await sleep(retryAfter ? Number(retryAfter) * 1000 : backoffMs(attempt));
}
}
const url = new URL("https://www.socialcrawl.dev/v1/naver/shopping-insight/category");
url.searchParams.set("category_code", "50000000");
url.searchParams.set("time_unit", "month");
const body = await socialcrawl(url);
if (body) console.log(body.data);Parameters
| Parameter | Required | Description |
|---|---|---|
| category_code | Yes | Comma-separated Naver Shopping category ids, up to 3 (e.g. `50000000` for 패션의류). Required. When `breakdown` is set, only the first id is used. Naver publishes no category-list API, so see the platform guide for the id table. |
| start_date | No | Window start, `YYYY-MM-DD`. Defaults to 12 months before `end_date`. Clamped up to 2017-08-01, the earliest Shopping Insight data Naver holds. |
| end_date | No | Window end, `YYYY-MM-DD`. Defaults to today. |
| time_unit | No | Aggregation bucket: `date`, `week`, or `month` (default `month`). (date | week | month) |
| device | No | Restrict to `pc` or `mo` (mobile). Omit for both. (pc | mo) |
| gender | No | Restrict to `f` or `m`. Omit for both. (f | m) |
| ages | No | Comma-separated age buckets: `10`, `20`, `30`, `40`, `50`, `60`. NOTE these differ from `search-trend`, which takes 1-11. |
| breakdown | No | Split a single category by `device`, `gender`, or `age` instead of comparing several categories. (device | gender | age) |
What does the Naver Shopping Insight Category API return?
Every response follows one unified schema. Here is a real, unmodified response body, so you can see the exact fields you get back before spending a credit.
Example response
{
"success": true,
"platform": "naver",
"endpoint": "/v1/naver/shopping-insight/category",
"data": {
"startDate": "2025-10-01",
"endDate": "2026-10-02",
"timeUnit": "month",
"results": [
{
"title": "50000000",
"category": [
"50000000"
],
"data": [
{
"period": "2025-10-01",
"ratio": 93.19497
},
{
"period": "2025-11-01",
"ratio": 100
}
]
}
]
},
"credits_used": 5,
"request_id": "req_example000000",
"cached": false,
"credits_remaining": 9999,
"source": "captured",
"captured_at": "2026-10-02T12:55:40.372Z",
"redacted": true
}Live sample illustrating the unified response shape. Field values reflect the record you query.
How does the Naver Shopping Insight Category API work?
Send a GET request with your API key and get back clean, structured JSON in our unified schema. Supported computed fields are populated when the source provides the required inputs.
Method
GET
Response
JSON
How do you scrape social media data in seconds?
The fastest social media scraping API for developers. Scrape profiles, posts, comments, and analytics from 69 platforms covering 10B+ monthly active users.
One schema, every platform
Query 69 platforms with identical response structures. Write your integration once.
Computed fields, not just scraped
When an endpoint supports these metrics and the source provides the required inputs, the normalized record includes engagement_rate, estimated_reach, content_category, and language. Ready to use.
See your data before you code
Visual Data Explorer. Paste any URL, get rich result cards, sortable tables, CSV export.
import requests
response = requests.get(
'https://www.socialcrawl.dev/v1/tiktok/profile',
params={'handle': 'charlidamelio'},
headers={'x-api-key': 'sc_YOUR_API_KEY'}
)
data = response.json(){
"success": true,
"platform": "tiktok",
"data": {
"author": {
"username": "charlidamelio",
"followers": 152400000
},
"engagement": {
"likes": 12400000000,
"engagement_rate": 0.087
},
"metadata": {
"language": "en",
"content_category": "lifestyle"
}
}
}Have a question? We got answers
Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.
Contact usWhat does the Naver Shopping Insight Category API return?
When should I use the Naver Shopping Insight Category endpoint?
How much does the Naver Shopping Insight Category API cost?
What parameters does the Naver Shopping Insight Category API need?
How do I call the Naver Shopping Insight Category API?
Ask AI about SocialCrawl
Ready to scrape Naver Shopping Insight Category data?
Get your API key and start pulling Naver data in under 60 seconds.
