Transactional customer email
Receipts, confirmations, alerts, and product messages sent one recipient at a time.
Transactional email and permission-based campaigns.
Every messagehas a route.Know exactly where it went.
Create customer emails, send campaigns, manage contacts, and understand every delivery state from one clear workspace.
Workspace creation is temporarily unavailable.Sign in
See how it worksOne workspace
Two kinds of email. One clear operation.
Send the customer messages your product depends on and the permission-based campaigns your audience chose to receive. RouteKite keeps both visible without turning them into one confusing workflow.
For marketers
Build the message. Choose the audience. Send with confidence.
Bring subscribed contacts into clear lists, compose with the shared editor, and review the exact campaign before sending it now.
- 01
Details
Name the campaign and choose a verified Sending Address.
- 02
Audience
Choose subscribed contacts from the lists you manage.
- 03
Content
Create the message in the same editor used across RouteKite.
- 04
Review
Check the audience, content, sender, and compliance details together.
- 05
Send now
Confirm the campaign and start one traceable delivery per recipient.
CSV imports preserve consent context.
Suppressions and unsubscribe handling are enforced before a marketing send.
Delivery clarity
Know what happened next.
Follow each message through provider-neutral states that say what RouteKite knows, without turning an accepted handoff into a promise about the inbox.
Submitted is not Delivered. Submitted means the receiving provider accepted the handoff for processing. Delivered is a later provider-reported state.
- Queued
- Submitted
- Delivered
- Delayed
- Bounced
- Failed
- Suppressed
Responsible by operation
Clarity also means knowing what should not be sent.
- 01
Permission first
Marketing is for people who agreed to receive it.
- 02
One recipient, one message
Every delivered message represents exactly one recipient.
- 03
Suppressions enforced
Known suppressions stop submission before an email is sent.
- 04
Published means fixed
Published template versions and campaign recipient snapshots stay immutable.
- 05
Variables stay safe
Declared variables are typed, escaped for context, and evaluated without eval.
- 06
Compliance stays present
Required marketing compliance blocks cannot be removed.
Preview pricing
Start with the volume you need. Keep the operation clear.
Transactional and marketing deliveries share one email allowance.
Trial
$0for 14 days
- 1,000 emails total
- 500 marketing contacts
- 1 workspace · 1 domain · 1 seat
- No overage
Starter
$19per month
- 10,000 emails per month
- 1,000 marketing contacts
- 1 workspace · 3 domains · 2 seats
- $1.80 per additional 1,000
Growth
Featured$49per month
- 50,000 emails per month
- 5,000 marketing contacts
- 3 workspaces · 10 domains · 5 seats
- $1.00 per additional 1,000
Scale
$149per month
- 200,000 emails per month
- 25,000 marketing contacts
- 10 workspaces · 50 domains · 15 seats
- $0.75 per additional 1,000
Workspace creation is temporarily unavailable. Sign in
Preview pricing. Billing and automatic plan enforcement are not active. Limits and overage rates are planned for launch and may change.
How usage is counted
One accepted recipient consumes one email across transactional and marketing delivery.
A recipient suppressed before submission does not consume an email.
A bounce or failure after submission still consumes an email.
Only unique subscribed marketing contacts count against the contact allowance.
Transactional-only, unsubscribed, and suppressed addresses do not count as marketing contacts.
For developers
For the systems behind the scenes.
One recipient, one message, one traceable state.
POST /api/v1/emails
curl --request POST https://routekite-app--routekite.us-east4.hosted.app/api/v1/emails \
--header "Authorization: Bearer rk_your_key" \
--header "Idempotency-Key: order-123-confirmation" \
--header "Content-Type: application/json" \
--data '{
"from": "updates@example.com",
"to": "customer@example.net",
"subject": "Your order is confirmed",
"html": "<h1>Thank you</h1><p>Your order is confirmed.</p>"
}'202 Accepted
{
"id": "7dd5da7f-40b0-4c29-bb78-7e0d95ef9eb7",
"object": "email",
"status": "queued",
"created_at": "2026-08-27T10:30:00.000Z"
}- 01Verify a domain
- 02Create a Sending Address
- 03Create an API key
- 04Send one recipient
- 05Observe the resulting state
HTML and plain text
Private attachments
Required idempotency
Message retrieval
Delivery history
Questions, clearly answered
Before the first send.
What does RouteKite do?
RouteKite brings transactional customer email, permission-based campaigns, contacts, templates, and delivery states into one workspace.
Can I use RouteKite without being a developer?
Yes. Marketers can manage contacts, build a campaign, choose an audience, review it, and send from the visual workspace.
How do transactional and marketing email work together?
They share verified domains, Sending Addresses, templates, contacts, suppressions, and delivery history while keeping their different sending flows clear.
Why must marketing recipients have permission?
Permission protects recipients and your sending operation. RouteKite marketing campaigns are designed for people who have agreed to receive them.
How are email and contact usage counted?
One accepted recipient consumes one email. Transactional and marketing sends share that allowance. Only unique subscribed marketing contacts count toward the contact allowance.
What do Submitted and Delivered mean?
Submitted means the receiving provider accepted the handoff for processing. Delivered is a later provider-reported state. Submitted does not mean Delivered.
Is billing active now?
No. Pricing is a launch preview. Checkout, billing, and automatic plan enforcement are not active.
Where can developers find the API documentation?
Start with the public Docs and Quickstart, then use the API reference for exact requests and responses.
Begin clearly
Send with clarity from the first message.
Workspace creation is temporarily unavailable.Sign in
Read the docs