Skip to main content
Most issues fall into three categories: invalid identity, key scope, or suppressed recipient at send time.

​
In brief

  • Suppression does not spend credit or call the provider — the send stops with RECIPIENT_SUPPRESSED.
  • Transient provider failures do not create suppression automatically.
  • Permanent bounces, complaints, and STOP are durable signals and may create an entry on their own.

​
Codes in the suppressions API

​
In message sending

Removing the suppression re-enables sending immediately. If the original issue (bounce, spam, opt-out) persists, the identity may return to the list automatically.

​
Day-to-day situations

The system creates a global phone suppression. SMS, WhatsApp, RCS, and voice are blocked. This is different from email marketing unsubscribe.
In batch (batch/add), each row has an individual result. Invalid rows do not block valid ones. Fix only those that returned invalid.
Check that you removed the correct normalized value. Use DELETE /v1/suppressions/by-identity with the same type and value on the list.
Tag organizes contacts. Topic is marketing consent. Suppression blocks sending. Email unsubscribe does not block SMS on its own.

​
Next steps