Ecosystem
Integrations
An audit that stays inside the audit tool does not get fixed. Here is every way results currently leave WebAuditOS - and, below it, the connectors people ask for that do not exist yet.
What exists today
Public REST API
list and create scans, read findings, pages and projects, on Pro and above
In-app alerts
score regressions and new critical findings, raised when a scan completes
E-mail alerts
one message per scheduled scan that finds a critical or high regression, to everyone in the workspace except client viewers, and switchable off
Scheduled monitoring
weekly or monthly from Starter, daily from Pro, with alerts on regression
CSV export
findings and page inventory, from the screens that show them
Shared report links and PDF
read-only, expiring, revocable, and white-labelled on Agency
Not built yet
Named rather than implied, because finding out by clicking something that does nothing is the worst way to learn it. If one of these is what you need, it is not here today.
Building against the API
The REST API is the supported way to move data out today, and /api documents exactly which endpoints exist and which do not. Keys are scoped read or write, stored only as a hash, and rate limited per workspace - every key shares the plan's budget.