Amazon SES migration to Pepipost in 100 seconds

Migrating from Amazon SES to Pepipost is easier and you can get rid of Amazon SES spam when you have specific guidelines for the move. Plus, when you switch to Pepipost, you will get more insights on your user engagement such as:

  • who opened emails
  • which links are being clicked and by whom
  • the IP address and User Agent of the recipient
  • who requested to unsubscribe or marked the email as spam
  • a complete solution to Amazon SES spam emails

As a current user of Amazon SES, you are sending an email with Amazon SES SMTP or API. Follow these steps to seamlessly migrate to Pepipost from Amazon SES and avoid Amazon SES spam.

Migrating from Amazon SES SMTP to Pepipost

Here are the steps:

  1. Signup for Pepipost and activate your account through email.
  2. Configure and wait for your sending domain to be approved.
  3. Go to Settings and copy your Pepipost SMTP credentials.
  4. Open your application (CRM, backend app, website or any other plugin) which generates an email.
  5. Navigate to their Email/SMTP settings tab and just replace Amazon SMTP settings with the copied Pepipost settings.

An example of new settings:

Port: 25, 587 or 2525
Sender email address: is your sender domain; prior to sending an email, this needs to be configured and approved within your Pepipost account.

Check out our blog: Amazon SES Migration Guide

Migrating from Amazon SES API to Pepipost:

The API setup process at Pepipost is easy and straightforward. When setting up Amazon, you might have struggled with all of of Amazon's elements. You only need the API key and SDK with Pepipost, and you are done.

Amazon customers are familiar with terms such as –

Here are the Pepipost equivalent parameters for the above:

Amazon SES Equivalent Pepipost parameter Description
['Action'] NA In case of SES, Action=SendEmail;in Pepipost, Action parameter is not required as the base URL itself is pointing to sending email. i.e.
['Source'] from This is the sender email address. needs to be configured and approved in your Pepipost account.
"recipients": [
These are the set of recipient email addresses on which you want to send the email.
['Message']['Subject']['Data'] subject Subject of the email
['Message']['Body']['Text']['Data'] content The body content of the email

POST Examples for Pepipost Email Sending API

Content-Type: application/x-www-form-urlencoded
POST /api/web.send.json HTTP/1.1
"api_key": "string",
"email_details": {
"fromname": "yourfromname",
"subject": "this is test email subject",
"from": "",
"content": "
hi, this is a test email sent via Pepipost JSON API.
"recipients": [

POST Examples for Amazon SES Email Sending API

Content-Type: application/x-www-form-urlencoded


Note: Before running your first test email through Pepipost API, make sure that the domain (eg. is configured and approved under your Pepipost Account.

Just use any of your favorite SDKs and get started with Pepipost. Explore our complete API documentation.

    • PHP
    • Python
    • Ruby
    • NodeJS
    • NodeJS – Nodemailer
    • Java
    • Perl
    • C#

You can try every endpoint in the Pepipost API right from your browser using our Live API Explorer. That means there’s no longer a need to run cURL commands in terminal to test things out (though it’s fine, if that’s your preference).

At Pepipost, we believe in keeping things simple and easy. If you still have trouble migrating from Amazon SES or have any questions, just ping us on our 24X7 live chat support.  Our developer evangelists will be happy to walk you through the migration process. Or alternatively, you may email

Ready to get started?

Get started with up to 30,000 emails/month free!

Pepi thinking

Start typing and press Enter to search

Pin It on Pinterest