DramaWave.tv Scraper — Short-Drama Catalog, Genres & Episodes avatar

DramaWave.tv Scraper — Short-Drama Catalog, Genres & Episodes

Pricing

from $2.00 / 1,000 results

Go to Apify Store
DramaWave.tv Scraper — Short-Drama Catalog, Genres & Episodes

DramaWave.tv Scraper — Short-Drama Catalog, Genres & Episodes

Scrape the dramawave.tv short-drama catalog in 19 languages: titles, synopses, genres, episode lists and the originating platform (ReelShort, FreeReels, PineDrama). Public-JSON based (no browser) — fast and cheap.

Pricing

from $2.00 / 1,000 results

Rating

0.0

(0)

Developer

SignalBench

SignalBench

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

13 days ago

Last modified

Categories

Share

Scrape the dramawave.tv short-drama catalog in 19 languages: titles, synopses, genres, episode lists, paywall shape, and — most usefully — which platform each title was originally published on. API-first (reads the site's own public JSON, no browser), so runs are fast, cheap, and reliable. Export as JSON, CSV, Excel, or XML, or pull straight through the Apify API into your app, agent, notebook, or spreadsheet.

⚠️ Read this first: which "DramaWave" is this?

This Actor scrapes dramawave.tv, a third-party short-drama aggregator that re-hosts other platforms' catalogs.

It is NOT the DramaWave mobile app published by Skywork AI (mydramawave.com, App Store / Google Play). That product has no public web catalog at all — its official site is a bare landing page with no title listing — so there is nothing there to scrape.

Every row this Actor returns is attributed in the platform field to the platform it actually came from: ReelShort, FreeReels, PineDrama, and others depending on language. If you need first-party ReelShort or DramaBox data with real engagement counts, use the dedicated ReelShort and DramaBox scrapers instead — and dedupe against them before merging this dataset in.

No per-datapoint games, never charged for failures. Flat $2 per 1,000 titles ($0.002 each), billed only per title actually stored. Empty, invalid, or failed lookups are never stored and never charged — a no-result search costs $0.00.

What it scrapes

FieldDescription
platform / platformSlugThe originating platform the title was re-hosted from (ReelShort, FreeReels, PineDrama, …) — the single most useful field on this site
id / uniqueKey / languageNumeric ID plus the cross-language-safe {lang}:{id} key
title / slug / urlLocalized title, slug, and canonical URL
descriptionFull localized synopsis (details mode)
genres / tags / primaryGenreGenre names, their slugs, and the single primary genre (details mode)
episodes + episodeList[]Episode count, and optionally the full list — number, title, duration, free/locked
status / audioTypeongoing / completed; subtitled vs dubbed
pricingMode / freeEpisodesPaywall shape, e.g. first_free with 12 free episodes
coverCover image URL, CDN transform params stripped for full resolution
releaseDateISO-8601 — but see the honesty notes below
trendRank / trendWatchSecondsTrending mode only

Honesty notes — what this source cannot give you

These are measured facts about the site, not caveats-in-case. They're here so you don't build on data that isn't there:

  • views is effectively dead. Across 124 sampled English titles, zero had a non-zero view count; the site-wide maximum observed anywhere was 560. It is emitted as-is and must not be used for ranking. trendWatchSeconds is never aliased into it — different unit entirely.
  • follows is always null. The site has no follow/subscriber concept. Nothing is substituted for it.
  • cast is always []. The field exists in the site's schema but is unpopulated (0 of 32 sampled titles), and its 54 actor pages 404.
  • rating is meaningless. Nearly every title shows a default 4.8 with ratingsCount: 0. The count is emitted so you can see that for yourself.
  • releaseDate is dramawave.tv's ingest date, not the original platform's release date.
  • The genre taxonomy is noisy — it contains untranslated i18n placeholders, Portuguese names leaking into English responses, and a few person names used as genres. Genre slugs are language-specific.
  • Each language is a separate catalog. The same drama appears once per language with a different numeric ID and a different localized slug. Dedupe on uniqueKey; there is no reliable cross-language join key.
  • The smaller language catalogs are not reliably in that language. Rows served under e.g. lang=ar frequently carry Portuguese, Malay or English titles and English genre names. language faithfully reports which catalog the row came from — it is not a guarantee about the text. English and Portuguese, the two largest catalogs, are consistent.

Modes

  • Full catalog — pages through every title in the chosen language(s).
  • By genre — server-side filtered by genre slug (language-specific). An unknown slug fails immediately with the live list of valid ones.
  • By source platform — one originating platform's re-hosted catalog, e.g. reelshort (~2,820 English titles), freereels (~3,550).
  • Search — free-text title search.
  • Trending — the site's own top-40 ranking. ⚠️ This measures dramawave.tv's own traffic, which is tiny (the #1 title accrues roughly eight hours of total viewing per day). It is not a proxy for real platform popularity, and it isn't the default mode for that reason.
  • Specific title URLs — scrape exactly the URLs you provide. Both /{lang}/drama/{slug} and the prefix-less Portuguese /drama/{slug} work.

Cost control

maxItems is a hard cap — 1 stored title = 1 charge. Turning Include genres, synopsis & full metadata off halves the request count (the listing endpoint alone has no synopsis or genres) for a faster, cheaper run.

Input example

{
"mode": "creator",
"language": ["en"],
"creatorSlugs": ["reelshort"],
"maxItems": 200,
"includeDetails": true
}

Output example

{
"source": "dramawave.tv",
"platform": "FreeReels",
"platformSlug": "freereels",
"id": 43295,
"uniqueKey": "en:43295",
"title": "A Fortune Fell Into My Hands",
"slug": "a-fortune-fell-into-my-hands",
"url": "https://dramawave.tv/en/drama/a-fortune-fell-into-my-hands",
"language": "en",
"views": 0,
"follows": null,
"likesCount": 0,
"episodes": 66,
"genres": ["Identity Twist", "Revenge"],
"tags": ["identity-twist", "revenge"],
"primaryGenre": "Revenge",
"releaseDate": "2026-08-21T17:31:43-03:00",
"cast": [],
"cover": "https://static-v1.mydramawave.com/vt/prod/cover/b9f00c4f-42d5-4aa7-9c1a-011da8046eb5.jpg",
"description": "Poor rural student Chen Fei discovers he is the lost heir to a billion-dollar fortune…",
"rating": 4.8,
"ratingsCount": 0,
"status": "ongoing",
"audioType": "leg",
"pricingMode": "first_free",
"freeEpisodes": 12,
"episodeList": [],
"scrapedAt": "2026-08-21T21:21:33.520Z"
}

Scope & compliance

  • Catalog metadata only. The site's video-stream endpoints (/api/dramas/hls, /api/dramas/dbx) are never requested, no authenticated route is ever touched, and no comments or user data are collected.
  • The catalog endpoints used here are explicitly allow-listed in the site's robots.txt. Trending is the one exception — it is not allow-listed, which is why it is opt-in rather than the default.
  • Requests are capped at 120/minute with a default concurrency of 5, because this is a small single-operator site.
  • Cover images are emitted as URLs only and are never re-hosted. They are hotlinked by the site from the originating platforms' CDNs and may rotate.