# Naver Shopping API — Products, Prices & Stores (`gauravlabs/naver-shopping-api`) Actor

Search Naver Shopping with Korean keywords, price filters and pagination. Export product prices, stores, brands, images and review counts. Charged per successful page, not per product.

- **URL**: https://apify.com/gauravlabs/naver-shopping-api.md
- **Developed by:** [Gaurav Kumar Choudhary](https://apify.com/gauravlabs) (community)
- **Categories:** E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 successful shopping requests

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Naver Shopping API — Products, Prices & Stores

Search Naver Shopping with Korean or English product keywords. Export normalized product listings as JSON, CSV or Excel through Apify.

### Pricing

**$2 per 1,000 successfully parsed search pages ($0.002 per request), on every plan. No Actor start fee and no per-product fee.** Each pagination page is a separate request. Failed reads or invalid responses do not incur the request event charge. A valid empty search still counts as one request. Pricing is per page, not per Actor run: one run can fetch multiple pages.

Request up to 40 products per page. Actual counts depend on Naver, duplicates and filters; 40 products are not guaranteed. At 40 products on every page, 1,000 requests could return 40,000 products for $2 in event charges. This is an illustration, not a promised yield. Check the run's spending limit before starting.

### Example

```json
{"query":"해리슨 ASA1001","minPrice":15500,"maxPrice":169500,"maxPages":1,"maxItems":40}
```

Use `maxPages` to paginate, `startPage` to begin later, and `maxItems` to cap exports. Results are deduplicated by product ID within a run. Stop conditions include the page/item limits, repeated products, source exhaustion and run spending limit. If a later page fails, earlier results remain available with a warning in the summary. `nextPage` is a best-effort page-level continuation, not a cursor: stopping within a page can omit its remaining products when resuming at the next page.

### Data and limitations

Available fields include product ID/title, KRW prices, brand/maker, image, store, product URL, category path, rating, review count, delivery fee, source URL and fetch time. Missing fields are null. Ratings/review counts are listing metadata, not full review text. This Actor does not fetch product detail pages, historical prices, stock guarantees, Naver Maps, News or Blogs. Results remain in the source language and may vary over time. Prices should be verified before purchase.

Product rows are in the dataset. A summary with successful request count, source-reported total, warnings and next page is saved in the key-value store under `OUTPUT`. Invalid input and first-page failures fail the run with a safe message.

Use only for authorized collection of publicly available data and comply with applicable laws and site terms. There is currently no additional per-account trial quota. Service authentication is configured privately by the owner and is not an input field.

# Actor input Schema

## `query` (type: `string`):

A Korean or English product keyword, e.g. 해리슨 ASA1001 or 아이폰.

## `minPrice` (type: `integer`):

Optional minimum product price in Korean won.

## `maxPrice` (type: `integer`):

Optional maximum product price in Korean won.

## `sort` (type: `string`):

The requested Naver Shopping result order.

## `productSet` (type: `string`):

Search all products, comparison models, or store listings.

## `startPage` (type: `integer`):

First page to request. Page numbers start at one.

## `pageSize` (type: `integer`):

Requested page size. The source may return fewer products.

## `maxPages` (type: `integer`):

Each successfully parsed page costs $0.002. Pages may contain fewer products than requested.

## `maxItems` (type: `integer`):

Stop exporting after this many unique products.

## Actor input object example

```json
{
  "query": "해리슨 ASA1001",
  "sort": "rel",
  "productSet": "total",
  "startPage": 1,
  "pageSize": 40,
  "maxPages": 1,
  "maxItems": 40
}
```

# Actor output Schema

## `products` (type: `string`):

Normalized product rows.

## `summary` (type: `string`):

Page count, total matches, warnings and next page.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "query": "해리슨 ASA1001"
};

// Run the Actor and wait for it to finish
const run = await client.actor("gauravlabs/naver-shopping-api").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "query": "해리슨 ASA1001" }

# Run the Actor and wait for it to finish
run = client.actor("gauravlabs/naver-shopping-api").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "해리슨 ASA1001"
}' |
apify call gauravlabs/naver-shopping-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gauravlabs/naver-shopping-api"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/bpJyWF9Ca9lvT5mh1/builds/z1jaeSqkvqHNl13ws/openapi.json