Getting Started

# Quick Start

Go from zero to sending your first email in seven steps. The whole workflow takes about five minutes.

1Create Project

2Create Domain

3Push DNS

4Verify Domain

5Create Mailbox

6Enable Warmup

7Send Email

## Before You Begin

Make sure you have the following before starting:

* A Mission Inbox account with an active subscription.
* Your product API key (starts with `mi`), visible in the sidebar of this portal under your product subscription.
* A domain you own and have DNS access to (e.g. via Cloudflare, Route 53, or your registrar's DNS panel).

1

## Create a Project

Projects are the top-level container for your domains and mailboxes. Create one to keep your sending infrastructure organised. The returned `id` can be passed when creating domains to assign them automatically.

cURL

```bash
curl -X POST https://api.v4.missioninbox.com/api/projects \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Campaign Q1"
  }'
```

Response

```json
{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "name": "Campaign Q1",
  "domainsCount": 0,
  "mailboxesCount": 0,
  "createdAt": "2026-02-20T10:00:00.000Z",
  "updatedAt": "2026-02-20T10:00:00.000Z"
}
```

2

## Create a Domain

Register your domain with Mission Inbox. Pass the project `id` from the previous step to assign the domain immediately. The domain is created with `verified: false` — its DNS records must be published and verified before you can send from it.

If you have connected a [DNS provider key](https://doc.v4.missioninbox.com/sales/api/dns-credentials.md) for the domain's DNS host, the records are published in this same call: `hasDnsManager` is `true` and `emailDns.pushed` confirms it. Skip to step 4.

cURL

```bash
curl -X POST https://api.v4.missioninbox.com/api/domains/create \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "domainName": "yourdomain.com",
    "projectId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
  }'
```

Response

```json
{
  "uuid": "86c0c812-cb50-4b25-8b01-721e3933bf63",
  "domainName": "yourdomain.com",
  "verified": false,
  "verificationToken": "uFfAONu1UBFgR1qNgXJOOb2bIHlQTlLd",
  "dnsVerificationString": "postal-verification uFfAONu1UBFgR1qNgXJOOb2bIHlQTlLd",
  "spfHost": "yourdomain.com",
  "spfValue": "v=spf1 include:spf.cobalt.obmengine.com ~all",
  "dkimHost": "mi-tAsUUQ._domainkey.yourdomain.com",
  "dkimValue": "v=DKIM1; t=s; h=sha256; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCdJ03e...",
  "rpHost": "bounce.yourdomain.com",
  "rpValue": "rp.cobalt.obmengine.com",
  "mxHost": "yourdomain.com",
  "mxValue": "staging.outboxment.com",
  "mxPriority": 10,
  "dmarcHost": "_dmarc.yourdomain.com",
  "dmarcValue": "v=DMARC1; p=quarantine; rua=mailto:abuse@yourdomain.com; ruf=mailto:abuse@yourdomain.com; sp=quarantine; adkim=r; aspf=r; fo=1; ri=864000;",
  "hasDnsManager": false
}
```

3

## Push DNS Records

Writes the domain's records to your DNS provider with your connected key, and returns each record with its own result. Use it when the domain was added before the key was connected, or to re-publish records changed at the provider. With no key connected, take the record values from `GET /api/domains/:domainName` and add them in your DNS panel exactly as shown.

cURL

```bash
curl -X POST https://api.v4.missioninbox.com/api/domains/push-dns \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "domainName": "yourdomain.com"
  }'
```

Response

```json
{
  "domainName": "yourdomain.com",
  "message": "Successfully pushed 5 DNS records for yourdomain.com via CloudFlare.",
  "dnsRecords": [
    {
      "type": "TXT",
      "name": "yourdomain.com",
      "value": "v=spf1 include:spf.cobalt.obmengine.com ~all",
      "purpose": "spf"
    },
    {
      "type": "TXT",
      "name": "mi-tAsUUQ._domainkey.yourdomain.com",
      "shortName": "mi-tAsUUQ._domainkey",
      "value": "v=DKIM1; t=s; h=sha256; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCdJ03e...",
      "purpose": "dkim"
    },
    {
      "type": "CNAME",
      "name": "bounce.yourdomain.com",
      "shortName": "bounce",
      "value": "rp.cobalt.obmengine.com",
      "purpose": "return_path"
    },
    {
      "type": "MX",
      "name": "yourdomain.com",
      "value": "staging.outboxment.com",
      "priority": 10,
      "purpose": "mx"
    },
    {
      "type": "TXT",
      "name": "_dmarc.yourdomain.com",
      "value": "v=DMARC1; p=quarantine; rua=mailto:abuse@yourdomain.com; ruf=mailto:abuse@yourdomain.com; sp=quarantine; adkim=r; aspf=r; fo=1; ri=864000;",
      "purpose": "dmarc"
    }
  ],
  "results": [
    { "record": { "type": "TXT",   "name": "yourdomain.com",                      "value": "v=spf1 include:spf.cobalt.obmengine.com ~all",  "purpose": "spf"         }, "success": true },
    { "record": { "type": "TXT",   "name": "mi-tAsUUQ._domainkey.yourdomain.com", "value": "v=DKIM1; t=s; h=sha256; p=...",                 "purpose": "dkim"        }, "success": true },
    { "record": { "type": "CNAME", "name": "bounce.yourdomain.com",               "value": "rp.cobalt.obmengine.com",                        "purpose": "return_path" }, "success": true },
    { "record": { "type": "MX",    "name": "yourdomain.com",                      "value": "staging.outboxment.com", "priority": 10,         "purpose": "mx"          }, "success": true },
    { "record": { "type": "TXT",   "name": "_dmarc.yourdomain.com",               "value": "v=DMARC1; p=quarantine; ...",                    "purpose": "dmarc"       }, "success": true }
  ]
}
```

DNS propagation typically takes a few minutes but can take up to 24–48 hours depending on your provider's TTL settings. Wait for propagation before running the verification step.

4

## Verify the Domain

Once DNS records have propagated, verify the domain. Mission Inbox checks SPF, DKIM, Return-Path, MX, and DMARC records. All five must pass before mailboxes can be created.

cURL

```bash
curl -X POST https://api.v4.missioninbox.com/api/domains/verify \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "domainName": "yourdomain.com"
  }'
```

Response

```json
{
  "message": "Domain yourdomain.com verified successfully",
  "dnsChecks": {
    "spf":         { "status": "OK", "error": null },
    "dkim":        { "status": "OK", "error": null },
    "return_path": { "status": "OK", "error": null },
    "mx":          { "status": "OK", "error": null },
    "dmarc":       { "status": "OK", "error": null }
  },
  "fullyVerified": true
}
```

If any record status is not `OK`, double-check the values in your DNS provider and retry. You can call verify as many times as needed.

5

## Create a Mailbox

Create a mailbox on your verified domain. The `email` must use the domain you just verified.

cURL

```bash
curl -X POST https://api.v4.missioninbox.com/api/mailboxes \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "email": "sender@yourdomain.com",
    "fullName": "John Doe",
    "password": "StrongPassword123"
  }'
```

Response

```json
{
  "email": "sender@yourdomain.com",
  "fullName": "John Doe",
  "password": "StrongPassword123",
  "sent": 0,
  "warmedDays": 0,
  "totalWarmedDays": 0,
  "isWarmupActive": false,
  "domainId": "c6cffd67-1628-407e-bc92-e317ea852397",
  "domainName": "yourdomain.com",
  "createdAt": "2026-04-07T09:10:36.563Z",
  "updatedAt": "2026-04-07T09:10:36.563Z",
  "integrations": []
}
```

The `password` field is optional — if omitted, Mission Inbox auto-generates one. If you plan to send via SMTP (Step 7), set an explicit password now so you have it ready.

You can create mailboxes one at a time or use `POST /api/mailboxes/bulk-create` to provision hundreds at once via a background task.

6

## Enable Warmup

Recommended

Warming up a mailbox gradually builds its sending reputation before you use it in production campaigns. It is strongly recommended for any mailbox that will send at volume.

cURL

```bash
curl -X POST https://api.v4.missioninbox.com/api/warmup/mailboxes/sender@yourdomain.com \
  -H "X-Server-API-Key: miacme_4eC8vKmN2pQrStUwXyZaB6dEfGhIjLoPqRsT9uVwX1b" \
  -H "Content-Type: application/json" \
  -d '{
    "enabled": true
  }'
```

Response

```json
{
  "success": true,
  "message": "Warmup enabled successfully",
  "mailboxId": "sender@yourdomain.com",
  "enabled": true,
  "syncStatus": "synced",
  "lastSyncedAt": "2026-04-07T09:12:10.408Z",
  "stateChanged": true
}
```

Once started, leave warmup running for the full cycle.

Warmup runs automatically in the background. Check progress at any time with `GET /api/warmup/mailboxes/:email`.

7

## Send an Email

With a verified domain and a provisioned mailbox you are ready to send. Sending is done over **SMTP** using the mailbox credentials you just created — available on every plan.

All plans

Send via SMTP

Use any SMTP library. The host is the cube host shown in the sidebar of this portal. Use the mailbox email as the username and the password you set in Step 5.

JavaScript

```javascript
import nodemailer from 'nodemailer';

const transporter = nodemailer.createTransport({
  host: 'cube1.missioninbox.com',   // shown in sidebar as "SMTP / IMAP Host"
  port: 465,
  secure: true,
  auth: {
    user: 'sender@yourdomain.com',   // the mailbox email you just created
    pass: 'StrongPassword123',       // the password you set in Step 5
  },
});

const info = await transporter.sendMail({
  from: '"Your Name" <sender@yourdomain.com>',
  to:   'recipient@example.com',
  subject: 'Hello from Mission Inbox',
  text: 'Your first email sent via Mission Inbox SMTP.',
  html: '<p>Your first email sent via Mission Inbox SMTP.</p>',
});

console.log('Sent:', info.messageId);
```

## What's Next

You've completed the core workflow. Here are some things to explore next.

[Bulk operations Create hundreds of domains or mailboxes at once with background tasks.](/api/overview)[Track delivery Poll message status and handle bounces programmatically.](/api/overview)[Domain warmup Warm up an entire domain instead of individual mailboxes.](/api/overview)[Health checks Test inbox placement before sending to real recipients.](/api/overview)

[PreviousAuthentication](https://doc.v4.missioninbox.com/sales/authentication.md)[NextErrors](https://doc.v4.missioninbox.com/sales/errors.md)
