Remove a suppression

DELETE/api/v1/email-suppressions/{suppression}
Requires anorganization API keywith the scopesuppressions:write

Allows sending to this address again.

Worth doing only when you know why it was suppressed and that the cause is gone — a fixed typo, a mailbox that has been recreated. Removing a spam complaint because you would rather keep sending is how a sending reputation is lost.

Parameters

NameInTypeDescription
suppressionrequiredpathstringThe suppression identifier.

Request

DELETE/api/v1/email-suppressions/{suppression}
curl -X DELETE 'https://app.mailyte.com/api/v1/email-suppressions/01JBT8XQ2M9WYC3K4F6R7S8T9V' \
  -H 'Authorization: Bearer mk_live_YOUR_API_KEY'
The key names its own organization, so no X-Organization-ID header is needed.

Response

Success.

  • datanull

    No content. Sending to the address is allowed again -- worth doing only when you know the cause is gone, because a removed complaint still happened.

Returned inside the standard envelope.

Errors

StatusWhen
401The API key is missing, unknown, revoked or expired. All four answer identically, on purpose: distinguishing them would confirm which keys exist.
403The key is valid but may not do this: it lacks the required scope, its IP allowlist does not include you, or this endpoint does not accept API keys.
404No such resource in this organization.
422The request was understood but the values were not acceptable.
429Too many requests, or the organization has spent its sending allowance. `Retry-After` says how long to wait.

Every status, with what causes it and what to do, is on the error reference.