Vigilfield Docs
API referenceAlert destinations

Recent changes to this alert destination, from the audit log: the last 20 in 90 days, newest first. Readable by whoever can read the alert destination; IP addresses and the full-history query only for owners and admins. New changes can take a few minutes to appear.

GET/alert-destinations/{id}/activity

Path Parameters

id*string

The alert destination's id

Response Body

application/json

curl -X GET "https://example.com/alert-destinations/string/activity"
{  "audit_query": "string",  "data": [    {      "action": "string",      "actor": {        "kind": "person",        "name": "string",        "user_id": "string"      },      "ip": "string",      "outcome": "ok",      "time": "string"    }  ]}

`POST /alert-destinations/{id}/verifications` — Verify: publish the test message (SNS) or send the signed test request (webhook). An email destination has nothing to verify and answers 400. Stateless — the outcome is the response, not stored state (G-4). POST

Previous Page

`POST /alerts/{id}/acknowledgements` — acknowledge an alert. POST

The alert's id and resulting status. A repeat succeeds. Acknowledging a resolved alert is a 409. Recorded as you. The first acknowledgement stands: a repeat, by anyone, changes nothing.