# Naver Image Search API (https://www.socialcrawl.dev/platforms/naver/image-search) > Searches Naver Image: image search across crawled Korean web. Returns images under `data.items[]` with `title`, `link` (image URL), `thumbnail` (preview URL), `sizeheight`, and `sizewidth`. Narrow to a size band with `filter`. TL;DR: `GET /v1/naver/image/search` costs 1 credit per call and returns SocialCrawl's unified JSON schema. Single x-api-key auth, 100 free credits on signup. ## Parameters | Parameter | Required | Description | | --- | --- | --- | | `query` | yes | Free-text search term (UTF-8). Required. | | `display` | no | Number of items to return per page. Defaults to 10, cap 100; `display=101` returns 400. | | `start` | no | 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`. | | `sort` | no | 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. (sim \| date) | | `filter` | no | Restrict to an image size band: `all` (default), `large`, `medium`, or `small`. (all \| large \| medium \| small) | | `since` | no | 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`. | | `until` | no | 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`. | | `max_pages` | no | 1 to 50 (default 1, or 50 when `max_items` or `max_credits` is sent). Walk up to this many pages in one call and return the rows from all of them. Each page walked is billed exactly as one call to this endpoint (a cached page is free) and counts against your rate limit; its charge and any refund are recorded under the page's own request id, listed in `data.walk.request_ids`. The walk stops early at the last page, or when the request's time budget runs low; `data.walk.stopped` says why (`end`, `max_pages`, `max_items`, `max_credits`, `time_budget`, `page_error`) and `pagination.next_cursor` continues from where it stopped. | | `max_items` | no | 1 to 5000. Get more in one call: keep walking pages until the response holds at least this many rows, then stop with `data.walk.stopped: "max_items"`. The last page is returned whole (it was billed), so `data.items` can hold up to one page more than this, and `pagination.next_cursor` resumes right after it without skipping a row. Walks up to 50 pages unless `max_pages` says fewer; each page is billed as one call (a cached page is free). Add `max_credits` to cap the spend. A long walk can stop on the time budget first (`"time_budget"`): send the returned cursor with the same params to continue. | | `max_credits` | no | 1 to 100000. The most this call may spend, across every page it walks. A page starts only while the credits already spent plus that page's price (or, when higher, the most any page of this walk has cost) still fit, so the call never goes past it; the walk then stops with `data.walk.stopped: "max_credits"` and the cursor to resume. Sent alone, it walks as far as the budget goes (up to 50 pages). A value below the price of one page is a free 400 whose `error.details.page_credits` names that price. Credits a row join (`include=`) adds are known only once a page has run, so page 1 is checked against its own price. | ## Code example ```bash curl -G "https://www.socialcrawl.dev/v1/naver/image/search" \ --data-urlencode "query=한라산" \ -H "x-api-key: sc_YOUR_API_KEY" ``` ## FAQ ### How do I search Naver images with an API? Send a GET request to /v1/naver/image/search with a keyword in the query parameter. SocialCrawl searches images crawled across the Korean web and returns the image link, a thumbnail URL, and pixel dimensions for each result under data.items. ### What fields does the Naver Image endpoint return? Each item includes title, link (the full-size image URL), thumbnail (a preview URL), and sizeheight and sizewidth in pixels. The dimensions let you filter for high-resolution images before downloading the full-size file. ### Can I sort and paginate Naver image results? Yes. sort accepts sim (relevance, the default) and date (newest first). Use display to set page size and start as the offset to page through more images for the same query beyond the first response. ### What does the Naver Image corpus search across? It searches images indexed from the Korean web, so it surfaces visuals tied to Korean blogs, news, and shopping pages. This makes it a strong source for Korean-context image discovery that general image APIs tend to under-index. ### How much does the Naver Image Search API cost? Each image search costs 1 credit on the standard tier, no matter how many images come back. New accounts get 100 free credits with no credit card required, enough to run roughly 100 image searches before any charge applies. See the full Naver API: https://www.socialcrawl.dev/platforms/naver ## Pricing - Standard endpoints: 1 credit per call - Advanced endpoints: 5 credits per call - Premium endpoints: 10 credits per call - 100 free credits on signup, no credit card required. Cached responses cost 0 credits. Credit packs never expire. - Full pricing: https://www.socialcrawl.dev/pricing ## Explore with AI Questions this API answers, phrased for an AI assistant: - How do I search Korean web images with an API? - What is the SocialCrawl Naver Image Search API?