tencent cloud

Email Event Notification
Last updated:2025-10-30 11:08:29
Email Event Notification
Last updated: 2025-10-30 11:08:29
If you set a callback address, Tencent Cloud will notify the callback address of successful delivery, email rejection, bounce, open, click, unsubscription, and other events. You can configure a callback address in the SES console. For more details, see Callback Address.

Sample Request

{
"event":"bounce",
"email":"example@example.com",
"bulkId":"qcloudses-30-251200670-date-20220601142439-8jolHvR2XcXC1",
"timestamp":1654064683,
"reason":"551 5.1.1 recipient is not exist",
"bounceType":"hard_bounce",
"username":"251200670",
"from":"test@fromexample.com",
"fromDomain":"fromexample.com",
"templateId":123456,
"subject":"example subject",
"messageId":"ea2783c1-7704-48a8-af36-2b9e83e767ec@fromexample.com",
"sentTimestamp":1761555487,
"X-Tencentcloudses-Cb-Custom":"ses callback"
}
Field
Type
Description
event
string
Event type. For more information, see Email Event Notification.
email
string
Recipient address.
link
string
Clickable URL in the email. This field takes effect only when the value of event is click.
bulkid
string
MessageId returned by SendEmail.
timestamp
int
Event occurrence timestamp.
reason
string
Cause of email delivery failure.
bounceType
string
Rejection type when the email is rejected by the recipient’s email service provider (ESP). Valid values: soft_bounce | hard_bounce. This field takes effect only when the value of event is bounce.
username
string
Tencent Cloud account appId.
from
string
Sender address (excluding the sender name).
fromDomain
string
Sender domain.
templateId
int
Template ID.
useragent
string
User agent provides information about the device, operating system, and browser being used to access the Email.It is only effective when event="open" or event="click".
subject
string
Email subject. If it contains non-ASCII characters (such as Chinese), they will be escaped using MIME encoding.
messageId
string
The ​Message-ID​ is a field in the SMTP protocol header, where users can pass their own custom unique identifier for an email when sending via SMTP or API. It's crucial that this identifier must be able to uniquely identify an email message and comply with the RFC5322 standard.
eventid
int
1:delivered
2:dropped
3:bounce
4:open
5:click
6:spamreport
7:unsubscribe
8:deferred
taskId
int
taskId of the batch sending task
sentTimestamp
int
Email sent timestamp
X-Tencentcloudses-Cb-
string
Set custom callback content in the email headers using the prefix 'X-Tencentcloudses-Cb-'. This is supported for sending via both API and SMTP. For API sending, this can be set using the 'SmtpHeaders' parameter of the SendEmail interface.

Event Types

Value
Description
deferred
The delivery of the email has been delayed by the recipient's ESP and is being retried.
delivered
Delivery is successful. The recipient's ESP receives the email.
dropped
The email cannot be delivered and is dropped for some reasons.
open
The recipient opens the email.
click
The recipient clicks the URL in the email.
bounce
The recipient’s ESP rejects the email (usually because the email address is incorrect).
spamreport
The recipient reports the email.
unsubscribe
The recipient clicks the unsubscribe button. The unsubscribe URL should contain the "unsubscribe" keyword.

Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Yes
No

Doc Feedback