scan_id immediately; processing happens in the background.
The scan mode is selected by the path you call:
| Mode | Endpoint | Behaviour |
|---|---|---|
| Deep | POST /api/v2/scan/deep | Full analysis — profile data plus link traversal, social-media scraping, and external context search. Typically completes in under two minutes. |
| Quick | POST /api/v2/scan/quick | Cheaper and faster — skips link traversal, social-media scraping, and external context search; runs a fast model on the profile data only. Typically completes in about 30 seconds. |
scan_mode field echoes which one ran). The resulting
triage report has the same fields in either mode;
read the coverage object to see which steps a
quick scan skipped. See Scan modes
for the full comparison.
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. A deep scan
typically finishes in under two minutes; a quick scan in about 30
seconds.
Which mode ran:
deep or quick. Echoes the endpoint you called.Example
/api/v2/scan/quick with the same
body. The response is identical except scan_mode is "quick" and
estimated_completion is roughly 30 seconds out:
Errors
| Status | Detail |
|---|---|
| 422 | Body failed schema validation — typically a malformed profile_url. See Errors → validation. |
| 429 | The org’s daily_scan_limit has been hit. Body is a structured object: {"error": "daily_scan_limit_exceeded", "limit": N, "used": N}. See Rate limits. |
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.
Pick a scan mode
Under Scan mode, choose Deep scan (default) or Quick
scan. Deep runs the full pipeline; quick is faster and cheaper
and skips link traversal, social scraping, and external context
search.
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.

