START HERE · Published 2026-10-06 · Updated 2026-10-06 · SecureSMTP

Quickstart

Add a site, copy its key, send the first email — with curl, Node, Python or PHP.

Four steps: add a site, copy its key, add your domain, send. New accounts send only from their own verified domain.

1. Add a site and copy the key

  1. Create an account (the Free plan needs no card).
  2. In the dashboard open Sites (/app/forms/sites) and add your website or app.
  3. Copy the API key from the box that appears. It starts with qcs_live_ and is shown in full only once. We also email it to the account owner. If you lose it, rotate it — see Sites and API keys.
Confirm your email first. New accounts confirm their email address before their sites can send: open the link in the email we send when you sign up. Until then a send is refused with 403 email_not_verified (over SMTP, 550 5.7.1). If you signed up with Google, your address is confirmed already. You can get a new link from the banner at the top of your dashboard.

Keep the key on your server, for example in an environment variable:

Shell
export SECURESSMTP_API_KEY="qcs_live_..."
Never put the key in browser JavaScript or a mobile app. Anyone who has it can send email as your site.

2. Add your domain

  1. In the dashboard open Sending domains (/app/forms/email) and enter the domain you want to send from. The Free plan includes 1 sending domain.
  2. Publish the DNS record it shows at your DNS host.
  3. Click Check DNS, then verify.

See Domains and DNS for the records. Until the domain is verified, a new account’s emails are refused with 403 domain_not_verified.

3. Send an email

curl -X POST https://securessmtp.com/api/v1/mail/send \
  -H "x-securessmtp-api-key: $SECURESSMTP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "to": "[email protected]",
  "subject": "Hello from SecureSMTP",
  "text": "It works."
}'

A successful send answers:

Response
{
  "ok": true,
  "sent": true,
  "mode": "domain",
  "message_id": "<[email protected]>"
}

4. Check the result

  • Always read ok in the response. Some failures — rate limit, monthly limit, send failure — come back with HTTP 200 and "ok": false. See API conventions.
  • Open Email log in the dashboard (/app/forms/email-log) to see whether the email was delivered, bounced or opened.
  • The first email a site sends is always checked by the AI. If it looks like spam or phishing, it is not sent and sending on the site is paused until a person at SecureSMTP checks it: open a support ticket at /support. If we cannot check it just then, you get 503 first_email_check_unavailable: try again in a few minutes. See Deliverability.

Next