Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud Postbox
  • Getting started
  • Access management
  • Pricing policy
    • API authentication
    • How to use the API
    • Signing requests
      • All methods
      • Sending emails
      • Bulk email sending
        • ListSuppressedDestinations method
        • GetSuppressedDestination method
        • PutSuppressedDestination method
        • DeleteSuppressedDestination method
      • Request headers
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Request
  • Request headers
  • Request body
  • Responses
  • 200 OK
  • Errors
  1. API reference
  2. REST
  3. Suppression list
  4. PutSuppressedDestination method

PutSuppressedDestination method

Written by
Yandex Cloud
Updated at September 21, 2026
View in Markdown
  • Request
    • Request headers
    • Request body
  • Responses
    • 200 OK
    • Errors

Adds an address to the custom suppression list. The cloud is determined based on the service account the request originates from.

RequestRequest

PUT /v2/email/suppression/addresses HTTP/2

Request headersRequest headers

Use common request headers in your requests.

Request bodyRequest body

{
   "EmailAddress": "user@example.com",
   "Reason": "BOUNCE|COMPLAINT"
}

Parameter

Description

EmailAddress

Type: String.

The recipient's address to add to the suppression list.

Reason

Type: String.

This is a required setting. Reason to add the address to the suppression list: BOUNCE or COMPLAINT.

If the address is already on the suppression list, a new entry is not created: the reason and time of the change are updated for the current entry, and the creation time is preserved.

ResponsesResponses

200 OK200 OK

A successful request returns 200 OK in the response.

ErrorsErrors

For all errors, the response body has the same format:

{
   "Code": "<error_name>",
   "message": "<error_description>"
}

The name of the error is taken from its code, e.g., BadRequestException.

The possible errors include:

Error code

Description

400 BadRequestException

The request contains an empty or invalid address, or the reason is not specified or is not equal to BOUNCE or COMPLAINT.

403

Not enough permissions to execute the request.

429 TooManyRequestsException

The request quota was exceeded.

Was the article helpful?

Previous
GetSuppressedDestination method
Next
DeleteSuppressedDestination method
© 2026 Direct Cursus Technology L.L.C.