Skip to main content
GET
Get a page audit
Returns the status of a page audit and the status of each audited page. This is the resource identified by the Location header from Start a page audit. Each page’s terminal result belongs to this audit and does not change when a later audit runs. COMPLETED means every page has reached a terminal state, not that every page succeeded: inspect counts.failed and counts.skipped. An interrupted treatment can remain QUEUED or AUDITING while its exact result is recovered. A page whose run can no longer exist is FAILED: queueing is retried within 24 hours of acceptance, at most 12 times, and queued runs expire after 7 days. A run that is still active on the queue is waited for. Get a monitored page returns that page’s latest scores, which may come from a newer audit. Available on Growth, Agency Growth, Business, Agency Business and Enterprise plans. See Authentication.
string
required
Bearer token for your team.
string
required
Workspace identifier. The workspace must belong to the token’s team.
string
required
Audit identifier returned when the audit started.

Response

string | null
Audit identifier. null only for a dry run, which this endpoint never returns
string
RUNNING or COMPLETED. A dry run of Start a page audit returns PREVIEW
integer
Audit credit budget: 5 per page to audit, adjusted when dispatch refuses pages. Not an immediate hold or the final amount spent
object
total, succeeded, failed, skipped and running page counts.
array
One entry per page with pageId, status (QUEUED, AUDITING, COMPLETED, FAILED or SKIPPED) and completedAt (nullable).
string
ISO 8601 creation time
string | null
ISO 8601 time when the audit finished, or null while it runs. Once the site_audit.completed event exists, this is the completedAt of that event. It can be later than the last page date when the last pages were skipped or queueing closed later

Synthetic request and response

Errors

Read errors use the flat or nested shapes described in Error codes. On 429, honor Retry-After.