/naver/blog/posts/search

POST /api/naver/blog/posts/search

Price: 5 credits

Search Naver blog posts by keyword. Returns title, snippet, author, blog name, images, date.

How to use it

Search Naver blog posts by keyword. Order by relevance or newest, and optionally restrict to a date range. Returns each matching post's title, snippet, author nickname and blog name, profile image, thumbnails, post URL, and published timestamp.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "제주도 여행"; minLength: 1)
• count integer required — Max number of results (examples: 20; min: 1; max: 1000)
• sort string — Result ordering (default: "relevance"; one of: "relevance", "recent")
• start_date string nullable — Start date filter (YYYY-MM-DD) (examples: "2026-01-01")
• end_date string nullable — End date filter (YYYY-MM-DD) (examples: "2026-06-30")

Response

• @type string (default: "NaverBlogSearchPost")
• id string required
• blog_id string required
• post_url string required
• post_title string nullable
• description string nullable
• author string nullable
• blog_name string nullable
• profile_image string nullable
• image string nullable
• images array (default: [])
• published_at integer nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.