> **For coding agents and LLMs:** This is one Social Fetch marketing page (markdown export). For API orientation start with [`/llms.txt`](https://www.socialfetch.dev/llms.txt); for auth and crawl rules use [`/agents.txt`](https://www.socialfetch.dev/agents.txt); for every operation use [`/llms-endpoints.txt`](https://www.socialfetch.dev/llms-endpoints.txt).

## This page

- **On-site (HTML):** <https://www.socialfetch.dev/platforms/naver/trends-search>
- **Markdown (.mdx) URL:** <https://www.socialfetch.dev/platforms/naver/trends-search.mdx>

---

# Naver Search Trend API

How often Koreans searched Naver for up to five keywords, by day, week or month since 2016.

`GET /v1/naver/trends/search` returns `data.series`, one per keyword, each a list of `points` (`date`, `value`). Values are relative, 0 to 100: 100 is the busiest period of the busiest keyword in the answer.

Filter by `device`, `gender` and `ages`; the default period is the last year.

## Request

- **Endpoint:** `GET /v1/naver/trends/search`
- **Credits:** 1 credit
Failed requests are free
- **Input:** by keywords and period
- **Full reference:** [docs](https://www.socialfetch.dev/docs/api/v1/naver/trends/search/get)
- **Platform page:** [/platforms/naver](https://www.socialfetch.dev/platforms/naver)

## FAQ

### Are these absolute search counts?

No. Values are relative, 0 to 100, across the keywords in one request, the way Naver publishes them.

### How far back does it go?

To January 2016. Set startDate and endDate, and timeUnit to date, week or month.

### Can I compare audiences?

Yes: filter by device, gender and ages and compare the series.

### How many credits does a call cost?

Pricing is documented on the operation in the API registry (shown on this page). Confirm on every response with meta.creditsCharged: that field is the billing source of truth.
