test

Under maintenance

Try for free

Test

Pricing

Pay per usage

Rating

0.0

(0)

Developer

👁 Big Soup

Big Soup

Maintained by Community

Actor stats

Bookmarked

Total users

Monthly active users

7 days ago

Last modified

Scrape Batch Orchestrator

Submit a batch of targets and get the scraped results back — either synchronously (the run waits and returns the results) or asynchronously (the run accepts the batch and delivers the results to your webhook when they're ready).

Input

See the Input tab for the full schema. In short:

Field	Required	Description
`target_app`	yes	Which app to scrape. Currently: `youtube`.
`payload`	yes	Array of targets — YouTube `@handle`s or channel URLs. 1–100 items.
`webhook`	no	HTTPS URL to deliver the results to. Requires `secret`.
`secret`	with `webhook`	Key used to encrypt the results delivered to your webhook.
`metadata`	no	Opaque string echoed back to you.

Output

A dataset record:

Sync (no webhook): { batch_id, status, total, cached, completed, failed, skipped, results }, where results is an array of { handle, email }.
Async (webhook): { batch_id, status: "accepted", total, ... } — the full results are delivered to your webhook when ready.

Modes

Without a webhook the run waits for results and returns them. There is a time limit, so very large batches may return partial results — use a webhook for those.
With a webhook the run accepts the batch and returns immediately; results are POSTed to your webhook on completion, encrypted with your secret.

Webhook delivery

When you provide a webhook + secret, the results are POSTed to your URL encrypted so only you can read them. See the secret field on the Input tab for the exact decryption steps.