Skip to main content
10 min readMessaging & AI

Setting Up Emailit

Connect Emailit as a simple low-friction provider, verify your sending domain, use the right API and SMTP keys, and understand where its limits matter for agencies.

Emailit is a straightforward provider for agencies that want something simpler than AWS-style infrastructure and do not need every advanced feature found in the larger platforms.

It is a good fit when the main goal is to get a dedicated provider connected quickly and cheaply. The trade-off is that the current platform support is lighter, especially around automatic bounce handling and customer-specific sending domains.

What Emailit is and when it makes sense

Emailit uses SMTP for delivery but provides API-managed credentials and sending domains around that core. That makes it feel simpler than the heavier providers while still behaving more like a dedicated service than a normal personal mailbox.

PlanMonthly emailsCost
Starter10,000 per monthFrom $5 per month
Growth50,000 per monthFrom $20 per month
Business200,000 per monthFrom $50 per month
Worth knowing

Emailit positions itself as a simple, affordable option. It is often attractive when the team wants speed and low cost more than deep delivery tooling.

Before you start

  • An Emailit account
  • A sending domain verified in Emailit
  • Access to your DNS settings
  • An API key and a separate SMTP key from Emailit

Part 1: add your sending domain in Emailit

In Emailit, go to `Sending Domains`, add the domain, publish the SPF and DKIM records in your DNS provider, and verify the domain.

This step is not optional because the platform checks the domain in your from address against Emailit's verified sending domains.

Part 2: create the API key and SMTP key

Emailit separates API access from SMTP sending. The API key is used for validation and domain checks. The SMTP key is used later as the actual sending credential.

  • Create one credential with the type set to API
  • Create another credential with the type set to SMTP
  • Do not mix them up because setup only validates the API key directly

Part 3: connect Emailit in the platform

Go to `Platform -> Messaging -> Email`, click `Add Provider`, name the provider, expand `Other Providers`, choose `Emailit`, and move through the setup.

StepWhat to do
AuthenticatePaste the API key and SMTP key, then verify
Sender detailsSet from and reply-to details before moving on
ThrottlingKeep the default unless your plan clearly supports more
SummaryReview the setup and send a test email
Worth knowing

If the sender step says the sender domain has not been configured in Emailit, the domain in the from address does not match a verified sending domain in Emailit yet.

Sender details, throttling, and testing

Emailit requires sender details earlier than most providers because the platform validates the sender domain directly before it lets you continue.

The default throttling is deliberately conservative. That is usually the right place to start unless you are confident your Emailit plan can support faster sending safely.

  • Use a from address on the verified Emailit domain
  • A wrong SMTP key often only shows up when you send the test email
  • Increase throttling only after you confirm the plan and reputation can handle it

Understand the bounce and complaint limitation

Emailit does not currently support webhook-based bounce and complaint tracking in the platform. That is the main operational limitation agencies need to understand before choosing it.

In practice, that means bounced addresses are not automatically unsubscribed here the way they are with SendGrid, Brevo, Mailgun, Postmark, or SES.

  • You need to review bounce data manually in Emailit
  • This is more manageable on smaller lists than on larger campaign programs
  • If automatic bounce handling is important, a more fully featured provider is usually the better fit

How Emailit interacts with custom-plan credits

Emailit changes the delivery provider, not the custom-plan invite credit logic. In a normal agency-managed sending setup, invite emails still consume the customer plan email limit.

So if an Emailit-powered invite fails because of credits, the normal issue is still the assigned customer plan limit rather than the Emailit connection.

  • Transactional emails remain separate from invite credits
  • Normal agency-managed invite emails still respect the customer plan email limit
  • Customer-specific sending domains are not supported here, so choose another provider if that matters

Common questions