# Naver Search Trend API (https://www.socialcrawl.dev/platforms/naver/search-trend)

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

TL;DR: `GET /v1/naver/search-trend` costs 5 credits per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup.

## Parameters

| Parameter | Required | Description |
| --- | --- | --- |
| `keywords` | no | Comma-separated Korean keywords, up to 20, combined into ONE trend series (volumes summed, not compared). Send this or `groups`. |
| `groups` | no | 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. |
| `start_date` | no | Window start, `YYYY-MM-DD`. Defaults to 12 months before `end_date`. Clamped up to 2016-01-01, the earliest 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) |
| `group_name` | no | Label for the `keywords` series in the response. Defaults to the first keyword. Not used with `groups`. |
| `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-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. |

## Code example

```bash
curl -G "https://www.socialcrawl.dev/v1/naver/search-trend" \
  --data-urlencode "keywords=삼성전자,갤럭시" \
  -H "x-api-key: sc_YOUR_API_KEY"
```

## FAQ

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

See the full Naver API: https://www.socialcrawl.dev/platforms/naver

## Pricing

- Standard endpoints: 1 credit per call
- Advanced endpoints: 5 credits per call
- Premium endpoints: 10 credits per call
- 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire.
- Full pricing: https://www.socialcrawl.dev/pricing

## Explore with AI

Questions this API answers, phrased for an AI assistant:

- How do I get Naver DataLab search trend data through an API?
- Does SocialCrawl have a Naver search trend API for comparing Korean keywords?
- What is the Korean equivalent of the Google Trends API?