Feature · transactional

Receipts and resets,
same platform.

API-triggered sends against a pinned template version, on the same platform as your marketing.

Permission first. Every brand distinct.
Why it matters

Two systems, two versions of the truth.

Running transactional mail through a separate service means separate templates, a separate suppression list, and separate reporting. Ask what a customer received last Tuesday and you have to check two places and reconcile them by hand.

SendNectar sends transactional mail through the same brands, templates, providers, and reporting as everything else — while keeping the message class genuinely distinct so marketing rules never apply to a password reset.

Capabilities

Transactional email, in detail.

01

One explicit request

A brand, a pinned template version, a recipient, merge variables, metadata, and your own external reference. Nothing is implicit.

02

Pinned to a version

Sends target an immutable, hash-verified template version — editing the draft never changes what is going out right now.

03

Its own message class

Transactional is separate from marketing: not subject to frequency caps, not gated on topic subscription, and separately routable.

04

Dedicated routes

Give transactional traffic its own provider connection and sending routes so a marketing burst cannot delay it.

05

Live and test keys

API keys carry a mode, explicit scopes, optional brand restrictions, and an expiry. New tokens are shown exactly once.

06

Unified history

Transactional history sits alongside campaign reporting with the same message events and per-message status.

The product surface

The request payload.

Everything a transactional send needs, and nothing it does not.

brand_id
The brand the message sends as — identity, footer, and legal entity
template_version_id
An immutable published version, never a live draft
to_email
Recipient address, optionally with a contact reference
external_reference
Your identifier, for idempotency and reconciliation
variables
Merge data rendered into the pinned version
metadata
Arbitrary key-values carried through to reporting

Bring your provider.
Keep your brands distinct.
Start today.

Set up your first workspace, connect a provider, and publish a workflow — free, in test mode, before you pay a thing.