Skip to main content
turboSMTP offers an SMTP relay and a JSON email API with Global and EU sending endpoints. Compare the request formats, credentials, regional setup, and plan requirements before migrating.

Evaluate turboSMTP

Global and EU Endpoints

Use api.eu.turbo-smtp.com for API sending or pro.eu.turbo-smtp.com for SMTP in the EU region. Review processing terms for your requirements.

Plan Features

Check sending allowances, analytics retention, webhooks, and support channels for your plan.

Support

Chat and ticket support are listed for Free and Basic. Pro and Enterprise also list phone support.

SMTP and JSON API

Send with a Consumer Key and Consumer Secret through an SMTP client or an HTTPS request.

Comparisons

turboSMTP vs SendGrid

Compare regional endpoints, API payloads, and SMTP credentials.

turboSMTP vs Mailgun

Compare regional setup, JSON and form data, and message limits.

Migration guides

Migrate from SendGrid

Map SMTP settings and v3 Mail Send requests to turboSMTP.

Migrate from Mailgun

Map SMTP settings and form-data requests to turboSMTP.

Plan your migration

1

Check your plan and credentials

Review current pricing and create API keys with the sending permissions you need.
2

Authenticate your domain

Add turboSMTP to your existing single SPF record and publish its DKIM record. Keep your current provider authorized during cutover. See SPF, DKIM, and DMARC.
3

Move settings and suppression data

Update SMTP or API configuration, import suppressions, and adapt webhook handling. Verify regional and feature availability before moving traffic.
4

Ramp up and cut over

Move a share of traffic first and inspect Analytics. Retire the old provider after its queue has drained.