The List Scans endpoint returns an array of scan records stored in your Webhood instance. You can filter results by any scan field, control sort order, and paginate through large result sets using theDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/webhood-io/webhood/llms.txt
Use this file to discover all available pages before exploring further.
limit and offset parameters. All query parameters follow PocketBase filter and sort syntax.
Request
GET /api/v1/scans
Authentication
All requests require a valid Bearer token in theAuthorization header.
Query Parameters
A PocketBase filter expression to narrow results. Fields available for filtering include
status, url, slug, created, updated, and final_url.Example: status = "done" or url ~ "example.com"Field name to sort results by. Prefix with
- for descending order, or omit the prefix for ascending order.Example: -created (newest first) or created (oldest first)Maximum number of scan records to return in a single response. Use together with
offset to paginate through results.Number of records to skip before returning results. Use together with
limit to implement pagination.Response
Returns an array of scan record objects. Each object contains the full scan metadata including status, URL, timestamps, and file references.Response Fields
Unique identifier for the scan record.
Human-readable identifier in
hostname-timestamp format, e.g. example.com-1714000000.The original URL that was submitted for scanning.
Current scan status. One of
pending, running, done, or error.ISO 8601 timestamp of when the scan record was created.
ISO 8601 timestamp of when the scan record was last updated.
Error description, populated only when
status is error.Array of file IDs for captured HTML and trace files. Index 0 is the HTML file; index 1 is the network trace.
Array of file IDs for captured PNG screenshots.
Array of additional file IDs associated with the scan.
ISO 8601 timestamp of when the scan completed. Null if not yet finished.
The final URL after all redirects were followed. May differ from the submitted
url.The
ScanOptions that were applied to this scan.Structured scan metadata including document details, initial request/response, and scanner configuration. Matches the
ScanDataV1_1 schema.