The Sendlom platform

One less thing
between you and send.

An email workflow that feels like part of your stack. Send through an API or SMTP, then follow the details that matter.

Get started

01 / The email API

A small request.
A meaningful message.

Bring welcome emails, password resets, and receipts into your application with a familiar HTTP request.

  • JSON requests from your server
  • A message ID to connect the dots
  • Examples for the tools you already use
Explore the sending guide
fetch('https://api.sendlom.com/emails', {  method: 'POST',  headers: {    Authorization: 'Bearer YOUR_API_KEY',    'Content-Type': 'application/json'  },  body: JSON.stringify({    from: 'hello@example.com',    to: 'alex@example.com',    subject: 'Welcome aboard'  })});
DeliveredExample response

Clarity after send

Every send
has a story.

Follow the message beyond your API call. See what arrived, what needs attention, and what to do next.

Message activityInteractive example
RECIPIENT / SUBJECTSTATUS
Select a message to follow its delivery.
DeliveredJust now

Welcome to Acme

Your message was accepted by the receiving server.

  1. API acceptedRequest received
  2. QueuedPrepared for delivery
  3. Delivered250 2.0.0 — Message accepted
Message ID email_01

Useful delivery events

Connect the request to the result with a message ID.

Clear bounce details

Understand the receiving server’s response in context.

Your workflow, connected

Bring delivery updates into your application with webhooks.

02 / Familiar connections

Your SMTP library.
A new home.

An existing app shouldn’t need a fresh email integration. Keep your library and connect with familiar SMTP settings.

Read the SMTP guide
Example connection
Host
smtp.sendlom.com
Port
587
Encryption
STARTTLS
Authentication
API key

Illustrative settings. Production credentials will be available in your workspace.

Thoughtfully connected

The essentials.
Without the overhead.

An email toolkit that fits around your product, from the first integration to the moment you need to investigate a send.

Make your domain your own.

Start with domain authentication. Connect the records that help receiving servers recognize your email.

Domain authentication

A clear, focused API.

Add email to the application you’re already building. A straightforward request, an identifiable message.

Explore the email API

SMTP. Still right at home.

Keep the tools and libraries you know. Connect an existing SMTP client to your sending workflow.

Connect with SMTP

Keep your app in the loop.

Make delivery events part of your application, from successful sends to messages that need attention.

Understand webhooks

The details, in context.

Look at the message, its delivery history, and the server response together. Troubleshooting starts with clarity.

Troubleshoot a send

Keys with a purpose.

Connect your server with an API key. Keep credentials out of your frontend and rotate them when needed.

Work with API keys

From idea to your first send

Three steps.
One less thing to build.

Follow the quickstart
  1. 01

    Connect your domain

    Add your sending domain and authenticate it with the DNS records provided.

    Explore this step
  2. 02

    Create an API key

    Give your application a secure way to send. Keep your key on your server.

    Explore this step
  3. 03

    Make your first call

    Use the API or SMTP. Then follow your message through its delivery events.

    Explore this step

Your next great idea starts here

Build something.
We’ll bring the email.

A little less setup

Your first send.

See how a message moves from request to delivery.

Interactive demo. No account is created and no email is sent.
Email preview

Welcome aboard.

Good things start with a hello.
You’re all set to start building.

Explore the integration guide