Skip to main content
turboSMTP serves management and sending requests on different hosts. Append each endpoint path to the base URL listed below. Use the authentication guide to choose credentials and permissions.

​
API base URLs

For example, list analytics at https://pro.api.serversmtp.com/api/v2/analytics and send through https://api.turbo-smtp.com/api/v2/mail/send. Sending hosts accept the same message format. Do not send management requests to a sending host. Use consumerKey and consumerSecret headers for sending and supported management operations. Key management and password changes require a session API key; see endpoint-specific authentication.

​
GDPR and data residency

turboSMTP is an Italian company with European sending infrastructure. Choose api.eu.turbo-smtp.com for HTTP sending or pro.eu.turbo-smtp.com for SMTP when you need the EU sending route. Selecting an endpoint is one part of your data-protection configuration. Review turboSMTP’s data-protection information and obtain confirmation from support if you need contractual details about processing locations, retention, or subprocessors.

​
SMTP server settings

Both SMTP hosts support the same ports: Port 587 starts an SMTP connection and upgrades it with STARTTLS. Ports 465 and 25025 use TLS from the beginning. Port 2525 is a STARTTLS-capable alternative when port 587 is blocked. Port 25 is also available but is often blocked by hosting providers. Require encryption in your client before sending credentials. Create your key at Settings → Integrations → API Keys → Edit in the dashboard. Your dashboard login password is not the SMTP password. See SMTP setup for client instructions.