Setting Up Webhooks

Webhooks are an advanced feature that allow us to notify your own web service whenever an event happens in your SMTP2GO account.

For example, you can choose for your own server to be instantly notified whenever a bounce occurs.

Setup of webhooks can be done on the "Settings > Webhooks" page in your SMTP2GO control panel.

When a particular event listed on that page happens, our server will contact your server and provide it with details of the event.

Standard Reported Data

The listed URL will receive an HTTP (or HTTPS) post request with the following parameters:


what happened: "processed", "delivered", "open", "click", "bounce", "spam", "unsubscribe", "resubscribe", or "reject".

An unsubscribe event happens if a recipient clicks on an unsubscribe link that you have inserted using the Unsubscribe Footer feature.
If a recipient decides to resubscribe (using the link shown to them on the unsubscribe confirmation page), a resubscribe event will occur.
reject event happens if you attempt to send an email to a recipient that has previously hard-bounced, made a spam complaint, or unsubscribed.

UTC timestamp of when the event happened.
UTC timestamp of when the email was sent to our server.
the 'envelope-from' email address.
the email address the email was sent from.
the email address the email was addressed to.
the email addresses the email was sent to.
the SMTP Username, API Key or IP Address used to send the email.
the recipient server that bounced the message (bounce only).
the error message we got (where available).
contains additional information on the event (where available).
an identifier that uniquely identifies the email, which can be used to retrieve further details of the email delivery.
this parameter will be included for a bounce event, and will be either hard or soft, depending on how we classify the bounce type.
the subject of the email.
the "User-Agent" header of the device that opened the email (where applicable).
the number of seconds an email was open - in five second increments up to a maximum of 30 (where applicable).
the reported client that clicked/opened the link ( based on the User-Agent ).
the reported device type of the User-Agent associated with the open/click event (where available)
the reported device operating system of the User-Agent associated with the open/click event (where available)
a 2 character continent code based on a geoip lookup of the IP address associated with the open/click event (where available)
a 2 character country code based on a geoip lookup of the IP address associated with the open/click event (where available)
the name of the city based on a geoip lookup of the IP address associated with the open/click event (where available)
the IP address of the end-user associated with an open/click event (where available) or the IP address that submitted the email ( for processed events )

Securing the URL 

You can optionally secure the URL with a username/password, with formats such as the following.
The URLs given below are just examples.

or simply make the name of the endpoint hard to guess:

Securing Endpoint

Optionally, you can further secure your endpoint with our webhook delivery IP addresses by using the A record for  MXToolbox is a good resource for viewing the IP addresses.


A good way to start testing is to deploy a local version of RequestBin, which will let you see exactly what data we send to you. Another option to try is Beeceptor.

Optional Email Headers

Custom email headers can optionally be reported along with the standard data above. You can specify the headers you wish to receive on the settings page.

any custom header that is sent in your emails.

You can add multiple headers to be returned by pressing "Tab" in between each entry in the "Headers" field:



Each 'URL of web service' that you enter must follow the URI standard.

with most parts of that being optional.
PROTOCOL can be either HTTP or HTTPS.
USER and PASSWORD are only required if you choose to password protect your web service.

We send a POST (not a GET) request to your URL with the data
application/x-www-form-urlencoded in the body.

Was this article helpful?