naver

Get Naver search-volume trend for Korean keywords (검색어트렌드)

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.

get/naver/search-trend

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/naver/search-trend
  • Auth: API key in header x-api-key

Query parameters

keywordsstring

Comma-separated Korean keywords, up to 20, combined into ONE trend series (volumes summed, not compared). Send this or groups. (one of: keywords, groups; at least one required)

groupsstring

Up 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. (one of: keywords, groups; at least one required)

start_datestring

Window start, YYYY-MM-DD. Defaults to 12 months before end_date. Clamped up to 2016-01-01, the earliest data Naver holds.

end_datestring

Window end, YYYY-MM-DD. Defaults to today.

time_unit'date' | 'week' | 'month'

Aggregation bucket: date, week, or month (default month).

group_namestring

Label for the keywords series in the response. Defaults to the first keyword. Not used with groups.

device'pc' | 'mo'

Restrict to pc or mo (mobile). Omit for both.

gender'f' | 'm'

Restrict to f or m. Omit for both.

agesstring

Comma-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.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "naver",
  "endpoint": "/v1/naver/search-trend",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  }
}

Changes

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