SMTP relay.

Connect the software you already use to Bird’s email delivery. Keep your application’s SMTP integration, send over an encrypted connection, and track results in the dashboard or through MCP.

Trusted every day by teams that
build world-class software.

Check the setup.
Then connect your app.

Start with your sending identity. Ask Bird MCP to check the domain and its DNS records, then connect your application to the regional SMTP relay with an email-enabled API key.

Check my sending domain
before I connect SMTP.

Bird MCP
  1. email_domains_listFound
  2. email_domains_getChecked
Sending domain

mail.harbor.example

DKIMVerified
Return pathVerified
Ready forSMTP / API

Change the connection.
Keep the message.

Add Bird’s host, port and credentials to your mail library or application. Keep your HTML and attachments. Set category, tracking and IP-pool defaults on the API key so each application sends with its own configuration.

Use implicit TLS on port 465 or STARTTLS on 587 or 2525. Match the SMTP region to your API key.

Ready to build?

Your app sends it.
Bird shows you what happened.

SMTP messages appear in the same email log and reports as API sends. Keep the message ID from the queued response, then follow delivery, deferrals and bounces in Bird or through signed webhooks.

Your domain.
Your reputation.

Verify your sending identity. Manage reputation as your volume grows.

Sending domain
harbor.exampleReady to send
DKIMSign outgoing messages
Verified
Return-pathAuthenticate your sending path
Verified
DMARCPublish your domain’s policy
Verified
Sending enabledSending records verified.

SMTP relay, explained.

What credentials does Bird SMTP use?

Use bird as the username and a regional API key with emails permission as the password. Connect to eu1.smtp.bird.com or us1.smtp.bird.com to match the key region.

Which ports are supported?

Use 465 for implicit TLS or 587 and 2525 for STARTTLS. Authentication requires encryption. Port 25 is not offered for submission.

Can SMTP render a stored Bird template?

SMTP takes content from the MIME message your application submits. Use the Email API when you want to send a stored template with structured parameters.

Scale without losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

Go further.
With Email.

Everything from your first send to delivery at scale.

Start with one. Build across channels.

Bring your next customer conversation into the same workspace.

Your next idea. Ready to connect.

Your next idea. Ready to connect.