apik
JOIN WAITLIST
TRACKING SHEET — 2 SOURCE(S)

Naver Trends API changes

Naver Trends (Naver DataLab search-trend API on the Naver Developers platform). Signals: the platform notice/announcements feed (covers DataLab incl. service-termination notices) and the DataLab API doc page snapshot. No OpenAPI/llms.txt is published.

LAST CHECKED
Jun 20, 2026
TRACKED SINCE
Jun 20, 2026
CHANGES / 90D
11
BREAKING / 90D
0
DETECTED CHANGES — MOST RECENT
  1. INFO Change Jun 20, 2026

    [네이버 로그인] openapi.naver.com 서버 변경 작업 (완료 및 일정 변경) 안내

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/naver-trends/charges
    + POST /v1/naver-trends/payments  (auth scope changed)
  2. INFO Change Jun 20, 2026

    [네이버 로그인] openapi 도메인 인증서 발급 정책 변경에 따른 사전점검 및 조치 안내

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/naver-trends/charges
    + POST /v1/naver-trends/payments  (auth scope changed)
  3. INFO Change Jun 20, 2026

    [네이버 로그인] TLS 1.1 이하 버전 지원 중단 안내 ('25.08.19.~)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/naver-trends/charges
    + POST /v1/naver-trends/payments  (auth scope changed)
  4. INFO Change Jun 20, 2026

    TLSv1.2 미만(TLSv1.0/1.1) 지원 종료 안내 (2025년 9월 29일 적용)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/naver-trends/charges
    + POST /v1/naver-trends/payments  (auth scope changed)
  5. INFO Change Jun 20, 2026

    블로그 RSS 서비스 이용 안내 (HTTP/1.0 미지원)

    - "version": "2024-09-30"
    + "version": "2025-06-01"
    - POST /v1/naver-trends/charges
    + POST /v1/naver-trends/payments  (auth scope changed)

How to track Naver Trends API changes

The Naver Trends API evolves without warning — endpoints move, parameters change, auth scopes tighten and old fields get deprecated. apik.dev watches the public Naver Trends API documentation for you: we scrape it on a schedule, diff every revision and grade each change as breaking or informational. Instead of re-reading the Naver Trends changelog by hand, you get a clean, dated record of exactly what changed — and why it matters.

Get notified when the Naver Trends API changes

Subscribe to Naver Trends and apik pages you by email or webhook the moment a change is detected — with the full diff, a severity grade and a short migration summary. Filter to Naver Trends breaking changes and deprecations only, so you hear about what will actually break your integration and nothing else.

FREQUENTLY ASKED — NAVER TRENDS
How do I track Naver Trends API changes?
apik.dev tracks the Naver Trends API for you. We scrape the public Naver Trends API documentation on a schedule, diff every revision and grade what changed — so you never have to re-read the Naver Trends changelog by hand. Subscribe once and we monitor it continuously.
How do I get notified when the Naver Trends API changes?
When apik detects a Naver Trends API change, you're notified by email or webhook within hours — with the full diff, a severity grade (breaking vs. informational) and a short migration summary. You can choose to be alerted on breaking changes only.
What kinds of Naver Trends API changes does apik detect?
Endpoint changes, base-URL changes, authentication and parameter changes, schema changes and deprecations. Every Naver Trends API change is categorised and severity-graded so you can triage at a glance.
How often is the Naver Trends API checked for changes?
apik re-checks the public Naver Trends documentation on a daily schedule. The most recent check for Naver Trends ran on Jun 20, 2026.
FIG. — GET PAGED NEXT TIME

Don't find out from a 500.

apik is in private development. Join the waitlist and we'll email you the moment Naver Trends tracking goes live — full diffs, severity grading and migration summaries.

No spam — one email when we launch. Unsubscribe anytime.

Naver Trends official docs ↗