📮Transactional SMTP Relay

You will only see your API key if you log in as a user account on the frontend, if you impersonate a customer account as a backend admin the API key will be blank.

In the email marketing platform, go to Integrate -> API & SMTP -> SMTP Relay

Configure your sending application to use your ESP hostname or IP address and ports 587, 2525, or 8025.

To make a secure encrypted connection, use the TLS extension after connecting via regular SMTP. SSL method is not supported.

If a multipart message consists of text and HTML parts, only HTML will be used.

Text parts are unsupported.

Use your API Key for your username and password.

  • From: The from name and from email address, aka the 'Friendly From' or 'From Name'.

  • To: Specify the recipient's name but not their email address.

  • Subject: The message subject line.

  • Reply-To: Include an optional Reply-To address.

  • X-Transactional-Tag: If left blank, the message will be tracked as “untagged” on the transactional dashboard.

  • X-Transactional-Route: Specifies a postal route to use. This is required if the customer account has more than one postal route available, otherwise, the message will fail.

  • X-Transactional-Template: Include a template ID if you want to send this message using a pre-created transactional template.

  • X-Auth-APIKey: Bypass the SMTP AUTH username and password method and authenticate via header instead.

  • X-Transactional-Variables: Specifies a JSON string to use as an input dictionary for the Jinja2 templating system. For more details on Jinja2 see our API docs.

Last updated

Was this helpful?