Submit multiple profile URLs in one request. The response returns aDocumentation Index
Fetch the complete documentation index at: https://docs.tumban.com/llms.txt
Use this file to discover all available pages before exploring further.
batch_id immediately; each profile is processed independently and
delivers its own webhook.
Request body
Array of creator profile URLs. Each URL must be a valid HTTP or
HTTPS URL.
HTTPS endpoint Tumban will
POST each result to as profiles
complete. Optional: if omitted, Tumban falls back to the
organization’s default_callback_url.
If neither is set, the batch still runs and individual scans can be
polled via GET /api/v2/scans/{scan_id} — no
webhooks are sent.Arbitrary JSON object applied to every profile in the batch. Echoed
back on each per-profile webhook payload.
Response
UUID of the batch. Use it to fetch aggregate progress via
GET /api/v2/batches/{batch_id}.Always
processing on submission. See
Status values.Count of profiles accepted in the batch.
ISO 8601 UTC timestamp of when Tumban accepted the batch.
ISO 8601 UTC timestamp of the expected completion time. Scales
roughly linearly with batch size at the deployment’s concurrency
cap.
Example
The batch’s
scan_ids are not returned in the response. Read each
per-profile result via the webhook callback or by querying
GET /api/v2/batches/{batch_id} for
aggregate progress.
