Incident reporting
Log an incident from your SOC, ticketing or monitoring tool and get every regulatory reporting deadline back, computed from when you became aware.
Deadlines V77 computes
| Regime | When | Deadline |
|---|---|---|
| EU AI Act Art. 73(2) | Serious incident | 15 days after awareness |
| EU AI Act Art. 73(4) | Death of a person | 10 days |
| EU AI Act Art. 73(3) | Widespread infringement or critical-infrastructure disruption | 2 days |
| DORA | Major ICT-related incident (financial entities) | Initial, intermediate and final reports |
| GDPR Art. 33 | Personal-data breach | 72 hours |
Log an incident
curl https://v77trust.com/api/v1/incidents -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
-H "Idempotency-Key: INC-2026-0412" -d '{
"systemId": "'$SYSTEM_ID'",
"title": "Scoring model rejected eligible applicants",
"severity": "high",
"seriousIncident": true,
"euArticleRef": "Art. 73(2)",
"awareAt": "2026-11-01T09:00:00Z",
"gdprBreach": false
}'Use your ticket number as the Idempotency-Key, so a retried sync never logs the same incident twice.
Record that you reported
When you've filed with the market surveillance authority (or the DPA, or your DORA competent authority), record it. The deadline's state becomes done.
curl -X PATCH https://v77trust.com/api/v1/incidents/$INCIDENT_ID -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" -d '{
"authorityNotifiedAt": "2026-11-05T14:20:00Z",
"status": "mitigated",
"rootCause": "Feature drift after a bureau data schema change",
"correctiveActions": "Rolled back to v3.2; added schema validation"
}'Deadline
state is one of open, due_soon (under 24 h left), overdue, done or waiting (an earlier step isn't done yet). Poll GET /incidents?serious=true or subscribe to incident.created to drive alerts.