Send one message through SMTP2GO's email API

Use SMTP2GO’s official libraries or the documented API client for your runtime. Its standard-email guide distinguishes standard messages from the separate MIME endpoint.

Build the standard-email request

This is a body-shape example for the documented client, not a live request. Replace both addresses with approved real addresses before sending:

{
  "sender": "sender@example.com",
  "to": ["recipient@example.net"],
  "subject": "Controlled SMTP2GO test",
  "text_body": "A message from an authorized sender."
}

Authenticate using the current documented API-key header/client configuration. Do not confuse that key with an SMTP user’s password or include it in a public request sample.

Check the complete result

Inspect data.succeeded, data.failed, and data.failures; an outer 200 does not justify marking every recipient delivered. Retain the returned email_id and request correlation with the application’s send record.

Check activity and the controlled recipient, then configure delivery feedback. A timeout may leave acceptance uncertain; investigate before replaying it. Switching to a MailKite send at that point can duplicate a message rather than recover it.

SMTP2GO sends the outbound message; replies still require a real receiving address/service. Use the next guide for delivery feedback, not as an inbound-mail replacement.