# Naver Video Search Collector (`daftvader/naver-video-search-collect-a8afe8da-af37-545b-a27f-8c664a91ad9e`) Actor

- **URL**: https://apify.com/daftvader/naver-video-search-collect-a8afe8da-af37-545b-a27f-8c664a91ad9e.md
- **Developed by:** [Sam Towers](https://apify.com/daftvader) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.80 / 1,000 apify-default-dataset-items

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 Video Search Collector

Collect public Naver video-search results for one or more keywords and store
normalized records in the Actor's default dataset. The Actor uses direct HTTP
requests and does not require customer credentials, browser automation, or a
proxy.

### Input

```json
{
  "keywords": ["python", "data engineering"],
  "maxItemsPerKeyword": 100,
  "sort": "relevance",
  "concurrency": 3
}
```

`keywords` accepts one non-empty string or a non-empty list of strings.
`maxItemsPerKeyword` ranges from 1 to 1000. `sort` is `relevance`, `date`, or
`views`; `concurrency` ranges from 1 to 10. Defaults are 100, `relevance`, and
3 respectively.

### Output

Each dataset item contains `title`, `url`, `thumbnail`, `duration` (seconds),
`channel`, `official`, `uploadDate`, `viewCount`, `sourcePlatform`, `keyword`,
`ranking`, `sort`, and the UTC `collectedAt` timestamp. Optional source metadata
may be `null`, and duplicate URLs are emitted only once per run.

### Pricing behavior

The Actor uses pay-per-event charging: one `apify-actor-start` event is emitted
when a run starts, and one `apify-default-dataset-item` event is emitted after
each dataset item is successfully stored. Failed persistence is not charged.
The configured monetary price is managed by the platform release configuration.

### Limitations

Naver's server-rendered result markup and sort parameters are undocumented and
may change. Results and optional metadata depend on what Naver exposes publicly
at run time. Results are deduplicated across all supplied keywords, so the first
keyword that finds a URL owns that output item.

### Functional input contract

`CollectorConfig.from_mapping` accepts:

- `keywords`: one non-empty string or a non-empty list of strings;
- `maxItemsPerKeyword`: integer 1–1000 (default 100);
- `sort`: `relevance`, `date`, or `views` (default `relevance`);
- `concurrency`: integer 1–10 (default 3).

### Functional output contract

Each record contains `title`, `url`, `thumbnail`, duration in seconds, `channel`,
`official`, `uploadDate`, integer `viewCount`, `sourcePlatform`, `keyword`,
one-based `ranking`, `sort`, and ISO-8601 `collectedAt`. Missing optional source
fields are represented by `null` (and `official` defaults to `false`). URLs are
deduplicated across the entire run.

The caller supplies asynchronous `persist(record)` and `charge(event)` adapters.
The collector calls `charge("apify-default-dataset-item")` only after the
corresponding `persist` succeeds. The platform adapter owns the run-start event.

# Actor input Schema

## `keywords` (type: `array`):

One or more Naver video-search keywords.

## `maxItemsPerKeyword` (type: `integer`):

Maximum number of results to store for each keyword.

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

Naver ordering to request.

## `concurrency` (type: `integer`):

Maximum concurrent keyword requests.

## Actor input object example

```json
{
  "keywords": [
    "python"
  ],
  "maxItemsPerKeyword": 100,
  "sort": "relevance",
  "concurrency": 3
}
```

# Actor output Schema

## `results` (type: `string`):

Normalized Naver video-search results.

# 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 = {
    "keywords": [
        "python"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("daftvader/naver-video-search-collect-a8afe8da-af37-545b-a27f-8c664a91ad9e").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 = { "keywords": ["python"] }

# Run the Actor and wait for it to finish
run = client.actor("daftvader/naver-video-search-collect-a8afe8da-af37-545b-a27f-8c664a91ad9e").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 '{
  "keywords": [
    "python"
  ]
}' |
apify call daftvader/naver-video-search-collect-a8afe8da-af37-545b-a27f-8c664a91ad9e --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,daftvader/naver-video-search-collect-a8afe8da-af37-545b-a27f-8c664a91ad9e"
        }
    }
}
```

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/oTimbtAzVfDgdh4M1/builds/4daCulGESQpb0Seyl/openapi.json