Quickstart

Not your website’s domain: the sender’s. Use a subdomain — news.yourcompany.com, mail.yourcompany.com — not the apex.The reason is reputation. If your newsletter and your password reset leave from the same domain, one bad campaign takes down the email someone is waiting for on screen.

curl -X POST https://kourio.app/v1/domains \
  -H "Authorization: Bearer $KOURIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "name": "news.yourcompany.com" }'

The response carries the DNS records to publish.

Publish the DNS

If the domain already has SPF — common with Google Workspace or Microsoft 365 — do not publish a second one. Two v=spf1 records on the same name are a permerror, and the domain ends up with no SPF at all: the mail you already send today starts failing. Add include:_spf.kourio.app to the record that exists.

Then ask for a check:

curl -X POST https://kourio.app/v1/domains/{id}/verify \
  -H "Authorization: Bearer $KOURIO_API_KEY"

Send the first message

curl -X POST https://kourio.app/v1/emails \
  -H "Authorization: Bearer $KOURIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "from": "Your Company <orders@news.yourcompany.com>",
    "to": "customer@example.com",
    "subject": "Order A-10428 is on its way",
    "html": "<p>Arriving tomorrow by 6pm.</p>"
  }'

The response comes back before the message leaves — it enters the queue. To know whether it arrived, use a webhook or fetch the message later.

With the SDK

npm install @kourio/sdk

import { Kourio } from '@kourio/sdk';

const kourio = new Kourio(process.env.KOURIO_API_KEY!);

await kourio.emails.send({
  from: 'Your Company <orders@news.yourcompany.com>',
  to: 'customer@example.com',
  subject: 'Order A-10428 is on its way',
  html: '<p>Arriving tomorrow by 6pm.</p>',
});

Get started

Send

Know what happened

Account

Integrations

With the SDK

​With the SDK

With the SDK