Visibility is org-wide by design — every member of the organization
sees every scan, not just the ones they submitted themselves.
Query parameters
Maximum number of scans to return. Range:
1–100.Pagination cursor. Pass the
next_cursor from the previous response
to fetch the next page; omit it for the first page.Comma-separated list of recommendation values to restrict results to,
for example
review_high,review_medium. Allowed values: no_flags,
review_low, review_medium, review_high. When this parameter is
set, only completed scans are returned.Restrict to a single scan mode:
quick or deep. deep also
matches legacy scans recorded before scan modes existed.Case-insensitive substring search over the profile URL and username,
for example
buymeacoffee.com/john or john.Earliest submission date to include,
YYYY-MM-DD (UTC, inclusive). A
malformed value returns 400.Latest submission date to include,
YYYY-MM-DD (UTC, inclusive). A
malformed value returns 400.Field to sort by:
created_at or risk_score.Sort direction:
desc (default) or asc.Response
List of scan summaries.
Opaque cursor for the next page. Pass it back as the
after query
parameter. null when there are no further results.true when more scans match beyond this page (next_cursor is set).ISO 8601 UTC timestamp of when the response was generated.
scans[]
Use with
GET /api/v2/scans/{scan_id} to fetch the
full record.The submitted profile URL.
See Status values. Includes
processing so
in-flight scans are visible.quick or deep. null on legacy scans recorded before scan modes
existed.ISO 8601 UTC timestamp.
ISO 8601 UTC timestamp;
null if the scan is still processing.See Recommendation values.
null for
scans that have not produced a triage report.0–100.
null for scans without a triage report.low, medium, or high. null for scans without a triage report.Example
Errors
| Status | Detail |
|---|---|
| 400 | Invalid recommendation values: [...] — one or more values in recommendation are not allowed. |
| 400 | from_date must be YYYY-MM-DD / to_date must be YYYY-MM-DD — the date filter is malformed. |
| 400 | from_date is not a valid calendar date / to_date is not a valid calendar date — well-formed but not a real date (e.g. 2026-02-30). |
Using the dashboard
Both the Home and History pages read from this endpoint:- Home → Action Items tile — count of last-30-day scans with
recommendationofreview_highorreview_medium; clicking it deep-links into History with that filter applied. - Home → Recent scans — the most recent scans of any status.
- History — the full search/filter view (recommendation, scan mode, date range, and URL/username search), with pagination.
processing) scans every five seconds
and updates rows in place. Click any non-processing row to open
Get scan detail.
