Dismiss Nudge
Dismiss a pending nudge of your active account: its status becomes dismissed, it gets a dismissed_at, and it leaves List Nudges. No request body.
A dismissed nudge comes back as pending when its check finds the same condition again. For the fast-changing checks (error_rate, endpoint_down, suspicious_traffic) a recently dismissed nudge is left dismissed for a cooldown period before it can come back.
The call is idempotent: dismissing a nudge that is already dismissed — or a uuid that names no nudge of the account — changes nothing and still answers 204.
Permissions: any member of the active account; no role permission is needed. Refused while the account is suspended.
Path parameters
uuid string (uuid) Req
The nudge's
uuid from GET /v1/account/nudges.Response (204 No Content)
Empty body.
Errors
401 Unauthorized
Missing or invalid auth.
403 Forbidden
No active account selected, Not a member of this account, or the account is suspended (code account_suspended).415 Unsupported Media Type
Content-Type must be application/json — send the header even though there is no body.500 Internal Server Error
Failed to dismiss nudge.Request
curl -X POST "https://api.ngris.com/v1/account/nudges/019b002a-8b10-7965-8ec9-97bded381ab9/dismiss" \
-H "X-API-KEY: <your_api_key>" \
-H "Content-Type: application/json"
Response — 204 No Content