Search Naver Image

Free-text search term (UTF-8). Required.

Number of items to return per page. Defaults to 10, cap 100; display=101 returns 400. Native upstream page-size param. Send the universal limit instead: the API maps it to this name for you.

1-indexed offset for pagination. Defaults to 1, cap 1000; start=1001 is a 400 that costs nothing, and the page that reaches rank 1000 is the last one (has_more: false). Past rank 100, sim and point pages repeat Naver's top 100: those rows are removed and counted in _warnings (recycled_rows), and an emptied page is free. Page deeper with sort=date. Native upstream cursor param. Send the universal cursor instead: the API maps it to this name for you.

Sort order. Accepted values: sim|date. Defaults to sim (relevance) when the corpus supports sort. Values outside this corpus's domain are rejected with a 400 before any upstream call. date lists the newest first, but Naver serves only the first 1,000 rows of a query (start caps at 1000), so on a common word it reaches back hours or days, not months, and on a multi-word query Naver also loosens the match.

Restrict to an image size band: all (default), large, medium, or small.

Only rows published on or after this date: YYYY-MM-DD (midnight UTC) or an ISO 8601 timestamp. Rows older than it are left off each page. This list is not in date order, so the walk does not stop at the date: keep following next_cursor, and each page costs what a page costs even when every row on it is filtered out. A row with no date is kept. published_after, start_date, from_date, publish_time (yesterday, this-week, this-month, last-3-months, last-6-months) and max_age_days are accepted and applied as since.

Only rows published on or before this date: YYYY-MM-DD (that whole UTC day is included) or an ISO 8601 timestamp. Newer rows are left off each page and the walk does not stop, so older pages follow. A row with no date is kept. published_before, end_date and to_date are accepted and applied as until.

Universal pagination cursor. Send pagination.next_cursor from the previous response back verbatim: the API maps it to this endpoint's native start (offset style). You never construct, decode, or look up a cursor. Omit it for page 1.

Universal page size. The API maps it to this endpoint's native display.

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.