SendPost API is built on REST API principles. Authenticated users can interact with any of the API endpoints to perform:
  • GET- to get a resource
  • POST - to create a resource
  • PUT - to update an existing resource
  • DELETE - to delete a resource
The API endpoint for all API calls is:
 https://api.sendpost.io/api/v1
Some conventions that have been followed in the API design overall are following:
  • All resources have either /api/v1/subaccount or /api/v1/account in their API call resource path based on who is authorised for the resource. All API calls with path /api/v1/subaccount use X-SubAccount-ApiKey in their request header. Likewise all API calls with path /api/v1/account use X-Account-ApiKey in their request header.
  • All resource endpoints end with singular name and not plural. So we have domain instead of domains for domain resource endpoint. Likewise we have sender instead of senders for sender resource endpoint.
  • Body submitted for POST / PUT API calls as well as JSON response from SendPost API follow camelcase convention
  • All timestamps returned in response (created or submittedAt response fields) are UNIX nano epoch timestamp.
SendPost uses conventional HTTP response codes to indicate the success or failure of an API request.
  • Codes in the 2xx range indicate success.
  • Codes in the 4xx range indicate an error owing due to unauthorize access, incorrect request parameters or body etc.
  • Code in the 5xx range indicate an eror with SendPost’s servers ( internal service issue or maintenance )
In SendPost all responses return created in UNIX nano epoch timestamp.

Authentication

SendPost uses API keys for authentication. You can register a new SendPost API key at our developer portal. SendPost expects the API key to be included in all API requests to the server in a header that looks like the following: X-SubAccount-ApiKey: AHEZEP8192SEGH This API key is used for all Sub-Account level operations such as:
  • Sending emails
  • Retrieving stats regarding open, click, bounce, unsubscribe and spam
  • Uploading suppressions list
  • Verifying sending domains and more
In addition to X-SubAccount-ApiKey you also have another API Key X-Account-APIKey which is used for Account level operations such as :
  • Creating and managing sub-accounts
  • Allocating IPs for your account
  • Getting overall billing and usage information
  • Email List validation
  • Creating and managing alerts and more
You must look at individual API reference page to look at whether X-SubAccount-ApiKey is required or X-Account-ApiKey
In case an incorrect API Key header is specified or if it is missed you will get HTTP Response 401 ( Unauthorized ) response from SendPost.

HTTP Response Headers

CodeReasonDetails
200SuccessEverything went well
401UnauthorizedIncorrect or missing API header either X-SubAccount-ApiKey or X-Account-ApiKey
403ForbiddenTypically sent when resource with same name or details already exist
406Missing resource idResource id specified is either missing or doesn’t exist
422Unprocessable entityRequest body is not in proper format
500Internal server errorSome error happened at SendPost while processing API request
503Service UnavailableSendPost is offline for maintenance. Please try again later

API Reference

SendX REST API can be broken down into two major sub-sections:
  • Sub-Account
  • Account
Sub-Account API operations enable common email sending API use-cases like sending bulk email, adding new domains or senders for email sending programmatically, retrieving stats, adding suppressions etc. All Sub-Account API operations need to pass X-SubAccount-ApiKey header with every API call. The Account API operations allow users to manage multiple sub-accounts and manage IPs. A single parent SendPost account can have 100’s of sub-accounts. You may want to create sub-accounts for different products your company is running or to segregate types of emails or for managing email sending across multiple customers of yours.

SMTP Reference

Simple Mail Transfer Protocol (SMTP) is a quick and easy way to send email from one server to another. SendPost provides an SMTP service that allows you to deliver your email via our servers instead of your own client or server. This means you can count on SendPost’s delivery at scale for your SMTP needs.

Integrating SMTP

  1. Get the SMTP username and password from your SendPost account.
  2. Set the server host in your email client or application to smtp.sendpost.io. This setting is sometimes referred to as the external SMTP server or the SMTP relay.
  3. Set the username and password.
  4. Set the port to 587 (or as specified below).

SMTP Ports

  • For an unencrypted or a TLS connection, use port 25, 2525 or 587.
  • For a SSL connection, use port 465
  • Check your firewall and network to ensure they’re not blocking any of our SMTP Endpoints.
SendPost supports STARTTLS for establishing a TLS-encrypted connection. STARTTLS is a means of upgrading an unencrypted connection to an encrypted connection. There are versions of STARTTLS for a variety of protocols; the SMTP version is defined in RFC 3207. To set up a STARTTLS connection, the SMTP client connects to the SendPost SMTP endpoint smtp.sendpost.io on port 25, 587, or 2525, issues an EHLO command, and waits for the server to announce that it supports the STARTTLS SMTP extension. The client then issues the STARTTLS command, initiating TLS negotiation. When negotiation is complete, the client issues an EHLO command over the new encrypted connection, and the SMTP session proceeds normally.
If you are unsure which port to use, a TLS connection on port 587 is typically recommended.

Sending email from your application

"use strict";

const nodemailer = require("nodemailer");

async function main() {
// create reusable transporter object using the default SMTP transport
let transporter = nodemailer.createTransport({
host: "smtp.sendpost.io",
port: 587,
secure: false, // true for 465, false for other ports
auth: {
user:  "<username>" , // generated ethereal user
pass: "<password>", // generated ethereal password
},
requireTLS: true,
debug: true,
logger: true,
});

// send mail with defined transport object
try {
let info = await transporter.sendMail({
from: 'erlich@piedpiper.com',
to: 'gilfoyle@piedpiper.com',
subject: 'Test Email Subject',
html: '<h1>Hello Geeks!!!</h1>',
});
console.log("Message sent: %s", info.messageId);
} catch (e) {
console.log(e)
}
}

main().catch(console.error);
<?php
// Import PHPMailer classes into the global namespace
use PHPMailer\PHPMailer\PHPMailer;
use PHPMailer\PHPMailer\SMTP;
use PHPMailer\PHPMailer\Exception;

// Load Composer's autoloader
require 'vendor/autoload.php';

$mail = new PHPMailer(true);

// Settings
try {
$mail->SMTPDebug = SMTP::DEBUG_CONNECTION;                  // Enable verbose debug output
$mail->isSMTP();                                            // Send using SMTP
$mail->Host       = 'smtp.sendpost.io';                     // Set the SMTP server to send through
$mail->SMTPAuth   = true;                                   // Enable SMTP authentication
$mail->Username   = '<username>';                           // SMTP username
$mail->Password   = '<password>';                           // SMTP password
$mail->SMTPSecure = PHPMailer::ENCRYPTION_STARTTLS;         // Enable implicit TLS encryption
$mail->Port       = 587;                                    // TCP port to connect to; use 587 if you have set `SMTPSecure = PHPMailer::ENCRYPTION_STARTTLS`

//Recipients
$mail->setFrom('erlich@piedpiper.com', 'Erlich');
$mail->addAddress('gilfoyle@piedpiper.com', 'Gilfoyle');

//Content
$mail->isHTML(true);                                  //Set email format to HTML
$mail->Subject = 'Here is the subject';
$mail->Body    = 'This is the HTML message body <b>in bold!</b>';
$mail->AltBody = 'This is the body in plain text for non-HTML mail clients';

$mail->send();
echo 'Message has been sent';

} catch (Exception $e) {
echo "Message could not be sent. Mailer Error: {$mail->ErrorInfo}";
}
#!/usr/bin/python3

import sys
import os
import re

from smtplib import SMTP
import ssl

from email.mime.text import MIMEText

SMTPserver = 'smtp.sendpost.io'
PORT = 587
sender =     'erlich@piedpiper.com'
destination = ['gilfoyle@piedpiper.com']

USERNAME = "<username>"
PASSWORD = "<password>"

# typical values for text_subtype are plain, html, xml
text_subtype = 'plain'

content="""\
Test message
"""

subject="Sent from Python"

try:
msg = MIMEText(content, text_subtype)
msg['Subject']= subject
msg['From']   = sender

conn = SMTP(SMTPserver, PORT)
conn.ehlo()
context = ssl.create_default_context()
conn.starttls(context=context)  # upgrade to tls
conn.ehlo()
conn.set_debuglevel(True)
conn.login(USERNAME, PASSWORD)

try:
resp = conn.sendmail(sender, destination, msg.as_string())
print("Send Mail Response: ", resp)
except Exception as e:
print("Send Email Error: ", e)
finally:
conn.quit()

except Exception as e:
print("Error:", e)
package main

import (
"fmt"
"net/smtp"
"os"
)

// Sending Email Using Smtp in Golang

func main() {

username := "<username>"
password := "<password>"

from := "erlich@piedpiper.com"
toList := []string{"gilfoyle@piedpiper.com"}
host := "smtp.sendpost.io"
port := "587" // recommended

// This is the message to send in the mail
msg := "Hello geeks!!!"

// We can't send strings directly in mail,
// strings need to be converted into slice bytes
body := []byte(msg)

// PlainAuth uses the given username and password to
// authenticate to host and act as identity.
// Usually identity should be the empty string,
// to act as username.
auth := smtp.PlainAuth("", username, password, host)

// SendMail uses TLS connection to send the mail
// The email is sent to all address in the toList,
// the body should be of type bytes, not strings
// This returns error if any occured.
err := smtp.SendMail(host+":"+port, auth, from, toList, body)

// handling the errors
if err != nil {
fmt.Println(err)
os.Exit(1)
}

fmt.Println("Successfully sent mail to all user in toList")
}
// implementation 'com.sun.mail:javax.mail:1.6.2'

import java.util.Properties;

import javax.mail.Message;
import javax.mail.Session;
import javax.mail.Transport;
import javax.mail.internet.InternetAddress;
import javax.mail.internet.MimeMessage;

public class SMTPConnect {

// This address must be verified.
static final String FROM = "erlich@piedpiper.com";
static final String FROMNAME = "Erlich Bachman";

// Replace recipient@example.com with a "To" address. If your account
// is still in the sandbox, this address must be verified.
static final String TO = "gilfoyle@piedpiper.com";

// Replace smtp_username with your SendPost SMTP user name.
static final String SMTP_USERNAME = "<username>";

// Replace smtp_password with your SendPost SMTP password.
static final String SMTP_PASSWORD = "<password>";

// SMTP Host Name
static final String HOST = "smtp.sendpost.io";

// The port you will connect to on SendPost SMTP Endpoint.
static final int PORT = 587;

static final String SUBJECT = "SendPost SMTP Test (SMTP interface accessed using Java)";

static final String BODY = String.join(
System.getProperty("line.separator"),
"<h1>SendPost SMTP Test</h1>",
"<p>This email was sent with SendPost using the ",
"<a href='https://github.com/eclipse-ee4j/mail'>Javamail Package</a>",
" for <a href='https://www.java.com'>Java</a>."
);

public static void main(String[] args) throws Exception {

// Create a Properties object to contain connection configuration information.
Properties props = System.getProperties();
props.put("mail.transport.protocol", "smtp");
props.put("mail.smtp.port", PORT);
props.put("mail.smtp.starttls.enable", "true");
props.put("mail.smtp.debug", "true");
props.put("mail.smtp.auth", "true");

// Create a Session object to represent a mail session with the specified properties.
Session session = Session.getDefaultInstance(props);

// Create a message with the specified information.
MimeMessage msg = new MimeMessage(session);
msg.setFrom(new InternetAddress(FROM,FROMNAME));
msg.setRecipient(Message.RecipientType.TO, new InternetAddress(TO));
msg.setSubject(SUBJECT);
msg.setContent(BODY,"text/html");

// Create a transport.
Transport transport = session.getTransport();

// Send the message.
try {
System.out.println("Sending...");

// Connect to SendPost SMTP using the SMTP username and password you specified above.
transport.connect(HOST, SMTP_USERNAME, SMTP_PASSWORD);

// Send the email.
transport.sendMessage(msg, msg.getAllRecipients());
System.out.println("Email sent!");

} catch (Exception ex) {

System.out.println("The email was not sent.");
System.out.println("Error message: " + ex.getMessage());
System.out.println(ex);
}
// Close and terminate the connection.
}
}
Many programming languages support sending email using SMTP. This capability might be built into the programming language itself, or it might be available as an add-on, plug-in, or library. You can take advantage of this capability by sending email through SendPost from within application programs that you write. We have provided examples in Python3, Golang, Java, PHP, JS.