Signed event
scan.failed- Delivery
- whd_01J…
- HTTP status
- 503
- Next attempt
- Scheduled with backoff
- Scan state
- Unchanged; fetch remains authoritative
Accessibility webhooks for asynchronous scan results
Accessibility webhooks let a document upload or rendered-page scan finish outside the request cycle. AccessPreflight signs completion and failure events so your workflow can verify the sender, handle retries, and retrieve the authoritative result.
For backend teams connecting scan completion to CMS, DAM, CI, and approval workflows
Illustrative signed delivery
IllustrativeEvent
scan.completed- Event ID
- evt_01J…
- Scan ID
- scn_01J…
- Attempt
- 1
- Occurred
- 2026-08-02T14:32:18Z
AccessPreflight-Signature: t=…,v1=…- Events
- Queued · started · completed · failed · cancelled
- Integrity
- Signature · timestamp · replay protection
- Operations
- Test endpoint · retry · delivery log
Acknowledge quickly, retrieve deliberately.
The webhook announces a state transition and identifies the scan. Your system verifies and deduplicates it before fetching the full versioned result.
- Verify
Check the timestamp and signature
Reject stale or invalid deliveries before reading the payload.
- Deduplicate
Store the event ID
Return success for a previously processed event without applying the transition twice.
- Retrieve
Fetch the authoritative scan
Read findings, coverage, reports, and gate reasons through authenticated endpoints.
Keep delivery operations visible.
A test call and delivery log let integration owners confirm signatures, inspect attempts, and recover from endpoint downtime.
Treat the event envelope as a delivery contract.
The signed notification carries enough identity to route work while the full evidence remains retrievable from the API.
System boundaryscan.completed
Event and scan IDs
Deduplicate every delivery
Timestamp and signature
Verify before processing
Tenant-safe metadata
Route to the owning workflow
Status and report links
Pull complete evidence as needed
Choose the technical profile behind this capability.
Webhook receipts carry the profile and scan lineage needed to interpret an event after it leaves AccessPreflight. Consumers do not need to infer the ruleset.
Let signed scan events move the workflow forward.
Run a scan, verify one signed completion event, and add retries and idempotent handling before the webhook controls downstream work.
Check a website freeCreate an account
Automated preflight is not an accessibility certification or legal determination.