Send your first email

You can go from a new NevarMail account to a delivered email in about five minutes: connect a provider, verify a sender, then call one endpoint. Your first send will only reach your own inbox — every new organization starts in test mode, which restricts delivery to your verified address until you turn on live sending. That's expected, not a bug; see Test mode and safe send for how it works and when to graduate out of it.

What do you need first?

• A NevarMail account (sign up free)
• Credentials for SendGrid — the only provider available today (see Which providers can I use?)

Connect a provider

After signing in, go to Settings → Providers and either paste a SendGrid API key from your own account or let NevarMail provision a managed account for you. NevarMail verifies the connection automatically; there is nothing to configure in your own environment. See Providers for what the key needs to be allowed to do.

A managed account is billed by usage. Before NevarMail creates it, the setup step shows your email sending rate (per 1,000 emails, and any free monthly allowance your plan includes) and asks you to agree to it. Nothing is charged at that point. If your organization has no card on file yet, you save one with Stripe and come straight back, and the account is created without another click. Organizations billed by invoice see a note to contact their account team instead, because sending is added to their agreement. You can see the same rates and turn on usage items yourself at any time under Settings → Billing.

Verify a sender

You need at least one verified sender identity before you can send. Create one on the Senders page, or via the API with an API key:

curl -X POST https://app.nevarmail.com/api/v1/senders \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "name": "My App",
    "fromEmail": "hello@yourdomain.com",
    "fromName": "My Application"
  }'

Every v1 response wraps its payload in a standard envelope:

{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "name": "My App",
    "fromEmail": "hello@yourdomain.com",
    "fromName": "My Application",
    "isVerified": false
  },
  "requestId": "req_..."
}

See Senders for verification details.

Send your first email

With a provider connected and a sender verified, call /api/v1/email/send with an API key. Name the use case the send runs as in use_case_id: every project starts with a default one, and GET /api/v1/use-cases lists them with their ids. A key scoped to one project may leave it out and send as that project's default.

curl -X POST https://app.nevarmail.com/api/v1/email/send \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "use_case_id": "YOUR_USE_CASE_ID",
    "to": "you@your-company.com",
    "subject": "Hello from NevarMail!",
    "html": "<h1>It works!</h1><p>Your NevarMail integration is live.</p>",
    "text": "It works! Your NevarMail integration is live."
  }'

Your organization starts in test mode, and test mode does not redirect mail — it refuses it. A send to an address that is not on your test list comes back 422 TEST_MODE_RECIPIENT_NOT_ALLOWED rather than going anywhere.

So put your own address in to for this first send. Use the address you signed up with, or add one under Settings → Safety first. See Test mode and safe send for how the list works and how to turn on live sending when you're ready.

The response wraps a message ID and delivery status under data:

{
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "messageId": "msg-abc123@yourdomain.com",
    "status": "sent",
    "provider": "sendgrid",
    "sentAt": "2026-03-22T12:00:00.000Z"
  },
  "requestId": "req_..."
}

Set up your domain (optional, but recommended before going live)

For the best deliverability, configure your sending domain with SPF, DKIM, and DMARC — NevarMail automates the record generation. See Domains.

Where to next?

• Test mode and safe send — how test mode works and how to turn on live sending
• Authentication — API keys and session-based auth
• Sending Email — templates, scheduling, and other send options
• Templates — build reusable templates with variables
• Analytics — monitor delivery metrics