NAVER Python API Docs | dltHub
Build a NAVER-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
NAVER Open API provides a suite of services including search, machine translation, maps, and user authentication APIs for developers. The REST API base URL is https://openapi.naver.com and requests require either client ID/secret headers or an OAuth 2.0 Bearer token in the header.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading NAVER data in under 10 minutes.
What data can I load from NAVER?
Here are some of the endpoints you can load from NAVER:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| blog | v1/search/blog.json | GET | items | Search blog posts |
| news | v1/search/news.json | GET | items | Search news articles |
| book | v1/search/book.json | GET | items | Search book information |
| encyc | v1/search/encyc.json | GET | items | Search encyclopedia entries |
| cafearticle | v1/search/cafearticle.json | GET | items | Search cafe articles |
| kin | v1/search/kin.json | GET | items | Search knowledge iN entries |
| webkr | v1/search/webkr.json | GET | items | Search web documents |
| image | v1/search/image.json | GET | items | Search images |
| shop | v1/search/shop.json | GET | items | Search shopping products |
How do I authenticate with the NAVER API?
NAVER Open API authentication primarily uses two HTTP headers: 'X-Naver-Client-Id' and 'X-Naver-Client-Secret' for standard service APIs, or OAuth 2.0 access tokens in the 'Authorization' header for user-login APIs. NAVER Cloud Platform specific APIs utilize 'X-NCP-APIGW-API-KEY-ID' and 'X-NCP-APIGW-API-KEY' headers.
1. Get your credentials
- Log in to the NAVER Developers console or NAVER Cloud Platform console. 2. Navigate to the 'Application' or 'My Application' management menu. 3. If you have not yet registered an application, create a new one by providing the required details. 4. Once registered, click on the application name to view its details. 5. Locate the 'Authentication Information' section or tab within the application settings. 6. Click on the 'Authentication Information' button or link to display the 'Client ID' and 'Client Secret' values. Copy these values for your integration.
2. Add them to .dlt/secrets.toml
[sources.naver_source] client_id = "REPLACE_ME"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the NAVER API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python naver_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline naver_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset naver_data The duckdb destination used duckdb:/naver.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads authorize and token (for Login/OAuth API services) or search and me (for general/profile API services) from the NAVER API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def naver_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://openapi.naver.com", "auth": {"type": "bearer", "token": client_id}, }, "resources": [ {"name": "blog", "endpoint": {"path": "v1/search/blog.json", "data_selector": "items"}}, {"name": "news", "endpoint": {"path": "v1/search/news.json", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="naver_pipeline", destination="duckdb", dataset_name="naver_data", ) load_info = pipeline.run(naver_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("naver_pipeline").dataset() sessions_df = data.blog.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM naver_data.blog LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("naver_pipeline").dataset() data.blog.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load NAVER data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for NAVER?
Request dlt skills, commands, AGENT.md files, and AI-native context.