Available in Classic and VPC
Get blog search results from NAVER Search.
Blog searches use the Search API, which has a daily call limit of 25,000.
Request
This section describes the request format. The method and URI are as follows:
| Method | URI |
|---|---|
| GET | /search/v1/blog |
Request headers
For information about the headers common to NAVER API HUB, see NAVER API HUB request headers.
Request query parameters
You can use the following query parameters with your request:
| Field | Type | Required | Description |
|---|---|---|---|
query |
String | Required | Search keyword
|
display |
Integer | Optional | Number of search results to display at a time
|
start |
Integer | Optional | Search start location
|
sort |
String | Optional | How to sort search results
|
format |
String | Optional | Response format
|
Request example
The request example is as follows:
curl --location --request GET https://naverapihub.apigw.ntruss.com/search/v1/blog?query=Coffee&display=2&start=1&sort=date&format=json
--header X-NCP-APIGW-API-KEY-ID: {Client ID}
--header X-NCP-APIGW-API-KEY: {Client Secret}
Response
This section describes the response format.
Response body
The response body includes the following data:
| Field | Type | Required | Description |
|---|---|---|---|
lastBuildDate |
String | - | Time the search results were generated |
total |
Integer | - | Total number of search results |
start |
Integer | - | Starting location for the search |
display |
Integer | - | Number of search results to display at a time |
items |
Array | - | List of individual search results: items |
items
The following describes items.
| Field | Type | Required | Description |
|---|---|---|---|
title |
String | - | Blog post title
|
link |
String | - | Blog post URL |
description |
String | - | Passage information summarizing the blog post content
|
bloggername |
String | - | Name of the blog that contains the blog post |
bloggerlink |
String | - | Address of the blog that contains the blog post |
postdate |
String | - | Date the blog post was written |
Response status codes
The following describes the response status codes.
| HTTP status code | Code | Message | Description |
|---|---|---|---|
| 400 | SE01 |
Incorrect query request | Check for errors in the API request URL, such as the protocol or parameters. |
| 400 | SE02 |
Invalid display value. | Check that the display value is within the allowed range. |
| 400 | SE03 |
Invalid start value | Check that the start value is within the allowed range. |
| 400 | SE04 |
Invalid sort value | Check the sort value for typos. |
| 400 | SE06 |
Malformed encoding | Encode the search keyword in UTF-8. |
| 404 | SE05 |
Invalid search API | Check the API request URL for typos. |
| 500 | SE99 |
System error | An error occurred internally on the server. |
For information about the HTTP status codes common to all NAVER API HUB, see NAVER API HUB response status codes.
Response example
The response example is as follows:
{
"lastBuildDate": "Thu, 11 Jun 2026 19:14:42 +0900",
"total": 56692992,
"start": 1,
"display": 2,
"items": [
{
"title": "How to choose <b>coffee</b> beans and tips for getting started with a home coffee setup",
"link": "https://blog.naver.com/{blogId}/{logNo}",
"description": "Today, I've summarized the criteria for choosing <b>coffee</b> beans. Depending on acidity and body... ",
"bloggername": "{Blog name}",
"bloggerlink": "blog.naver.com/{blogId}",
"postdate": "20260611"
},
{
"title": "Review of a local <b>coffee</b> spot",
"link": "https://blog.naver.com/{blogId}/{logNo}",
"description": "Here’s a review of a <b>coffee</b> specialty shop I visited over the weekend. Both the pour-over and lattes... ",
"bloggername": "{Blog name}",
"bloggerlink": "blog.naver.com/{blogId}",
"postdate": "20260611"
}
]
}