# DestinationSuppressionReason

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

Why a notification destination endpoint was durably suppressed. A suppression is stored, like a
SendGrid-style suppression list, and stays in effect until it expires or is cleared.

## Values

| Value | Description |
| --- | --- |
| `ConsecutiveFailures` | The endpoint failed the configured number of sustained consecutive delivery attempts. |
| `PermanentHttpError` | The endpoint returned a permanent (non-retryable) HTTP client error (a 4xx other than 401 / 403 / 408 / 429), signalling the request is wrong-by-construction (URL gone, payload refused) and will keep failing the same way on retry. |
| `Manual` | An administrator suppressed the endpoint manually. |
| `AuthRejection` | The endpoint repeatedly rejected our credentials (401 Unauthorized or 403 Forbidden). Kept distinct from PermanentHttpError so an operator can tell an auth-plane problem (expired secret, WAF rule, IP allowlist) from an endpoint that is genuinely gone: the two call for completely different remediation. Unlike a gone endpoint, this is never applied on a single response and carries a shorter expiry. |

## See also

- [All documentation](https://devportal.demo.winkpg.io/llms.txt): the machine-readable index of every public page on this site.