100 free credits. No credit card required.Start building
Logo
Naver logo
100 free credits. No credit card required

Naver Search Trend API

Returns search-interest series as results[].data[] {period, ratio} pairs: one summed series for keywords, or up to 5 groups on one scale. ratio is a relative index, not a count.

GET /v1/naver/search-trend

Last updated November 2026Maintained by the SocialCrawl team

When to use the Naver Search Trend API

Use it for Korean search demand over time, the Naver equivalent of Google Trends. To compare terms, put them in one call as groups; two separate calls are never on the same scale.

From the API reference

Returns relative search-interest time series for Korean keywords from Naver Data Lab, one series per keyword group, under data.results[].data[] as {period, ratio} pairs. This is Korea's equivalent of Google Trends, and for the Korean market it is the more meaningful signal because Naver carries the majority of Korean search. keywords form ONE combined series (their volumes are summed). To compare topics, send groups instead: up to 5 groups in one call, one series each, and Naver scales them together so they are directly comparable. IMPORTANT: ratio is a RELATIVE index (the busiest series in the request peaks at 100), not a search count, so two different requests are NOT comparable. gender, ages and device filter the whole request, so compare demographic segments by the shape of their curves, not their levels. Periods Naver omits for low volume come back as ratio: 0. Naver counts whole weeks (Monday to Sunday) and months; the one still in progress carries partial: true. History starts 2016-01-01; an earlier start_date is clamped up to it. A request with no measurable volume in any series returns no data points and is not charged.

Searching 69 platforms in parallel

·TikTok logoTikTok·Instagram logoInstagram·YouTube logoYouTube·Facebook logoFacebook·X logoX·LinkedIn logoLinkedIn·Reddit logoReddit·Threads logoThreads·Pinterest logoPinterest·Twitch logoTwitch·Truth Social logoTruth Social·Snapchat logoSnapchat·Kick logoKick·Bluesky logoBluesky·Kwai logoKwai·Rumble logoRumble·Spotify logoSpotify·Apple Music logoApple Music·TikTok Shop logoTikTok Shop·Amazon Shop logoAmazon Shop·Google Shopping logoGoogle Shopping·Trustpilot logoTrustpilot·TripAdvisor logoTripAdvisor·Yelp logoYelp·Linktree logoLinktree·Komi logoKomi·Pillar logoPillar·lnk.bio logolnk.bio·Facebook Ads logoFacebook Ads·Google Ads logoGoogle Ads·LinkedIn Ads logoLinkedIn Ads·Google Search logoGoogle Search·Google News logoGoogle News·Finance logoFinance·Polymarket logoPolymarket·Tavily logoTavily·Hacker News logoHacker News·GitHub logoGitHub·Perplexity logoPerplexity·Naver logoNaver·Utility logoUtility·Universal Search logoUniversal Search
·TikTok logoTikTok·Instagram logoInstagram·YouTube logoYouTube·Facebook logoFacebook·X logoX·LinkedIn logoLinkedIn·Reddit logoReddit·Threads logoThreads·Pinterest logoPinterest·Twitch logoTwitch·Truth Social logoTruth Social·Snapchat logoSnapchat·Kick logoKick·Bluesky logoBluesky·Kwai logoKwai·Rumble logoRumble·Spotify logoSpotify·Apple Music logoApple Music·TikTok Shop logoTikTok Shop·Amazon Shop logoAmazon Shop·Google Shopping logoGoogle Shopping·Trustpilot logoTrustpilot·TripAdvisor logoTripAdvisor·Yelp logoYelp·Linktree logoLinktree·Komi logoKomi·Pillar logoPillar·lnk.bio logolnk.bio·Facebook Ads logoFacebook Ads·Google Ads logoGoogle Ads·LinkedIn Ads logoLinkedIn Ads·Google Search logoGoogle Search·Google News logoGoogle News·Finance logoFinance·Polymarket logoPolymarket·Tavily logoTavily·Hacker News logoHacker News·GitHub logoGitHub·Perplexity logoPerplexity·Naver logoNaver·Utility logoUtility·Universal Search logoUniversal Search
·TikTok logoTikTok·Instagram logoInstagram·YouTube logoYouTube·Facebook logoFacebook·X logoX·LinkedIn logoLinkedIn·Reddit logoReddit·Threads logoThreads·Pinterest logoPinterest·Twitch logoTwitch·Truth Social logoTruth Social·Snapchat logoSnapchat·Kick logoKick·Bluesky logoBluesky·Kwai logoKwai·Rumble logoRumble·Spotify logoSpotify·Apple Music logoApple Music·TikTok Shop logoTikTok Shop·Amazon Shop logoAmazon Shop·Google Shopping logoGoogle Shopping·Trustpilot logoTrustpilot·TripAdvisor logoTripAdvisor·Yelp logoYelp·Linktree logoLinktree·Komi logoKomi·Pillar logoPillar·lnk.bio logolnk.bio·Facebook Ads logoFacebook Ads·Google Ads logoGoogle Ads·LinkedIn Ads logoLinkedIn Ads·Google Search logoGoogle Search·Google News logoGoogle News·Finance logoFinance·Polymarket logoPolymarket·Tavily logoTavily·Hacker News logoHacker News·GitHub logoGitHub·Perplexity logoPerplexity·Naver logoNaver·Utility logoUtility·Universal Search logoUniversal Search
·TikTok logoTikTok·Instagram logoInstagram·YouTube logoYouTube·Facebook logoFacebook·X logoX·LinkedIn logoLinkedIn·Reddit logoReddit·Threads logoThreads·Pinterest logoPinterest·Twitch logoTwitch·Truth Social logoTruth Social·Snapchat logoSnapchat·Kick logoKick·Bluesky logoBluesky·Kwai logoKwai·Rumble logoRumble·Spotify logoSpotify·Apple Music logoApple Music·TikTok Shop logoTikTok Shop·Amazon Shop logoAmazon Shop·Google Shopping logoGoogle Shopping·Trustpilot logoTrustpilot·TripAdvisor logoTripAdvisor·Yelp logoYelp·Linktree logoLinktree·Komi logoKomi·Pillar logoPillar·lnk.bio logolnk.bio·Facebook Ads logoFacebook Ads·Google Ads logoGoogle Ads·LinkedIn Ads logoLinkedIn Ads·Google Search logoGoogle Search·Google News logoGoogle News·Finance logoFinance·Polymarket logoPolymarket·Tavily logoTavily·Hacker News logoHacker News·GitHub logoGitHub·Perplexity logoPerplexity·Naver logoNaver·Utility logoUtility·Universal Search logoUniversal Search
Naver API

What can you do with the Search Trend API?

The Search Trend 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/search-trend: 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 10: this endpoint's measured p99 latency x 1.5.
# --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 10 --retry 3 -o response.json \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Idempotency-Key: $IDEMPOTENCY_KEY" \
  "https://www.socialcrawl.dev/v1/naver/search-trend?keywords=%EC%82%BC%EC%84%B1%EC%A0%84%EC%9E%90%2C%EA%B0%A4%EB%9F%AD%EC%8B%9C&time_unit=month" && cat response.json
# GET /v1/naver/search-trend: 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 = 10  # this endpoint's measured p99 latency x 1.5.
MAX_RETRIES = 3
URL = "https://www.socialcrawl.dev/v1/naver/search-trend"


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 = {
    "keywords": "삼성전자,갤럭시",
    "time_unit": "month",
}
body = socialcrawl(params)
if body is not None:
    print(body["data"])
// GET /v1/naver/search-trend: 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 = 10_000; // this endpoint's measured p99 latency x 1.5.
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/search-trend");
url.searchParams.set("keywords", "삼성전자,갤럭시");
url.searchParams.set("time_unit", "month");

const body = await socialcrawl(url);
if (body) console.log(body.data);

Parameters

ParameterRequiredDescription
keywordsNoComma-separated Korean keywords, up to 20, combined into ONE trend series (volumes summed, not compared). Send this or `groups`.
groupsNoUp to 5 keyword groups, each its own series on one shared scale: separate groups with `|` and the keywords inside a group with `,`, for example `손 다한증,발 다한증|미라드라이|암내,액취증`. Each series is named by its first keyword. Up to 20 keywords per group. Send this or `keywords`, not both.
start_dateNoWindow start, `YYYY-MM-DD`. Defaults to 12 months before `end_date`. Clamped up to 2016-01-01, the earliest data Naver holds.
end_dateNoWindow end, `YYYY-MM-DD`. Defaults to today.
time_unitNoAggregation bucket: `date`, `week`, or `month` (default `month`). (date | week | month)
group_nameNoLabel for the `keywords` series in the response. Defaults to the first keyword. Not used with `groups`.
deviceNoRestrict to `pc` or `mo` (mobile). Omit for both. (pc | mo)
genderNoRestrict to `f` or `m`. Omit for both. (f | m)
agesNoComma-separated age-band codes, `1` to `11`: `1` 0-12, `2` 13-18, `3` 19-24, `4` 25-29, `5` 30-34, `6` 35-39, `7` 40-44, `8` 45-49, `9` 50-54, `10` 55-59, `11` 60+. Several codes are SUMMED into one audience, not split. NOTE this endpoint uses different codes from `shopping-insight/*`, which takes 10/20/30/40/50/60.
Example Response

What does the Naver Search Trend 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/search-trend",
  "data": {
    "startDate": "2025-10-01",
    "endDate": "2026-10-02",
    "timeUnit": "month",
    "results": [
      {
        "title": "삼성전자",
        "keywords": [
          "삼성전자",
          "갤럭시"
        ],
        "data": [
          {
            "period": "2025-10-01",
            "ratio": 46.29239
          },
          {
            "period": "2025-11-01",
            "ratio": 40.46304
          }
        ]
      }
    ]
  },
  "credits_used": 5,
  "request_id": "req_example000000",
  "cached": false,
  "credits_remaining": 9999,
  "source": "captured",
  "captured_at": "2026-10-02T12:48:02.787Z",
  "redacted": true
}

Live sample illustrating the unified response shape. Field values reflect the record you query.

API Details

How does the Naver Search Trend 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

Why SocialCrawl

Why use SocialCrawl for Naver Search Trend data?

We handle the complexity of Naver data extraction so you can focus on building. Unified schema, AI enrichment, and zero platform logic in your code.

Developer First

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()
[ .JSON ]
{
  "success": true,
  "platform": "tiktok",
  "data": {
    "author": {
      "username": "charlidamelio",
      "followers": 152400000
    },
    "engagement": {
      "likes": 12400000000,
      "engagement_rate": 0.087
    },
    "metadata": {
      "language": "en",
      "content_category": "lifestyle"
    }
  }
}
+ 69 platforms
FAQ

Have a question? We got answers

Find answers to frequently asked questions about SocialCrawl's API, pricing, and capabilities.

Contact us
What is the Naver DataLab search trend API?
It returns relative search-interest time series for Korean keywords from Naver Data Lab (검색어트렌드), as period and ratio pairs under data.results[].data[]. Naver carries the majority of Korean search, so for the Korean market it is the more meaningful counterpart to Google Trends.
How do I call the Naver search trend API?
Send a GET request to /v1/naver/search-trend with an x-api-key header and either keywords (up to 20, combined into one series) or groups (up to 5 groups). Set start_date, end_date and time_unit (date, week or month, default month) to choose the window.
Can I compare several keywords on one scale?
Yes. Send groups, separating groups with | and the keywords inside a group with a comma, for example groups=손 다한증,발 다한증|미라드라이. Each group becomes its own series and Naver scales them together, so the curves are directly comparable. Keywords sent through keywords are summed into a single series instead.
Does the Naver search trend API give search volume numbers?
No. ratio is a relative index in which the busiest series in the request peaks at 100, so it is not a search count and two different requests are not comparable. For absolute monthly Google volume use /v1/google/keyword-volume.
Can I filter Naver search trends by device, gender or age?
Yes. device takes pc or mo, gender takes f or m, and ages takes codes 1 to 11 for fine age bands (1 is 0 to 12, 11 is 60 and over). The filters apply to the whole request, so compare segments by the shape of their curves rather than their levels.
How far back does the data go and what does a call cost?
History starts on 2016-01-01, and an earlier start_date is clamped up to it. Each call costs 5 credits on the advanced tier, and a request with no measurable volume in any series returns no data points and is not charged. Credits for failed or empty calls are refunded automatically.

Ask AI about SocialCrawl

Ready to scrape Naver Search Trend data?

Get your API key and start pulling Naver data in under 60 seconds.

Start for free

🤖 AI agent or LLM? Read this page as markdown