Free Email Service

Quickstart

Create a key, verify a domain, and send your first email.

Open this guide on its own page

You can send your first email in minutes: create an API key, verify a domain, and make a POST request.

1. Create an API key

Go to API Keys. Choose a preset — Full, Sending, or Read only — or narrow it further. Copy the key when shown.

Tip: Scope keys tightly

A server that only sends mail should use a Sending key. Keys can never manage other keys, team, or billing.

2. Verify a sending domain

Add your domain under Domains and publish the generated DNS records. Verification runs automatically.

Note: No domain yet?

While DNS propagates you can still send test emails to your own address from the dashboard onboarding flow — no verified domain required. Test sends confirm the pipeline works; live API sends need a verified domain.

3. Send

Send an email in one call — a from address on your verified domain, a recipient, a subject, and either inline HTML or a template ID. The from accepts a bare address or a display name ("Acme <you@yourdomain.com>").

var result = await unitpost.Email.Send(new {
    from = "Acme <you@yourdomain.com>",
    to = "customer@acme.com",
    subject = "Welcome aboard",
    html = "<p>Thanks for signing up!</p>",
});

The response includes the new email's id. Use GET /api/v1/email/ (or unitpost.email.get(id)) to read its current status and lifecycle events, or watch it live on the Emails page in the dashboard.

Quickstart

Create a key, verify a domain, and send your first email.

Open this guide on its own page

You can send your first email in minutes: create an API key, verify a domain, and make a POST request.

1. Create an API key

Go to API Keys. Choose a preset — Full, Sending, or Read only — or narrow it further. Copy the key when shown.

Tip: Scope keys tightly

A server that only sends mail should use a Sending key. Keys can never manage other keys, team, or billing.

2. Verify a sending domain

Add your domain under Domains and publish the generated DNS records. Verification runs automatically.

Note: No domain yet?

While DNS propagates you can still send test emails to your own address from the dashboard onboarding flow — no verified domain required. Test sends confirm the pipeline works; live API sends need a verified domain.

3. Send

Send an email in one call — a from address on your verified domain, a recipient, a subject, and either inline HTML or a template ID. The from accepts a bare address or a display name ("Acme <you@yourdomain.com>").

var result = await unitpost.Email.Send(new {
    from = "Acme <you@yourdomain.com>",
    to = "customer@acme.com",
    subject = "Welcome aboard",
    html = "<p>Thanks for signing up!</p>",
});

The response includes the new email's id. Use GET /api/v1/email/ (or unitpost.email.get(id)) to read its current status and lifecycle events, or watch it live on the Emails page in the dashboard.

Templates & variables

Reference a saved template and pass per-recipient data.

Open this guide on its own page

Rather than inlining HTML on every send, save a template once and reference it by ID. Pass template.variables and any {{variable}} in the template is substituted at send time.

using Unitpost;

var unitpost = new UnitpostClient(); // reads UNITPOST_API_KEY

var result = await unitpost.Email.Send(new
{
    from = "you@yourdomain.com",
    to = "customer@acme.com",
    template = new
    {
        id = "tmpl_123",
        variables = new { plan = "Pro" },
    },
});

When you send to a known contact, that contact's custom fields merge into the variables automatically — so a template can reference {{first_name}} without you re-sending it on every request.

Warning: Drafts can't be sent

A template must be published before the API will send it. Referencing a draft returns a 422 with code template_not_published. Publish it in the editor first.

Author templates in the visual editor, or in your app with import { Heading, render } from "@unitpost/email/react" and POST { name, html: render(<Email />), subject }. Manage them under Templates. Every block and layout is documented at /components.

Sending domains

Add SPF, DKIM, and DMARC so mail sends from your domain.

Open this guide on its own page

To send from your own domain you publish a few DNS records so mailbox providers trust the mail is really from you. Add the domain under Domains and copy the generated records to your DNS provider.

• DKIM — a TXT record that lets us cryptographically sign your mail.
• MAIL FROM — a custom return-path subdomain for SPF alignment.
• DMARC — a policy record that tells receivers what to do with unaligned mail.

Verification is continuous, not one-shot. A domain is Verified, Degraded, or Unverified, and we keep re-checking the records over time.

Note: Degraded still sends

You can send from a Verified or Degraded domain. Degraded means some records drifted but mail still flows — fix the flagged records to return to Verified. You cannot send from an Unverified domain.

Open & click tracking

Control engagement tracking per send, template, or category.

Open this guide on its own page

With tracking on, we inject a 1×1 open pixel and rewrite links so opens and clicks land in the email's event timeline and feed the engagement rates on your dashboard.

How the default is resolved

Tracking is resolved per send in a clear order, most specific first:

1. An explicit tracking flag on the request wins.
2. Otherwise the referenced template's default applies.
3. Otherwise the category default applies.

Tip: Sending a receipt or password reset?

Set tracking to false to deliver a clean, untracked transactional message. Many providers and recipients prefer no pixel on sensitive mail.