Apify integration
for BatScrape actors.

Run an actor in Apify Console

No code is required. You need an Apify account, and each run is charged to it.

1. Open the actor on Apify and sign in. The TikTok Shop Scraper, Reddit Scraper, Threads Scraper, Realtor.com Scraper, TikTok Scraper, Douyin Scraper and FollowScores Scraper pages link to each listing and explain its input.
2. Fill in the Input tab, then click Start.
3. Follow the run in its log. When it finishes, the results appear in the Output tab, and the Storage tab holds the full dataset.

To reuse an input, click Save as a new task. You can run a task from Console, a schedule or the API. See Apify’s guides to running Actors and tasks.

Run an actor through the Apify API

The run-sync-get-dataset-items endpoint starts a run, waits for it to finish and returns the dataset items. Send the actor’s input as JSON, and put your API token, found under Settings → API & Integrations in Apify Console, in the Authorization header. Keep the token out of client-side code.

curl -X POST \
  "https://api.apify.com/v2/actors/batscrape~douyin-scraper/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"keywords":["coffee"],"maxResultsPerQuery":20}'

In API paths the actor ID takes a tilde, as in batscrape~douyin-scraper. A run longer than 300 seconds returns HTTP 408 here, so start a longer one with the Run Actor endpoint and read its dataset when it finishes. See the endpoint reference.

Export the dataset

Each run writes its results to a dataset, one item per row. In Console, click Export on the Output tab or on the dataset’s page, and choose JSON, CSV, XML, Excel, HTML table, RSS or JSONL.

Through the API, the Get dataset items endpoint takes a format of json, jsonl, csv, html, xlsx, xml or rss. The call above accepts it too: add ?format=csv for CSV. fields and omit pick the columns.

How long Apify keeps a run’s dataset depends on your plan. Name a dataset to keep it indefinitely. See Apify’s dataset guide.

Schedule runs and add webhooks

A schedule starts an actor or a saved task on a cron expression, in the time zone you choose. Run the actor once before scheduling it, then enable the schedule: new schedules start disabled.

A webhook, set on the actor’s or task’s Integrations tab, sends an HTTP POST to your URL when a run event occurs, such as ACTOR.RUN.SUCCEEDED or ACTOR.RUN.FAILED. The default payload includes the run ID, so your endpoint can fetch the results. A webhook can arrive more than once, so handle duplicates.

Send results to automation tools

Apify’s own integrations pass a run’s results to other apps. They are part of the Apify platform, not BatScrape features, and work with any actor in your account, ours included.

• Make: an Apify module runs actors, watches run status and returns results in a scenario.
• Zapier: starts actors or tasks, fetches dataset items and triggers a Zap when a run finishes, so results can go on to apps such as Google Sheets.
• n8n: the Apify node works as a trigger or an action, on n8n Cloud or self-hosted.
• Google Drive: uploads a run’s results to your Drive, by default after each successful run.
• Slack: sends run notifications and results to Slack.

Apify documents more, from Airtable to Snowflake, in its integrations guide.