ShortMax Scraper

ShortMax Scraper at a glance

ShortMax Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its documented output includes platform, recordtype, id, slug and title, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.40 on paid plans, with smaller per-run or optional feature charges listed on Apify.

Runs on: Apify cloud: console, API, schedules and integrations
Data type: Web data
Pricing: $2.00 per 1,000 results (Free plan), from $1.40 on paid plans
Output: Documented below · JSON, CSV, Excel
Inputs: 17 options

Scrape the ShortMax short-drama catalog: titles, descriptions, creators, view and follow counters, two genre taxonomies, trending rails with rank and episode lists. Catalog, category, genre, trending or pasted links, in 19 site languages. Resume, incremental updates and MCP export.

What ShortMax Scraper can do

Five ways in. Walk the full catalog page by page, follow selected categories or genres (two independent, live-resolved taxonomies), read the homepage trending rails with rail name and position, or paste your own drama links.
Nineteen site languages. The same numeric title id across every localized catalog - collect one language or all of them, with localized titles, synopses and slugs.
Full episode lists. Every enriched record carries its episode list (number + URL) plus the all-episodes link.
Trending rails with rank. The homepage rails come back with the rail name and the exact position of every title in it.
Built for schedules. Incremental mode returns only new and changed titles on recurring runs, and a refused run fails loudly instead of returning an empty dataset.
Honest failures. An unknown category or genre value is named in the error; a refused run never reads as an empty catalog.

Choose what to collect

These inputs let you configure ShortMax Scraper - Short Dramas, Rankings & Episodes. Open the actor on Apify to enter your values and review the current options.

Supported input fields
Input	What it controls
`mode`string	catalog walks the full drama catalog page by page. category walks selected category pages. genre walks selected genre pages (a second, independent taxonomy). trending reads the homepage rails with rail name and position. urls scrapes only the links you paste. Choices: catalog, category, genre, trending, urls
`categories`array	Category slugs, ids or display names, resolved against the live category index when the run starts (example: fantasy). Leave empty to walk every category.
`genres`array	Genre slugs, ids or display names, resolved against the live genre index when the run starts (example: modern). Leave empty to walk every genre.
`language`string	Which localized catalog to read. The stable numeric title id is the same across languages; titles, synopses and slugs are localized. Choices: en, zh-Hans, ja, ko, pt, vi, id, th, es, it, ar, de, fr, zh-Hant, tr, hi, ru, ms, fil
`listingUrls`array	Homepage (trending rails), drama pages (/drama/...), episode pages (/episode/...), all-episodes pages (/episodes/...), category pages (/dramas/-), genre pages (/genres/-) with optional page numbers, and catalog links (/dramas), with an optional language prefix. Each link keeps its own site language. Unsupported links are skipped with a warning.
`maxItems`integer	Maximum number of title records per run. 0 means no limit.
`maxPages`integer	Maximum pages walked per catalog, category or genre scope. 0 means no page cap, so Max items is the only cap that stops a run early.

Show 10 more inputs

More input fields
Input	What it controls
`fetchDetails`boolean	Read each title's drama page for the full description, creator, view/follow counters, tag taxonomy and the episode list. Off = catalog card rows only (title, cover, links).
`resumeFromRunId`string	Run ID whose collected titles should be skipped (for continuing after an interrupted run).
`incrementalMode`boolean	Track state between runs and classify every title as NEW, UPDATED, UNCHANGED or EXPIRED instead of always NEW. Rows already known and unchanged are suppressed. Compared: every returned field except views, viewsDisplay, follows, followsDisplay, rank, section, resultsReturned, releaseDate and releaseDateSource (the last two are derived from the cover, which is compared). Counter ticks, rank and rail changes never mark a title UPDATED. A run capped by Max items or Max pages, cut short by the time limit, or started from a pasted page-2+ list link never marks titles EXPIRED.
`stateKey`string	Named baseline for incremental runs. Leave empty to derive the key from the run scope (mode, categories, genres, language).
`emitUnchanged`boolean	In incremental mode, also push rows that did not change (changeType UNCHANGED).
`emitExpired`boolean	In incremental mode, emit EXPIRED tombstone rows for titles that disappeared from the walked scope.
`ignoreFieldsForChanges`array	Extra field names that must never mark a row UPDATED (counters and rank positions are already excluded by default).
`mcpConnectors`array	Apify MCP connector IDs that receive pushed records while the run executes.
`notionParentPageUrl`string	Notion parent page for the Notion MCP connector.
`maxNotifyListings`integer	Cap on records sent to MCP connectors per run.

Fields in the output

The documented dataset includes the fields below. Availability can depend on the source page and selected mode.

platformplatform

recordTyperecordType

idid

slugslug

titletitle

urlurl

covercover

releaseDatereleaseDate

releaseDateSourcereleaseDateSource

descriptiondescription

genresgenres

categorycategory

Show 24 more fields

genregenre

sectionsection

rankrank

viewsviews

viewsDisplayviewsDisplay

followsfollows

followsDisplayfollowsDisplay

episodesepisodes

episodeUrlepisodeUrl

allEpisodesUrlallEpisodesUrl

creatorcreator

languagelanguage

modemode

extractionPathextractionPath

discoveredFromUrldiscoveredFromUrl

resultsReturnedresultsReturned

detailFetcheddetailFetched

scrapedAtscrapedAt

changeTypechangeType

changedFieldschangedFields

firstSeenAtfirstSeenAt

lastSeenAtlastSeenAt

episodeListepisodeList

episodeNumberepisodeNumber

Example output

An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.

{
  "platform": "ShortMax",
  "id": "43438",
  "title": "The Day I Chose His Roommate",
  "creator": "Elisa",
  "viewsDisplay": "238K",
  "followsDisplay": "79.5K",
  "episodes": 25,
  "genres": [
    {
      "name": "Modern",
      "id": "200052"
    },
    {
      "name": "Fantasy",
      "id": "200070"
    }
  ],
  "url": "https://www.shorttv.live/drama/the-day-i-chose-his-roommate-43438"
}

Ways to use this data

Who: short-drama analysts - track view and follow counters, episode counts and trending positions across the ShortMax catalog on a schedule.
Who: content researchers - collect descriptions, creators and both genre taxonomies for market studies.
Who: localization teams - compare the same title id across 19 site languages.

Before you run

Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.

Questions about this actor

What data does ShortMax Scraper return?

The documented output for ShortMax Scraper includes platform, recordtype, id, slug, title, url, cover and releasedate. Availability of each field depends on the source page and the selected mode.

How much does ShortMax Scraper cost?

It costs $2.00 per 1,000 results on the Apify Free plan and from $1.40 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.

Does it scrape comments or reviews?

No. ShortMax publishes no review, comment or rating surface on its website or in its app (verified October 2026 across the web pages, the community section and the mobile app's full API surface), so there is nothing to collect. Titles, episodes, counters and taxonomies are the catalog's full public depth.

Can I get only new or changed titles on a schedule?

Yes. Turn on Incremental mode and schedule the actor. The first run returns everything matching as NEW; later runs return only NEW and UPDATED records. Compared: every returned field except views, viewsDisplay, follows, followsDisplay, rank, section, resultsReturned, releaseDate and releaseDateSource (the last two are derived from the cover, which is compared). Those excluded fields are still returned in the row; add more with Ignore fields when detecting changes. A run that is capped (Max items or Max pages), cut short by the time limit, or started from a pasted page-2+ list link is a partial scan and never marks titles EXPIRED. Use State key to keep a monitoring campaign stable, and Emit unchanged or Emit expired only if you also want those rows (they return and bill extra rows).

Why did my run fail instead of returning an empty dataset?

A run that never got a single readable answer fails loudly with a connection message instead of reporting an empty catalog; an unknown category or genre value is named in the error rather than silently skipped.

Can I use it with AI agents or MCP?

Yes. Every record is plain JSON over the dataset API, and the MCP connector export sends rows straight into tools like Notion. Point an agent at the dataset items endpoint with the input above.