# NetShort Drama Episodes Scraper (`spider_studio/netshort-drama-episodes`) Actor

Get every episode ID and detailed episode metadata for one or more NetShort short dramas.

- **URL**: https://apify.com/spider_studio/netshort-drama-episodes.md
- **Developed by:** [Tarique](https://apify.com/spider_studio) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 netshort episode detail results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

### NetShort Drama Episodes Scraper: export complete episode lists

**NetShort Drama Episodes Scraper** retrieves the full episode list and available episode metadata for one or more NetShort dramas. Give this **NetShort episode API** a list of drama IDs to collect episode numbers, episode IDs, drama information, subtitles, and available playback details in a structured export.

### 🧭 Explore more NetShort Actors

Build your NetShort workflow with these companion Actors:

| Actor | What it does |
| --- | --- |
| 🔎 [NetShort Search Scraper](https://apify.com/spider_studio/netshort-search) | Find dramas by keyword and collect their IDs. |
| ✨ [NetShort Recommendations Scraper](https://apify.com/spider_studio/netshort-recommendations) | Discover dramas from the For You feed. |
| 🔗 [NetShort 1080p Video URL Scraper](https://apify.com/spider_studio/netshort-drama-playback-urls) | Extract playback links for free-user episodes. |
| 🎬 [NetShort Video Downloader](https://apify.com/spider_studio/netshort-video-downloader) | Download full dramas or selected episodes as MP4 files, with automatic unlocking and quality up to 1080p. |

### Why collect a NetShort episode directory?

An episode directory helps you understand the size and structure of a drama before planning further work. Build a catalog, match episodes to an editorial schedule, check metadata coverage, or prepare a list for licensed localization and media review.

You do not need to know the first episode ID or enter every episode separately. Supply the drama ID and review the resulting directory. If some episode details are unavailable, the output reports the coverage so you can distinguish a complete list from complete media access.

### How to get every episode of a NetShort drama

1. Find a current drama ID using NetShort Search Scraper or Recommendations Scraper.
2. Open this Actor's **Input** tab and add the ID to `short_play_ids`.
3. Add more IDs if you want to process several dramas together.
4. Click **Start**, then open the Dataset.
5. Review episode counts and available details before exporting the results.

### Input: one or more NetShort drama IDs

`short_play_ids` is required and accepts 1–1,000 numeric IDs written as strings. Repeated IDs in the same list are processed once. Keep quotation marks around large IDs when sending JSON from an application.

```json
{
  "short_play_ids": ["1894649662050627585"]
}
```

Use a current ID from search results. If a drama is unavailable or an ID no longer resolves, try a different title or check the input for typing errors.

### Episode metadata output

Each episode produces one Dataset row. This makes it easier to filter successful details, inspect missing information, and match each charged result to a specific episode. **Result summary** reports saved and unavailable results for each requested drama.

| Field | Meaning |
| --- | --- |
| `short_play_id` | Requested drama ID. |
| `drama_title` | Drama title when available. |
| `episode_id` and `episode_no` | Episode identifier and position. |
| `success` and `error` | Whether details were available, and a reason when they were not. |
| `catalog` | Available episode directory information. |
| `detail` | Available episode details, or `null`. |

Simplified output excerpt:

```json
{
  "short_play_id": "1894649662050627585",
  "episode_id": "1894649662692356102",
  "episode_no": 1,
  "success": true,
  "error": null,
  "catalog": {},
  "detail": {}
}
```

The empty objects above stand for the available metadata. Export as JSON, CSV, Excel, or HTML; JSON preserves nested fields. Locked or unavailable details remain visible as rows with `success: false` and `detail: null`, without a result charge. A drama that cannot be found is reported in the summary and may produce no episode rows.

### Pricing and run costs

Free-plan users pay **$0.003 per successfully saved episode detail result**. Paid-plan users pay **$0.002 per successfully saved episode detail result**. The billing unit is one episode with available details, not one drama or one request. Directory-only entries with unavailable details, failed requests, and duplicate episodes within the same run do not incur a result charge. Apify platform costs are additional. Review the **Pricing** and run **Usage** tabs before a larger batch.

### Does a complete episode list mean every video is downloadable?

No. A directory can include episodes whose playback or detailed metadata is unavailable. Check the reported coverage and episode errors. Use **NetShort Video Downloader** when you want MP4 files, including full-series or selected-episode downloads.

### Can I use this as a NetShort episode API?

Yes. The **Apify API** tab includes examples for applications and automation tools. You can schedule catalog checks and connect the exported episode information to your own data workflow.

### Support and responsible use

Open the **Issues** tab with the run link and affected drama ID if you need help. Use NetShort information and media only where you have permission and follow applicable terms and copyright rules.

# Actor input Schema

## `short_play_ids` (type: `array`):

Required NetShort short-play IDs. Exact duplicates are removed in first-seen order.

## Actor input object example

```json
{
  "short_play_ids": [
    "1894649662050627585"
  ]
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

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

No description

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

// Run the Actor and wait for it to finish
const run = await client.actor("spider_studio/netshort-drama-episodes").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 = { "short_play_ids": ["1894649662050627585"] }

# Run the Actor and wait for it to finish
run = client.actor("spider_studio/netshort-drama-episodes").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 '{
  "short_play_ids": [
    "1894649662050627585"
  ]
}' |
apify call spider_studio/netshort-drama-episodes --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,spider_studio/netshort-drama-episodes"
        }
    }
}
```

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/I7RBu85yhrGEZawiY/builds/eu0NtecNxoA2xmcvH/openapi.json
