Ship faster by treating email as code 🚀
---
[](https://crates.io/crates/templateless)
[](https://github.com/templateless/templateless-rust/actions)
[](https://docs.rs/templateless/latest/templateless/)
[](https://crates.io/crates/templateless)
[](https://twitter.com/templateless)
[Templateless](https://templateless.com) lets you generate and send transactional emails quickly and easily so you can focus on building your product.
It's perfect for SaaS, web apps, mobile apps, scripts and anywhere you have to send email programmatically.
## ✨ Features
- 👋 **Anti drag-and-drop by design** — emails are a part of your code
- ✅ **Components as code** — function calls turn into email HTML components
- 💻 **SDK for any language** — use your favorite [programming language](https://github.com/orgs/templateless/repositories)
- 🔍 **Meticulously tested** — let us worry about email client compatibility
- 💌 **Use your favorite ESP** — Amazon SES, SendGrid, Mailgun + more
- 💪 **Email infrastructure** — rate-limiting, retries, scheduling + more
- ⚡ **Batch sending** — send 1 email or 1,000 with one API call
## 🚀 Getting started
Install via Cargo:
```bash
cargo add templateless
```
Or add manually to your `Cargo.toml`:
```toml
[dependencies]
templateless = "0.1"
```
## 🔑 Get Your API Key
You'll need an API key for the example below ⬇️
[](https://app.templateless.com/)
- 3,000 emails per month
- All popular email provider integrations
- Start sending right away
## 👩💻 Quick example
This is all it takes to send a signup confirmation email:
```rust
use templateless::{Content, Email, EmailAddress, Templateless, Result};
#[tokio::main]
async fn main() -> Result<()> {
let content = Content::builder()
.text("Hi, please **confirm your email**:")
.button("Confirm Email", "https://your-company.com/signup/confirm?token=XYZ")
.build()?;
let email = Email::builder()
.to(EmailAddress::new(""))
.subject("Confirm your signup 👋")
.content(content)
.build()?;
let _result = Templateless::new("")
.send(email)
.await?;
Ok(())
}
```
There are more Rust examples in the [examples](examples) folder ✨
> [!NOTE]
> 🚧 **The SDK is not stable yet.** This API might change as more features are added. Please watch the repo for the changes in the [CHANGELOG](CHANGELOG.md).
## 🏗 Debugging
You can generate _test API keys_ by activating the **Test Mode** in your dashboard. By using these keys, you'll be able to view your fully rendered emails without actually sending them.
When you use a test API key in your SDK, the following output will appear in your logs when you try to send an email:
```log
Templateless [TEST MODE]: Emailed user@example.com, preview: https://tmpl.sh/ATMxHLX4r9aE
```
The preview link will display the email, but you must be logged in to Templateless to view it.
## 🔳 Components
Emails are crafted programmatically by making function calls. There's no dealing with HTML or drag-and-drop builders.
All of the following components can be mixed and matched to create dynamic emails:
Text / Markdown
Text component allow you to insert a paragraph. Each paragraph supports basic markdown:
- Bold text: `**bold text**`
- Italic text: `_italic text_`
- Link: `[link text](https://example.com)`
- Also a link: ``
- Headers (h1-h6):
- `# Big Header`
- `###### Small Header`
- Unordered list:
```md
- item one
- item two
- item three
```
- Ordered list:
```md
1. item one
1. item two
1. item three
```
```rust
Content::builder()
.text("## Thank you for signing up")
.text("Please **verify your email** by [clicking here](https://example.com/confirm?token=XYZ)")
.build()?;
```
Link
Link component adds an anchor tag. This is the same as a text component with the link written in markdown:
```rust
Content::builder()
.link("Confirm Email", "https://example.com/confirm?token=XYZ")
.build()?;
```
Button
Button can also be used as a call to action. Button color is set via your dashboard's app color.
```rust
Content::builder()
.button("Confirm Email", "https://example.com/confirm?token=XYZ")
.build()?;
```
Image
Image component will link to an image within your email. Keep in mind that a lot of email clients will prevent images from being loaded automatically for privacy reasons.
```rust
// Simple
Content::builder()
.image("https://placekitten.com/300/200")
.build()?;
// Clickable & with attributes
Content::builder()
.component(
Image::new("https://placekitten.com/300/200")
.url("https://example.com")
.width(200)
.height(100)
.alt("Alt Text")
.build()?
)
.build()?;
```
Only the `src` parameter is required; everything else is optional.
**If you have "Image Optimization" turned on:**
1. Your images will be cached and distributed by our CDN for faster loading. The cache does not expire. If you'd like to re-cache, simply append a query parameter to the end of your image url.
1. Images will be converted into formats that are widely supported by email clients. The following image formats will be processed automatically:
- Jpeg
- Png
- Gif
- WebP
- Tiff
- Ico
- Bmp
- Svg
1. Maximum image size is 5MB for free accounts and 20MB for paid accounts.
1. You can specify `width` and/or `height` if you'd like (they are optional). Keep in mind that images will be scaled down to fit within the email theme, if they're too large.
One-Time Password
OTP component is designed for showing temporary passwords and reset codes.
```rust
Content::builder()
.text("Here's your **temporary login code**:")
.otp("XY78-2BT0-YFNB-ALW9")
.build()?;
```
Social Icons
You can easily add social icons with links by simply specifying the username. Usually, this component is placed in the footer of the email.
These are all the supported platforms:
```rust
Content::builder()
.socials(&[
SocialItem::new(Service::Website, "https://example.com"),
SocialItem::new(Service::Email, "username@example.com"),
SocialItem::new(Service::Phone, "123-456-7890"), // `tel:` link
SocialItem::new(Service::Facebook, "Username"),
SocialItem::new(Service::YouTube, "ChannelID"),
SocialItem::new(Service::Twitter, "Username"),
SocialItem::new(Service::X, "Username"),
SocialItem::new(Service::GitHub, "Username"),
SocialItem::new(Service::Instagram, "Username"),
SocialItem::new(Service::LinkedIn, "Username"),
SocialItem::new(Service::Slack, "Org"),
SocialItem::new(Service::Discord, "Username"),
SocialItem::new(Service::TikTok, "Username"),
SocialItem::new(Service::Snapchat, "Username"),
SocialItem::new(Service::Threads, "Username"),
SocialItem::new(Service::Telegram, "Username"),
SocialItem::new(Service::Mastodon, "@Username@example.com"),
SocialItem::new(Service::Rss, "https://example.com/blog"),
])
.build()?;
```
View in Browser
If you'd like your recipients to be able to read the email in a browser, you can add the "view in browser" component that will automatically generate a link. Usually, this is placed in the header or footer of the email.
You can optionally provide the text for the link. If none is provided, default is used: "View in browser"
**Anyone who knows the link will be able to see the email.**
```rust
Content::builder()
.view_in_browser()
.build()?;
```
Store Badges
Link to your mobile apps via store badges:
```rust
Content::builder()
.store_badges(&[
StoreBadgeItem::new(StoreBadge::AppStore, "https://apps.apple.com/us/app/example/id1234567890"),
StoreBadgeItem::new(StoreBadge::GooglePlay, "https://play.google.com/store/apps/details?id=com.example"),
StoreBadgeItem::new(StoreBadge::MicrosoftStore, "https://apps.microsoft.com/detail/example"),
])
.build()?;
```
QR Code
You can also generate QR codes on the fly. They will be shown as images inside the email.
Here are all the supported data types:
```rust
// URL
Content::builder()
.qr_code("https://example.com")
.build()?;
// Email
Content::builder()
.component(QrCode::email("user@example.com"))
.build()?;
// Phone
Content::builder()
.component(QrCode::phone("123-456-7890"))
.build()?;
// SMS / Text message
Content::builder()
.component(QrCode::sms("123-456-7890"))
.build()?;
// Geo coordinates
Content::builder()
.component(QrCode::coordinates(37.773972, -122.431297))
.build()?;
// Crypto address (for now only Bitcoin and Ethereum are supported)
Content::builder()
.component(QrCode::cryptocurrency_address(Cryptocurrency::Bitcoin, "1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"))
.build()?;
// You can also encode any binary data
Content::builder()
.component(QrCode::new(&[1, 2, 3]))
.build()?;
```
Signature
Generated signatures can be added to your emails to give a bit of a personal touch. This will embed an image with your custom text using one of several available fonts:
```rust
// Signature with a default font
Content::builder()
.signature("John Smith")
.build()?;
// Signature with a custom font
Content::builder()
.component(Signature::new("John Smith", Some(SignatureFont::ReenieBeanie)))
.build()?;
```
These are the available fonts:
- `SignatureFont::ReenieBeanie` [preview →](https://fonts.google.com/specimen/Reenie+Beanie)
- `SignatureFont::MeowScript` [preview →](https://fonts.google.com/specimen/Meow+Script)
- `SignatureFont::Caveat` [preview →](https://fonts.google.com/specimen/Caveat)
- `SignatureFont::Zeyada` [preview →](https://fonts.google.com/specimen/Zeyada)
- `SignatureFont::Petemoss` [preview →](https://fonts.google.com/specimen/Petemoss)
Signature should not exceed 64 characters. Only alphanumeric characters and most common symbols are allowed.