customer_service

Revoke Suppression

Stop applying a rule, and bring back the mail it was holding. The rule stays on the record as revoked, because the fact that we ignored this sender is what you need when you go looking for the mail that never arrived.

Frederick, 2026-10-07 (#2284, #2171): mail from a suppressed sender opens no ticket and is held whole; removing the rule re-ingests every held message through the normal inbound path, once each (suppression_replay). Frederick ruled the hold and the replay; ARRIVAL ORDER is the builder's decision (recorded 2026-10-07, not Frederick's words): it is the order the desk would have seen the mail. Safe to call again: a retry, or the second of two simultaneous calls, revokes nothing, replays nothing twice and finishes anything the first attempt did not (revoked is false then, released says what this call brought back). 404 only when no such rule exists.

delete/api/cs/suppressions/{suppression_id}

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/cs/suppressions/{suppression_id}
  • Auth: none declared

Path parameters

suppression_idstring uuid required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.