Quickstart

From nothing to a delivered message in four steps.

1. Verify a sending domain

Use a subdomain you control, such as mail.yourcompany.com. Sending from a subdomain keeps a future delivery problem away from the reputation of your main domain. The dashboard prints every DNS record you need.

veltic-send domains add mail.yourcompany.com
# set the printed DNS records, then
veltic-send domains verify mail.yourcompany.com

2. Create an API key

Keys are created in the dashboard and shown exactly once. Only a SHA-256 hash is stored, so a lost key is replaced rather than recovered.

veltic-send auth
# paste the key when prompted

3. Send

The answer is 202, not 200: the message is accepted and handed to a queue that drains at a fixed rate. That is what keeps a burst from turning into refusals.

curl https://send.veltic.app/v1/emails \
  -H "Authorization: Bearer vsend_…" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-4711" \
  -d '{
    "from": "noreply@mail.yourcompany.com",
    "to": "customer@example.org",
    "subject": "Your order has shipped",
    "text": "Tracking: 1234567890"
  }'

4. Read what happened

Events come from Amazon: Send, Delivery, Bounce, Complaint. A permanent bounce or a complaint adds the address to your suppression list automatically, and the next attempt to send there is refused before it costs anything.

veltic-send logs
veltic-send logs 5f0c…