This guide walks you through the model — templates, sends, contacts — and gets you to a working send() in under five minutes. If you've used Resend, Postmark, or Mailgun before, the API surface will feel familiar. The difference is the layer above: Ewyn generates and maintains the templates themselves, so your designers and engineers stop trading HTML diffs at 11pm.
How Ewyn works
Three primitives compose every send:
- Brand kit — design tokens (colors, fonts, logo) extracted from your website, frozen into each template at save time
- Template — generated from a natural-language prompt, versioned, addressable by name or version ID
- Send — an API call that renders a template version with your variables and dispatches it through your configured ESP
TL;DR. A template + an API call = a delivered, on-brand email. Everything else (contacts, suppression, idempotency, delivery events) builds on those primitives.
Install the SDK
The official SDK is TypeScript-first and runs anywhere Node.js 18+ runs:
npm install @ewyn/client
# or
pnpm add @ewyn/clientOr skip the SDK and use the REST API directly — every endpoint is covered in the API reference.
Send your first email
The canonical hello world — a fully rendered, on-brand email:
import { Ewyn } from '@ewyn/client';
const client = new Ewyn({ apiKey: process.env.EWYN_API_KEY! });
const { messageId } = await client.send({
to: 'user@example.com',
subject: 'Welcome!',
templateId: 'template-version-uuid',
variables: { firstName: 'Maya' },
});
console.log(messageId); // queued for deliveryEvery published template version has a UUID, visible in the dashboard. Better: use type-safe templates and address templates by name with full autocomplete.
Where to go next
- Authentication — create an API key and wire it into your environment
- Send your first email — the full quickstart, from key to delivered message
- Type-safe templates — generate a typed config with
npx @ewyn/client fetch-config - API reference — every endpoint with request/response shapes and curl examples
Need help? Contact the team — pre-sales chats and support tickets are handled by the same people who build the product.