The Telnyx Email API now provides a more predictable suppression lifecycle, with automatic expiry and improved import and export handling.
What's new
- Automatic suppression expiry: Once a suppression expires, it automatically stops blocking email.
- Better Telnyx export and re-import handling: Native Telnyx suppression exports now retain their scoped state when re-imported.
- Clearer import results: error_count identifies rows that parsed successfully but failed suppression creation. Parser-skipped rows equal skipped_count - error_count.
Why it matters
Suppression lists are critical for preventing messages from being sent when they should not be. These updates make their lifecycle easier to manage and reduce manual cleanup.
Expired suppressions no longer continue blocking indefinitely. Telnyx exports can also be re-imported without losing their scoped state, while clearer import results make it easier to identify what happened when individual rows were not successfully imported.
Getting started
Prerequisites
- A Telnyx account
- A Telnyx API key
Existing Email API suppression workflows can continue to use the suppression import, export, and management APIs.
Learn more in the Suppressions and Unsubscribes documentation.
