# Keep your SMTP. Move your email forward.

Connect your application to Bird with an SMTP host, port and API key. Keep the code that builds your messages, with authenticated sending, suppression handling and delivery events on the same infrastructure as the Email API.

[Set up SMTP](/dashboard/signup?returnTo=%2Fdashboard%2Fw%2Femail)

[Read the SMTP guide](/docs/guides/email/smtp)

Create your account, then configure your sender and SMTP credentials.

[Part of the Bird Email API](/products/email)

EU relay

US relay

TLS

465

STARTTLS

587 / 2525

Authentication

Username: bird. Password: your API key.

Use the host for your API key region and verify your sending domain before a production send.

## How do I move an application to Bird SMTP?

Verify the domain you send from, create an API key with email sending enabled, and update your SMTP connection settings. Your application can keep building its existing MIME messages, including HTML, text and attachments. Start with a test send before moving production traffic.

## Use the relay for your region.

Choose the EU or US host that matches your API key. Connect with implicit TLS on port 465, or STARTTLS on 587 or 2525. Authenticate with the username bird and your API key as the password. The SMTP guide includes settings and a complete session.

## Follow a message beyond the send call.

SMTP and HTTP feed the same email product. Domain verification, DKIM signing, IP pools, suppression handling and message events apply to both. Use the returned message ID to investigate a delivery in the email log. Acceptance by a receiving server does not establish inbox placement.

## Move one application at a time.

Give applications separate API keys when they need different IP pools, categories or tracking settings. Test the sender, content and delivery events before expanding the migration. For higher-volume requirements, discuss connection limits and the sending plan with our email team.

## Questions before you start

### Can I keep my existing SMTP integration?

Yes. Applications that submit mail to an SMTP relay can use Bird by updating their host, port and credentials. Verify the sending domain and use an API key with email sending enabled.

### Which SMTP ports are supported?

Use port 465 for implicit TLS, or ports 587 and 2525 for STARTTLS. Select the host for your API key region. Port 25 is not offered for submission.

### Should I use SMTP or the Email API?

SMTP suits existing applications that already build MIME messages. The HTTP API provides structured request fields and stored-template operations. Both use the same domain, reputation and delivery controls.

### How is SMTP priced?

Consult the published email pricing for your sending requirements. Our team can help with high-volume or migration requirements; a separate SMTP protocol does not require a separate email product.

## Build the rest of your email workflow

- [Sending API](/products/email/sending): Send transactional messages and batches with templates, idempotency and delivery events.
- [Email API](/products/email): Send transactional email and follow its delivery events.
- [Inbound email](/products/email/inbound): Receive and parse messages for your application.
- [Agent Mailboxes](/products/email/mailboxes): Give an agent an inbox with threads and replies.
- [Email pricing](/products/email/pricing): Review published rates and discuss your sending requirements.

## Connect your first application.

Verify your sender and send a test message with your existing SMTP integration. Work with our email team on a larger migration.

[Plan an SMTP migration](/demo?product=smtp)