curl --request POST \
--url https://api.watchdog.no/v1/alerts/update \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({})
};
fetch('https://api.watchdog.no/v1/alerts/update', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.watchdog.no/v1/alerts/update"
payload = {}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"changed_count": 123,
"skipped_count": 123
}{
"error": {
"code": "validation_error",
"message": "The request is invalid. details lists up to 20 field errors. Request bodies are limited to 2 MiB.",
"request_id": "req_example"
}
}{
"error": {
"code": "invalid_token",
"message": "The bearer token is missing or invalid.",
"request_id": "req_example"
}
}{
"error": {
"code": "forbidden",
"message": "Access denied. The error code says why: forbidden, token_disabled, organization_required, insufficient_role or mfa_required.",
"request_id": "req_example"
}
}{
"error": {
"code": "not_found",
"message": "An alert in alert_ids, the claim, the topic or a selected View was not found.",
"request_id": "req_example"
}
}{
"error": {
"code": "conflict",
"message": "An alert in alert_ids cannot be changed (for example, it is in a completed claim or another open claim), the filter selects too many alerts, or a selected View has invalid saved filters. Nothing changed.",
"request_id": "req_example"
}
}{
"error": {
"code": "rate_limit_exceeded",
"message": "Too many requests. Wait for the Retry-After delay before retrying.",
"request_id": "req_example"
}
}{
"error": {
"code": "internal_error",
"message": "Unexpected server failure. Include the request ID when contacting support.",
"request_id": "req_example"
}
}{
"error": {
"code": "service_unavailable",
"message": "Temporarily unavailable. Retry after the Retry-After delay, when provided.",
"request_id": "req_example"
}
}Update alerts: confirm, mark as false alarm, skip, move back to review, add to or remove from a claim, move to another topic
Sets the verdict, dismissal, claim or topic of the selected alerts, with the same fields as PATCH /v1/alerts/. Only the fields you send change, and each changes only itself: setting a claim does not confirm, a verdict does not touch claims or credit. A false alarm (verdict dismissed) needs a dismissal category and starts a run that suggests improvements to the agreement’s instructions, unless suggest_instructions is false; once no alert keeps that false alarm, because its alerts took another verdict or a new reason, its suggestions nobody has reviewed are withdrawn. A claim can hold alerts of any verdict but asks only for accepted ones. To stop Watchdog flagging a kind of deviation again, teach the agreement a rule with POST /v1/agreements//teach. Select alerts with alert_ids or filter, at most 5000 per request. Retrying is safe. A filter must name topics, claims, agreements or invoices. Alerts in completed claims keep their verdict and claim.
curl --request POST \
--url https://api.watchdog.no/v1/alerts/update \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{}'const options = {
method: 'POST',
headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'},
body: JSON.stringify({})
};
fetch('https://api.watchdog.no/v1/alerts/update', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));import requests
url = "https://api.watchdog.no/v1/alerts/update"
payload = {}
headers = {
"Authorization": "Bearer <token>",
"Content-Type": "application/json"
}
response = requests.post(url, json=payload, headers=headers)
print(response.text){
"changed_count": 123,
"skipped_count": 123
}{
"error": {
"code": "validation_error",
"message": "The request is invalid. details lists up to 20 field errors. Request bodies are limited to 2 MiB.",
"request_id": "req_example"
}
}{
"error": {
"code": "invalid_token",
"message": "The bearer token is missing or invalid.",
"request_id": "req_example"
}
}{
"error": {
"code": "forbidden",
"message": "Access denied. The error code says why: forbidden, token_disabled, organization_required, insufficient_role or mfa_required.",
"request_id": "req_example"
}
}{
"error": {
"code": "not_found",
"message": "An alert in alert_ids, the claim, the topic or a selected View was not found.",
"request_id": "req_example"
}
}{
"error": {
"code": "conflict",
"message": "An alert in alert_ids cannot be changed (for example, it is in a completed claim or another open claim), the filter selects too many alerts, or a selected View has invalid saved filters. Nothing changed.",
"request_id": "req_example"
}
}{
"error": {
"code": "rate_limit_exceeded",
"message": "Too many requests. Wait for the Retry-After delay before retrying.",
"request_id": "req_example"
}
}{
"error": {
"code": "internal_error",
"message": "Unexpected server failure. Include the request ID when contacting support.",
"request_id": "req_example"
}
}{
"error": {
"code": "service_unavailable",
"message": "Temporarily unavailable. Retry after the Retry-After delay, when provided.",
"request_id": "req_example"
}
}Authorizations
Headers
Body
Whether the finding is right. pending: still to review. accepted: confirmed, the deviation is real (also when it is too small to pursue or already handled). dismissed: a false alarm, Watchdog was wrong; requires dismissal with a category. skipped (shown as Unsure): nobody can or will judge it; it leaves review without teaching anything. Claim membership and credit are not changed. Leaving dismissed takes the dismissal off the alert; it stays in the history.
pending, accepted, dismissed, skipped Whether the false alarm should start a run that suggests changes to the agreement's instructions, so later checks avoid the mistake. Defaults to true. Send false when the note explains a cleanup rather than a rule for future checks. Only valid with verdict dismissed; it is not stored on the alert.
Put the alerts in this pending or in-progress claim of their agreement, or null to take them out of their claim. Verdicts are not changed: send verdict accepted to accept them too. Alerts move out of a cancelled claim; out of another open claim only with move_from_open_claims. Alerts in completed claims cannot be changed. POST /v1/claims/alerts/preview says first which alerts would join and why the others would not.