Meghly Send

Send quickstart

Send your first email with Meghly Send in four steps: add and verify a domain, make a key, send by API or SMTP, and read the result in the events log.

Meghly Send delivers email by HTTP API or SMTP. It also includes address validation and inbound routes, which have their own pages (Validate and Receive).

1. Add and verify your domain

You can only send from a domain you have verified. On the Domains page, add the domain, then open DNS records for this domain. It lists every record you need (SPF, DKIM, DMARC and the rest) and shows which are in place. The domain turns Verified when they all are.

2. Make a key

On the API keys page, make a Send key. It starts with mpk_ and is sent in the X-Api-Key header. A Domain sending key works for one domain only and can only send.

Keys made for Validate (yvk_…) cannot send mail, and Send keys cannot validate. This is on purpose, so a leaked sending key cannot spend your validation credits.

3. Send a message

bash
curl -X POST https://api.meghlycloud.com/api/v1/messages \
  -H "X-Api-Key: mpk_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "hello@yourdomain.com",
    "to": "customer@example.org",
    "subject": "Your receipt",
    "html": "<p>Thanks for your order.</p>"
  }'

The answer is 202 Accepted with the message id. Delivery results arrive on your webhooks, or you can read them with GET /api/v1/messages/{id}.

Add "testMode": true to check everything as for a real send without sending anything.

3b. Or send over SMTP

On the SMTP logins tab of a domain, make a login. The page shows the server, the port (587 with STARTTLS, or 465 with TLS) and the username. The password is shown once, when the login is made. A login can send only from its own domain.

4. Read the result

The Send page shows the events log and charts of daily failures and the complaint rate. The same data is available at GET /api/v1/events and GET /api/v1/analytics.

Things that are always on

  • Every message carries a List-Unsubscribe header with one-click support.
  • A recipient who unsubscribes or complains is added to your suppression list, and later sends to them are refused with 422.

Next: the Send API reference.

Stuck?

Talk to our engineers directly — by phone or email.

01782618248shohag.meghly@gmail.com