Send Email

Endpoint: POSThttps://api.sendfleet.net/v1/send

Request headers

There is no SDK and no client library. Anything that can send an HTTP request with a JSON body can send email, and the examples below cover cURL, Python, Node.js, PHP, Go and Ruby. On WordPress, the official plugin makes this call for every wp_mail() email, so there is no code to write.

Example request

curl -X POST https://api.sendfleet.net/v1/send \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "to":         "alice@example.com",
    "from_email": "hello@yourdomain.com",
    "from_name":  "Your App",
    "subject":    "Your order has shipped",
    "message":    "Hi Alice,\n\nYour order #1234 has shipped!\n\nTrack it: https://track.example.com/1234\n\nThanks,\nYour App",
    "html":       "<p>Hi Alice,</p><p>Your order <strong>#1234</strong> has shipped!</p><p><a href=\"https://track.example.com/1234\">Track your order</a></p>",
    "reply_to":   "support@yourdomain.com",
    "attachments": [
      {
        "filename":     "invoice.pdf",
        "content":      "JVBERi0xLjQK...",
        "content_type": "application/pdf"
      }
    ]
  }'

The smallest body that works

A recipient, a sender and one body. Every other field on this page is optional and can be added later.

{
  "to": "user@example.com",
  "from_email": "hello@yourdomain.com",
  "message": "Thanks for your order!"
}

Request body

All parameters are passed as a JSON object in the request body.

Several recipients

One request sends one message to everyone in to, cc and bcc. Each recipient counts as one send against your monthly allowance, the way Amazon SES counts them, so the example below uses four. A send that needs more than your plan has left is refused whole with 429 usage_limit_exceeded; it never goes to only some of its recipients.

{
  "to":         ["alice@example.com", "bob@example.com"],
  "cc":         "accounts@example.com",
  "bcc":        ["archive@yourdomain.com"],
  "from_email": "orders@yourdomain.com",
  "subject":    "Your order #1042",
  "message":    "Thanks for your order!"
}

Successful response

HTTP 200 OK. The email has been accepted and queued, delivery is asynchronous, so this is not a delivery confirmation.

{
  "success":         true,
  "message":         "Email queued for delivery via your SES account.",
  "message_id":      "1a2b3c4d-5e6f-7890-abcd-ef1234567890",
  "idempotency_key": "3c59dc048e8850243be8079a5c74d079",
  "mode":            "byoc",
  "attachments":     2
}

{
  "success":         true,
  "message":         "Email queued for delivery.",
  "message_id":      "9f8e7d6c-5b4a-3210-fedc-ba9876543210",
  "idempotency_key": "8f14e45fceea167a5a36dedd4bea2543",
  "mode":            "shared",
  "warnings": [
    "DMARC record not found. Add 'v=DMARC1; p=none;' as a TXT record on _dmarc.yourdomain.com to improve inbox placement."
  ]
}

Response fields

Error responses

Sending refusals use the shape below. error is a machine-readable code to branch on;detail is a human-readable explanation. Field validation errors return a map of field names to messages. Authentication, rate-limit and HTTP-level errors can return only detail.

{
  "success": false,
  "error":   "domain_not_verified",
  "detail":  "Domain 'yourdomain.com' is not yet verified. Add both TXT ownership records, then press Verify all records at https://sendfleet.net/dashboard/domains/"
}

See the full Error Codes reference for retry guidance and worked handling examples.

HTML email tips

Email HTML is not browser HTML. Gmail, Outlook, and Apple Mail strip modern CSS and block external resources, so the rules are stricter than you are used to: