Getting Started
Quickstart
From account creation to your first accepted email in about five minutes. This guide takes the BYOC path, your own AWS SES account, which is available as soon as your account email and sending domain are verified.
Prerequisites
For the BYOC path you need:
- An AWS account. If its SES account is still in the sandbox, SendFleet requests production access for you from the dashboard
- A domain you control, so you can add DNS records
- Permission to create IAM roles in that AWS account
How to send your first transactional email with SendFleet
Create a SendFleet account
Register at sendfleet.net/register. Email verification is required before you can send. The Free BYOC plan costs nothing and includes 3,000 emails per month, no card needed.Create an IAM role in AWS
Open Dashboard → AWS and press Create the role in AWS. AWS CloudFormation opens a ready-made stack that creates the roleSendFleet-BYOC-Rolewith your unique ExternalId already filled in. Tick the IAM acknowledgement and press Create stack. Full walkthrough in BYOC Setup.Connect your IAM role
CopyRoleArnfrom the stack's Outputs tab, paste it into Dashboard → AWS and press Connect. We confirm that the role can be used, find the region where your SES account has production access, and set up delivery tracking in your account.arn:aws:iam::123456789012:role/SendFleet-BYOC-Role
Add and verify a sending domain
Go to Dashboard → Domains → Add BYOC domain and enter your root domain, for exampleacme.com. We register the identity in your SES account and show you the DNS records to add. Once both ownership TXT records have propagated, choose Verify ownership, then Verify DKIM. A domain is send-ready only once both checks pass.Generate an API key
Go to Dashboard → API Keys → New key and give it a name such as "Production". You land on the send page with the full key in a copy box at the top and the example requests below already using it. It is displayed exactly once, so copy it into your environment variables or secrets manager. Only a SHA-512 hash is stored, so a lost key cannot be recovered.
Optionally restrict the key to specific sending domains under Domain scope. A scoped key can only send from the domains you pick; leave it empty and the key can send from all of them.Send your first email
ReplaceYOUR_API_KEYandhello@acme.comwith your own key and verified domain.curl -X POST https://api.sendfleet.net/v1/send \ -H "X-API-Key: YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "to": "user@example.com", "from_email": "hello@acme.com", "from_name": "Acme", "subject": "Welcome aboard", "message": "Thanks for signing up!" }'
Successful response
A 200 OK means your email was accepted and queued. Delivery happens asynchronously, so this is an acceptance receipt rather than proof of delivery.
{
"success": true,
"message": "Email queued for delivery via your SES account.",
"message_id": "1a2b3c4d-5e6f-7890-abcd-ef1234567890",
"idempotency_key": "8f14e45fceea167a5a36dedd4bea2543",
"mode": "byoc"
}Next steps
| Topic | Description |
|---|---|
| Send Email reference | Every request parameter, HTML bodies, attachments, and reply-to. |
| DNS records | DKIM, MAIL FROM, and DMARC for the best inbox placement. |
| Error codes | Understand and handle every error response. |
| Plans & limits | Rate limits, monthly quotas, and upgrade paths. |