Naver DataLab Search Trend (English)

Apify Actor that wraps NAVER API HUB Search Trend — the official Naver integrated-search trend API — and presents it in English.

Type snail cream, retinol, or 달팽이크림 and get a clean time series. This is not a scraper. It calls only documented official HTTP APIs.

Shopping / book / academic search APIs ended 31 July 2026 with no replacement. This Actor is Search Trend only.

What the index means

The official field is ratio. Naver scales it so the largest value among all keyword groups in that one HTTP request equals 100. It is not absolute search volume and not comparable to Google Trends, nor across different Actor runs / request batches.

This Actor copies that value to index and stamps every row:

index is relative to the peak (=100) inside this request group, not absolute search volume

Official HUB wording: 「구간별 검색량의 상대적 비율 - 구간별 결과에서 가장 큰 값을 100으로 설정한 상댓값」.

The official API accepts at most 5 keywordGroups per request. Keywords beyond that are split into further calls. Only keywords that share a batch sit on the same 0–100 scale.

Confirmed official API (fetched 18 Aug 2026)

Item	Official value
Method + URL	POST https://naverapihub.apigw.ntruss.com/search-trend/v1/search
Headers	X-NCP-APIGW-API-KEY-ID, X-NCP-APIGW-API-KEY, Content-Type: application/json
Required body	startDate, endDate (yyyy-mm-dd, from 2016-01-01), timeUnit (date | week | month), keywordGroups
keywordGroups	max 5 pairs; each has groupName + keywords (max 20 strings)
Optional	device: pc | mo (omit = all); gender: m | f (omit = all); ages: official codes 1–11
Response	results[].data[].period, results[].data[].ratio
HTTP 429	official: daily allowance exceeded (호출 한도 초과)

Sources:

• https://api.ncloud-docs.com/docs/naver-api-hub-overview
• https://api.ncloud-docs.com/docs/naver-api-hub-search-trend
• https://api.ncloud-docs.com/docs/naver-api-hub-search-trend-examples

What changed in 2026 (do not use developers.naver.com)

Per Naver notice 32530:

Date	What happened
25 Jun 2026	NAVER API HUB launched on NAVER Cloud Platform
31 Jul 2026	Developers Center blocked new applications for Search, Search Trend, Shopping Insight. Shopping / book / academic search APIs ended with no replacement.
30 Jun 2027	Developers Center keys fade out; HUB only after that

This Actor never calls https://openapi.naver.com/v1/datalab/search and never sends X-Naver-Client-Id. New keys must come from the NCP console.

How to get keys (NCP console — not developers.naver.com)

1. Sign up / log in at NAVER Cloud Platform.
2. Console → region & platform → Menu → All Services → Application Services → NAVER API HUB.
3. Application → Application 등록.
4. Enable 검색어 트렌드 / Search Trend.
5. Open the app → API 관리 → 인증 정보.
6. Copy Client ID and Client Secret.

Paste them into this Actor as:

Actor secret	NCP field
NAVER_CLIENT_ID	Client ID (X-NCP-APIGW-API-KEY-ID)
NAVER_CLIENT_SECRET	Client Secret (X-NCP-APIGW-API-KEY)

Do not create a new Search Trend app on https://developers.naver.com — new applications have been blocked since 31 Jul 2026.

English vs Korean keywords

Naver Search Trend indexes Naver integrated search. Korean (Hangul) terms such as 달팽이크림 match how Koreans actually search.

• Default: English is sent as-is. snail cream is queried as snail cream.
• For Korean-market research, type Hangul yourself (달팽이크림, 레티놀).
• Optional translateEnglish uses NCP Papago Translation (a different NCP product, own Client ID / Secret as PAPAGO_CLIENT_ID / PAPAGO_CLIENT_SECRET). Papago on developers.naver.com ended 29 Feb 2024 and is never called. If Papago keys are missing or the call fails, the original keyword is kept (translated=false) and the run continues.

Input

Field	Required	Default	Notes
keywords	yes	—	Array of strings, English or Korean. Capped at 50.
startDate	yes	prefill last 12 months	YYYY-MM-DD, not before 2016-01-01
endDate	yes	prefill yesterday	YYYY-MM-DD
timeUnit	no	week	date | week | month
device	no	all (omit)	pc | mo
gender	no	all (omit)	m | f
ages	no	all (omit)	Official codes 1–11 only
translateEnglish	no	false	Optional NCP Papago; see above
maxKeywords	no	50	Actor cap, not a Naver field

Example input

{
  "keywords": ["snail cream", "retinol", "달팽이크림"],
  "startDate": "2025-08-18",
  "endDate": "2026-08-17",
  "timeUnit": "week",
  "device": "all",
  "gender": "all",
  "ages": ["4", "5", "6"],
  "translateEnglish": false
}

Output

One dataset row per keyword × period:

{
  "input": "달팽이크림",
  "queryKo": "달팽이크림",
  "translated": false,
  "period": "2026-03-01",
  "index": 100.0,
  "timeUnit": "week",
  "device": "all",
  "gender": "all",
  "ages": ["4", "5", "6"],
  "note": "index is relative to the peak (=100) inside this request group, not absolute search volume"
}

Key-value store file summary.json: per-keyword peak period, a short English gloss (input when the term was Latin-script; Korean search term: … when it was Hangul), batch count, and warnings.

How to deploy (student)

This repo is not published to Apify Store. You push it to your account.

1. Naver keys — follow How to get keys. Enable Search Trend only. (Shopping search is gone.)

2. Apify account — https://console.apify.com/ sign up. Install Apify CLI.

3. From this directory:

   pip install -r requirements.txt
   pytest
   apify login
   apify push
   

4. In Apify Console → this Actor → Settings → Environment variables (secrets):

   • NAVER_CLIENT_ID = NCP API HUB Client ID
   • NAVER_CLIENT_SECRET = NCP API HUB Client Secret
   • Optional: PAPAGO_CLIENT_ID / PAPAGO_CLIENT_SECRET only if you turn on translateEnglish

5. Run from the generated input UI.

Local run without publishing:

export NAVER_CLIENT_ID=...
export NAVER_CLIENT_SECRET=...
apify run -p

Pricing suggestion (PPE)

.actor/pay_per_event.json defines event keyword-series at $0.03 (suggested band $0.01–$0.05 per keyword time series). Enable pay-per-event in Actor monetization settings after apify push. The code charges keyword-series once per completed keyword when the run is in PPE mode.

Legal

Official API wrapper. No HTML scraping, no undocumented endpoints, no shopping-search fallback. You must accept Naver / NCP API terms. Do not claim the index is absolute volume.

What we could not verify

• Exact daily free quota number on API HUB Search Trend after the 2026 paid-plan review (HUB docs say 429 = daily allowance exceeded; they do not publish a single integer on the Search Trend page). Developers Center’s old “1,000 calls/day” figure is not used as a HUB limit here.
• Whether a given English brand name has meaningful Naver volume (often it does not — use Hangul).
• Live calls against your account (no keys on this box; tests are mocked HTTP).

Local tests

pip install -r requirements.txt
pytest

Tests mock HTTP. They never send real keys and never hit Naver.