Submit a single profile URL for ToS compliance analysis. The request 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.
scan_id immediately; processing happens in the background.
Request body
The creator profile URL to analyze. Must be a valid HTTP or HTTPS URL.
HTTPS endpoint Tumban will
POST the result to when the scan
finishes. Optional: if omitted, Tumban falls back to the
organization’s default_callback_url. If
neither is set, the scan still runs and the result is available via
GET /api/v2/scans/{scan_id} — no webhook is sent.Arbitrary JSON object echoed back in the webhook payload and
persisted on the scan record. Use it to thread your own correlation
ids (
reviewer_id, case_id, etc.) through the pipeline.Response
UUID of the scan. Use it to poll
GET /api/v2/scans/{scan_id}.Always
processing on success. See
Status values.ISO 8601 UTC timestamp of when Tumban accepted the scan.
ISO 8601 UTC timestamp of the expected completion time. The scan
typically finishes in under two minutes.
Example
Using the dashboard
Submit a profile URL
In the Submit Scan tile, paste the profile URL into the
Profile URL field. By default the result is delivered via
your organization’s default callback URL.To override per-scan, toggle Send result to callback URL on
and enter a URL in the revealed Callback URL field.
Submit and watch
Click Submit Scan. The new row appears at the top of the
Scans table with status Processing. The page polls in-flight
rows every five seconds and updates them in place. Click the row
once it reaches a terminal status to open
Get scan detail.

