When a scan reaches a terminal status (Documentation Index
Fetch the complete documentation index at: https://docs.tumban.com/llms.txt
Use this file to discover all available pages before exploring further.
completed,
completed_with_partial, or failed), Tumban issues a POST to the
scan’s callback_url with a JSON body. Headers:
Content-Type: application/jsonX-Sherlock-Signature: sha256=<hex>— when the organization has a webhook secret. See Signature verification.
Body
The scan id you received when submitting.
The submitted profile URL.
completed, completed_with_partial, or failed. See
Status values.ISO 8601 UTC timestamp.
See Recommendation values. On a failed
scan, Tumban defaults this to
review_high so the profile lands in
your queue for manual triage.0–100. On a failed scan, defaults to
50.low, medium, or high. On a failed scan, defaults to low.See Reason codes. On a failed scan, this
is
["SCAN_FAILED"].Human-readable summary. On a failed scan, this contains the error
message.
URLs your reviewers should look at first. On a failed scan, this is
["manual_investigation_required"].Short label describing the path Tumban followed (e.g.
Profile → External site). Empty string on a failed scan.Link to the detailed dossier for this scan.
The metadata you submitted with the scan, echoed back unchanged.
Per-URL evidence the contextual model cited. May be
[] when only
deterministic strategies fired or the contextual model hit an
infrastructure error. See Evidence index.Present when
status is failed. Brief description of what went
wrong.Present when
status is completed_with_partial. Brief description
of what was skipped.Example — completed
Example — failed
Acknowledging a webhook
Tumban considers a webhook delivered when your endpoint responds with a2xx status. Other statuses are retried — see
Delivery and retries.
