Resolve an event
Mark an event you handled in your own system in Dark Radar too; the panel and reports show the same state, and the action is written to the event’s history.
Choose the action
actionType decides the event’s new status. The key needs the leak-events:write scope.
| Action | New status | When |
|---|---|---|
acknowledge | ack | Seen, under review. |
resolve | solved | Password reset, session ended. |
false-positive | closed | Not a real leak. |
block | blocked | Account or access blocked. |
reopen | re-open | To be handled again. |
alert | ack if open | An alert was sent. |
Send the request
curl -X POST "https://api.darkradar.com/api/public/v1/leak-events/$EVENT_ID/actions" \
-H "x-api-key: $DARKRADAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"actionType": "resolve", "notes": "Parola sıfırlandı"}'The response returns the event’s new status:
{
"success": true,
"data": {
"action": {
"eventId": "64b1f0c2a9e4d21f8c3b9005",
"status": "solved",
"actionTaken": true,
"actionType": "resolve",
"actionTakenAt": "2026-09-19T10:48:12.402Z",
"leakType": "email",
"type": "employee",
"severity": "high",
"eventDate": "2026-09-18T14:54:04.834Z"
}
}
}Another firm’s event, or an event in a group a restricted key may not access, returns
404; the record’s existence is not revealed.